Interesting.
Can you get the full contents of the “cut here” section?
Also, I have a test version of kernel 5.8.6 available if that’s worth trying.
I have this higher up which is probably related to the error messages about no vector irq.
Sep 03 18:35:38 eos-xfce kernel: AMD-Vi: [Firmware Bug]: : No southbridge IOAPIC found
Sep 03 18:35:38 eos-xfce kernel: AMD-Vi: Disabling interrupt remapping
Sep 03 18:35:39 eos-xfce systemd-udevd[376]: controlC0: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
Sep 03 18:35:39 eos-xfce kernel: wl: loading out-of-tree module taints kernel.
Sep 03 18:35:39 eos-xfce kernel: wl: module license 'MIXED/Proprietary' taints kernel.
Sep 03 18:35:39 eos-xfce kernel: Disabling lock debugging due to kernel taint
Sep 03 18:35:39 eos-xfce kernel: wl: module verification failed: signature and/or required key missing - tainting kernel
Sep 03 18:35:39 eos-xfce kernel: MCE: In-kernel MCE decoding enabled.
Sep 03 18:35:39 eos-xfce systemd-udevd[408]: controlC1: Process '/usr/bin/alsactl restore 1' failed with exit code 99.
Sep 03 18:35:39 eos-xfce kernel: EDAC amd64: F17h_M70h detected (node 0).
Sep 03 18:35:39 eos-xfce kernel: EDAC amd64: Node 0: DRAM ECC disabled.
Sep 03 18:35:39 eos-xfce kernel: wl 0000:25:00.0: enabling device (0000 -> 0002)
Sep 03 18:35:39 eos-xfce kernel: wl 0000:25:00.0: can't find IRQ for PCI INT A; please try using pci=biosirq
Sep 03 18:35:39 eos-xfce kernel: genirq: Flags mismatch irq 0. 00000080 (wlan%d) vs. 00015a00 (timer)
Sep 03 18:35:39 eos-xfce kernel: ERROR @wl_cfg80211_detach :
Sep 03 18:35:39 eos-xfce kernel: NULL ndev->ieee80211ptr, unable to deref wl
Sep 03 18:35:39 eos-xfce kernel: ------------[ cut here ]------------
Sep 03 18:35:39 eos-xfce kernel: MCE: In-kernel MCE decoding enabled.
Sep 03 18:35:39 eos-xfce systemd-udevd[408]: controlC1: Process '/usr/bin/alsactl restore 1' failed with exit code 99.
Sep 03 18:35:39 eos-xfce kernel: EDAC amd64: F17h_M70h detected (node 0).
Sep 03 18:35:39 eos-xfce kernel: EDAC amd64: Node 0: DRAM ECC disabled.
Sep 03 18:35:39 eos-xfce kernel: wl 0000:25:00.0: enabling device (0000 -> 0002)
Sep 03 18:35:39 eos-xfce kernel: wl 0000:25:00.0: can't find IRQ for PCI INT A; please try using pci=biosirq
Sep 03 18:35:39 eos-xfce kernel: genirq: Flags mismatch irq 0. 00000080 (wlan%d) vs. 00015a00 (timer)
Sep 03 18:35:39 eos-xfce kernel: ERROR @wl_cfg80211_detach :
Sep 03 18:35:39 eos-xfce kernel: NULL ndev->ieee80211ptr, unable to deref wl
Sep 03 18:35:39 eos-xfce kernel: ------------[ cut here ]------------
Sep 03 18:35:39 eos-xfce kernel: name 'brcm_monitor0'
Sep 03 18:35:39 eos-xfce kernel: WARNING: CPU: 13 PID: 422 at fs/proc/generic.c:694 remove_proc_entry+0x17a/0x1b0
Sep 03 18:35:39 eos-xfce kernel: Modules linked in: amd64_edac_mod(-) pcc_cpufreq(-) wl(POE+) edac_mce_amd kvm_amd nls_iso8859_1 ccp nls_cp437 snd_hda_codec_realtek rng_core snd_hda_codec_generic vfat fat wm>
Sep 03 18:35:39 eos-xfce kernel: CPU: 13 PID: 422 Comm: systemd-udevd Tainted: P OE 5.8.5-arch1-1 #1
Sep 03 18:35:39 eos-xfce kernel: Hardware name: Micro-Star International Co., Ltd. MS-7C37/MPG X570 GAMING PLUS (MS-7C37), BIOS A.90 08/07/2020
Sep 03 18:35:39 eos-xfce kernel: RIP: 0010:remove_proc_entry+0x17a/0x1b0
Sep 03 18:35:39 eos-xfce kernel: Code: 00 00 00 e8 1e 71 d0 ff 0f 0b e9 7a ff ff ff 48 c7 c7 68 c3 38 a9 e8 95 22 68 00 4c 89 e6 48 c7 c7 2f a3 78 a8 e8 fc 70 d0 ff <0f> 0b e9 60 ff ff ff 48 8b b0 a0 00 00 0>
Sep 03 18:35:39 eos-xfce kernel: RSP: 0018:ffffb23a01117990 EFLAGS: 00010286
Sep 03 18:35:39 eos-xfce kernel: RAX: 0000000000000000 RBX: ffffffffa8ca9440 RCX: 0000000000000000
Sep 03 18:35:39 eos-xfce kernel: RDX: 0000000000000001 RSI: ffffffffa876ac7f RDI: 00000000ffffffff
Sep 03 18:35:39 eos-xfce kernel: RBP: 0000000000000000 R08: 0000000000000467 R09: 0000000000000003
Sep 03 18:35:39 eos-xfce kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffffb23a011179c8
Sep 03 18:35:39 eos-xfce kernel: R13: ffff8cacc56f2660 R14: 00000000000043a0 R15: ffff8cacc574dc00
Sep 03 18:35:39 eos-xfce kernel: FS: 00007f17933a9440(0000) GS:ffff8cacced40000(0000) knlGS:0000000000000000
Sep 03 18:35:39 eos-xfce kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 03 18:35:39 eos-xfce kernel: CR2: 0000559a8d64f950 CR3: 00000007f9dac000 CR4: 0000000000340ee0
Sep 03 18:35:39 eos-xfce kernel: Call Trace:
Sep 03 18:35:39 eos-xfce kernel: wl_free+0xbb/0x220 [wl]
Sep 03 18:35:39 eos-xfce kernel: wl_pci_probe+0x598/0xf7b [wl]
Sep 03 18:35:39 eos-xfce kernel: local_pci_probe+0x42/0x80
Sep 03 18:35:39 eos-xfce kernel: ? pci_match_device+0xd7/0x100
Sep 03 18:35:39 eos-xfce kernel: pci_device_probe+0xfa/0x1b0
Sep 03 18:35:39 eos-xfce kernel: really_probe+0x160/0x400
Sep 03 18:35:39 eos-xfce kernel: driver_probe_device+0xe1/0x150
Sep 03 18:35:39 eos-xfce kernel: device_driver_attach+0xa1/0xb0
Sep 03 18:35:39 eos-xfce kernel: __driver_attach+0x8a/0x150
Sep 03 18:35:39 eos-xfce kernel: ? device_driver_attach+0xb0/0xb0
Sep 03 18:35:39 eos-xfce kernel: ? device_driver_attach+0xb0/0xb0
Sep 03 18:35:39 eos-xfce kernel: bus_for_each_dev+0x89/0xd0
Sep 03 18:35:39 eos-xfce kernel: bus_add_driver+0x12b/0x1e0
Sep 03 18:35:39 eos-xfce kernel: driver_register+0x8b/0xe0
Sep 03 18:35:39 eos-xfce kernel: ? 0xffffffffc0cb4000
Sep 03 18:35:39 eos-xfce kernel: do_one_initcall+0x59/0x240
Sep 03 18:35:39 eos-xfce kernel: do_init_module+0x5c/0x260
Sep 03 18:35:39 eos-xfce kernel: load_module+0x21a5/0x2450
Sep 03 18:35:39 eos-xfce kernel: __do_sys_init_module+0x12d/0x180
Sep 03 18:35:39 eos-xfce kernel: do_syscall_64+0x44/0x70
Sep 03 18:35:39 eos-xfce kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Sep 03 18:35:39 eos-xfce kernel: RIP: 0033:0x7f179415ae4e
Sep 03 18:35:39 eos-xfce kernel: Code: 48 8b 0d 25 10 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d f2 0>
Sep 03 18:35:39 eos-xfce kernel: RSP: 002b:00007ffce8a85448 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
Sep 03 18:35:39 eos-xfce kernel: RAX: ffffffffffffffda RBX: 0000559a8d658670 RCX: 00007f179415ae4e
Sep 03 18:35:39 eos-xfce kernel: RDX: 00007f179429397d RSI: 0000000000734310 RDI: 0000559a8e024320
Sep 03 18:35:39 eos-xfce kernel: RBP: 0000559a8e024320 R08: ffffffffffffffe0 R09: 00007ffce8a83600
Sep 03 18:35:39 eos-xfce kernel: R10: 0000559a8d4e6010 R11: 0000000000000246 R12: 00007f179429397d
Sep 03 18:35:39 eos-xfce kernel: R13: 0000000000000002 R14: 0000559a8d6471a0 R15: 0000559a8d658670
Sep 03 18:35:39 eos-xfce kernel: ---[ end trace d34a9f180d398984 ]---
OK, yep, the driver is crashing. That’s not good.
I’d say to make sure you’re up-to-date, remove and reinstall the driver, and try a different kernel (e.g. linux-lts) until things get fixed. As @Stephane says, 5.8.6 includes a lot of fixes.
Just to bring you up to speed i had recently updated the UEFI firmware and i was getting the no vector handler irq errors so i flashed back to the previous UEFI firmware for a while. Then i updated it again and i was using the acpi=no irq kernel parameter without issue accept that there are a lot of pci-e errors in the journal. Then with these newer kernel updates i noticed the wifi not working. So now i just tried a couple of things and actually removing the acpi=noirq has worked and wifi is back up.
So now i guess i just put up with the messages on boot screen or revert back to the previous UEFI firmware? Or wait and see if a newer kernel will work again with the acpi=noirq parameter unless you have another one that will rid me of the messages. What do you suggest. I could post the whole journal as it has a lot of pci-express errors related to irq. I think it’s a poor implementation of UEFI firmware from MSI. This is an X570 motherboard. I flashed the 7C37vA9 version and the original was 7C37vA7
1 Like
If the choice is between a couple of messages on boot and working wifi I think I’d go for the working wifi. Recent AMD CPUs also seem to present various boot-time messages which are just cosmetic and don’t actually affect anything.
Well i didn’t have any issues before but now it seems that there are a lot more error messages using the kernel parameter and the wifi quit working. Here is the log of the journalctl -b without the kernel parameter and wifi is working. You can see the no vector handler irq messages but all the other error messages are now gone. Take a look at it if you don’t mind but it looks like with the newer kernels it’s a problem using that parameter.
Edit: I could go back to the other UEFI firmware version but this one actually has some features for the nvme drives also.
Seems to be this:
Essentially, it used to be an informational message, but was promoted to “emergency” level even though it hasn’t actually changed, it might improve with 5.8/5.9.
All in all, it’s a cosmetic issue.
2 Likes
Thanks for your advice. I appreciate it! Wifi is working now with it removed and less errors in journalctl -b.
5 Likes
just adding this to recheck libvirtd
and the hell dbus-org.bluez.service - pulseaudio - systemd ( bluetooth )
Sep 03 19:03:49 eos-xfce libvirtd[792]: direct firewall backend requested, but /usr/bin/ebtables is not available: No such file or directory
Sep 03 19:03:49 eos-xfce libvirtd[792]: internal error: Failed to initialize a valid firewall backend
Sep 03 19:03:56 eos-xfce dbus-daemon[594]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.62' (uid=1000 pid=1308 comm="/usr/bin/pulseaudio --daemonize=no ")
Sep 03 19:03:56 eos-xfce dbus-daemon[594]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Sep 03 19:03:56 eos-xfce systemd[1205]: Started Sound Service.
Sep 03 19:03:56 eos-xfce pulseaudio[1308]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.