Installed kernel 5.4.72-1 errors popped up

GokuSan · 21 October 2020 19:25

Hello, I just upgraded from kernel 4.19.152 to 5.4.72 and some errors popped up.
How to resolve them ???

$ sudo journalctl -p 3 -xb


-- Logs begin at Sun 2019-03-03 18:25:48 CET, end at Wed 2020-10-21 20:29:19 CEST. --
Oct 21 20:28:09 HELLRIDER kernel: usbhid 4-1.1:1.1: couldn't find an input interrupt endpoint
Oct 21 20:28:10 HELLRIDER kernel: hdaudio hdaudioC1D0: no AFG or MFG node found
Oct 21 20:28:10 HELLRIDER kernel: hdaudio hdaudioC1D1: no AFG or MFG node found
Oct 21 20:28:10 HELLRIDER kernel: hdaudio hdaudioC1D2: no AFG or MFG node found
Oct 21 20:28:10 HELLRIDER kernel: hdaudio hdaudioC1D3: no AFG or MFG node found
Oct 21 20:28:10 HELLRIDER kernel: hdaudio hdaudioC1D4: no AFG or MFG node found
Oct 21 20:28:10 HELLRIDER kernel: hdaudio hdaudioC1D5: no AFG or MFG node found
Oct 21 20:28:10 HELLRIDER kernel: hdaudio hdaudioC1D6: no AFG or MFG node found
Oct 21 20:28:10 HELLRIDER kernel: hdaudio hdaudioC1D7: no AFG or MFG node found
Oct 21 20:28:10 HELLRIDER kernel: snd_hda_intel 0000:01:00.1: no codecs initialized
Oct 21 20:28:24 HELLRIDER lightdm[1071]: gkr-pam: unable to locate daemon control file

$ inxi -SGAx


System:    Host: HELLRIDER Kernel: 5.4.72-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: Xfce 4.14.2 
           Distro: Manjaro Linux 
Graphics:  Device-1: Intel Core Processor Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 
           Device-2: NVIDIA GT216M [GeForce GT 325M] vendor: ASUSTeK driver: nvidia v: 340.108 bus ID: 01:00.0 
           Device-3: IMC Networks 2M Integrated Webcam type: USB driver: uvcvideo bus ID: 3-1.2:3 
           Display: x11 server: X.Org 1.20.9 driver: modesetting,nvidia resolution: 1600x900~60Hz 
           OpenGL: renderer: GeForce GT 325M/PCIe/SSE2 v: 3.3.0 NVIDIA 340.108 direct render: Yes 
Audio:     Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 
           Device-2: NVIDIA GT216 HDMI Audio driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           Sound Server: ALSA v: k5.4.72-1-MANJARO

I want to resolve the hdaudio and snd_hda_intel errors.
Any help is appreciated.
If any other details are needed do tell and i will post them.

Fabby · 21 October 2020 22:06

GokuSan:

If any other details are needed do tell and i will post them.

An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information… (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)

and if that doesn’t contain any info on usbhid 4-1.1:1.1, an lsusb too please.
Which sound problems are you having specifically?

GokuSan · 22 October 2020 18:47

Hello @Fabby, sorry for the late reply, I am super busy.

$ inxi --admin --verbosity=7 --filter --no-host --width


System:
  Kernel: 5.4.72-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
  parameters: BOOT_IMAGE=/vmlinuz-5.4-x86_64 
  Desktop: Xfce 4.14.2 tk: Gtk 3.24.20 info: xfce4-panel wm: xfwm4 
  dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:
  Type: Laptop System: ASUSTeK product: N71Jv v: 1.0 serial:  
  Mobo: ASUSTeK model: N71Jv v: 1.0 serial:  BIOS: American Megatrends 
  v: N71Jv.206 date: 01/29/2010  
CPU:
  Topology: Dual Core model: Intel Core i3 M 350 bits: 64 type: MT MCP 
  arch: Nehalem family: 6 model-id: 25 (37) stepping: 2 microcode: 11 
  L2 cache: 3072 KiB bogomips: 18549 
  Speed: 2301 MHz min/max: 933/2266 MHz Core speeds (MHz): 1: 2301 2: 2112 
  3: 2194 4: 2217 
  Flags: acpi aperfmperf apic arat arch_perfmon bts clflush cmov constant_tsc 
  cpuid cx16 cx8 de ds_cpl dtes64 dtherm dts ept est flexpriority flush_l1d 
  fpu fxsr ht ibpb ibrs lahf_lm lm mca mce mmx monitor msr mtrr nonstop_tsc 
  nopl nx pae pat pbe pdcm pebs pge pni popcnt pse pse36 pti rdtscp rep_good 
  sep ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc 
  vme vmx vnmi vpid xtopology xtpr 
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56 
  Device-2: NVIDIA GT216 HDMI Audio driver: snd_hda_intel v: kernel 
  bus ID: 01:00.1 chip ID: 10de:0be2 
  Sound Server: ALSA v: k5.4.72-1-MANJARO 
USB:
  Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 speed: 480 Mb/s 
  chip ID: 1d6b:0002 
  Hub: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0 
  speed: 480 Mb/s chip ID: 8087:0020 
  Device-1: 1-1.2:3 info: IMC Networks 2M Integrated Webcam type: Video 
  driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s chip ID: 13d3:5122 
  Device-2: 1-1.5:4 info: ASUSTek BT-270 Bluetooth Adapter type: Bluetooth 
  driver: btusb interfaces: 4 rev: 2.0 speed: 12 Mb/s chip ID: 0b05:1788 
  serial:  
  Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 speed: 480 Mb/s 
  chip ID: 1d6b:0002 
  Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 speed: 480 Mb/s 
  chip ID: 1d6b:0002 
  Hub: 3-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0 
  speed: 480 Mb/s chip ID: 8087:0020 
  Device-1: 3-1.1:3 info: KYE Systems (Mouse Systems) type: Mouse,HID 
  driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s 
  chip ID: 0458:018b 
  Device-2: 3-1.2:4 info: Elan Micro ActiveJet K-2024 Multimedia Keyboard 
  type: Keyboard,HID driver: hid-generic,usbhid interfaces: 2 rev: 1.1 
  speed: 1.5 Mb/s chip ID: 04f3:0103 
  Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.0 speed: 5 Gb/s 
  chip ID: 1d6b:0003

This is all the relevant info from the command about system, machine, audio and usb.
The usbhid 4-1.1:1.1 is under usbhid 3-1.1:1.1 today according to the errors from today(all the same except the usbhid) journalctl its Device-1: 3-1.1:3 in the log above its the mouse(Genius Gaming Mouse X-G200).

In regard to the

Currently none. Microphone is working, AUX is working, Speakers are working, so I really don’t know why are the errors from the journalctl appearing???

Fabby · 22 October 2020 18:57

They’re not: they’re debug / warning messages…

These are the errors:

journalctl --system --boot=0 | grep error

It’s just that the kernel gets chattier and chattier as it’s growing up, just like kids, and more potential warnings get posted over time…

Stop worrying if everything is working fine…

GokuSan · 22 October 2020 19:14

@Fabby ok thanks… cheers

Fabby · 22 October 2020 19:18

I’ve marked the below answer as the solution to your question:

In the future, please don’t forget to come back and click the 3 dots below the answer to mark a solution like this:

so that the next person that has the same problem as you will now find a “solved” question.

system · 6 November 2020 19:19

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.