When booting into Manjaro, 3 lines show
On the screen with the message no irq handler for vector on each line.
I can successfully boot into the OS fine and no other issues occur. Just really don’t like these errors popping up.
I did recently upgrade my BIOS to F60 for gigabyte aurous elite. Didn’t see these error before that but I also upgraded the kernel at the same time to the latest stable release.
It also would help others to help you better when you provide the exact log lines of those errors.
You should be able to view them using: sudo dmesg --human
Hello, sorry if not the same issue, I’m not sure.
I have a message boot, so I type: **journalctl -b -p err|less **
I extract just the message in the boot because they are a lot of lines, they error shows in red.
i think that maybe this could be because I change my motherboard, CPU and Graphic card, but I’m not sure either.
Thanks in advance for any help.
The error is this:
– Journal begins at Sat 2020-11-14 11:21:55 EST, ends at Fri 2020-12-18 15:53:46 EST. –
Dec 18 15:00:37 riggs kernel: __common_interrupt: 1.55 No irq handler for vector
Dec 18 15:00:37 riggs kernel: __common_interrupt: 2.55 No irq handler for vector
Dec 18 15:00:37 riggs kernel: __common_interrupt: 3.55 No irq handler for vector
Dec 18 15:00:37 riggs kernel: __common_interrupt: 4.55 No irq handler for vector
Dec 18 15:00:37 riggs kernel: __common_interrupt: 5.55 No irq handler for vector
Dec 18 15:00:37 riggs kernel: __common_interrupt: 6.55 No irq handler for vector
Dec 18 15:00:37 riggs kernel: __common_interrupt: 7.55 No irq handler for vector
Dec 18 15:00:37 riggs kernel: __common_interrupt: 8.55 No irq handler for vector
Dec 18 15:00:37 riggs kernel: __common_interrupt: 9.55 No irq handler for vector
Dec 18 15:00:37 riggs kernel: __common_interrupt: 10.55 No irq handler for vector
Dec 18 15:00:37 riggs kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
Dec 18 15:00:45 riggs gdm-password][1031]: gkr-pam: unable to locate daemon control file
Dec 18 15:00:49 riggs sudo[1417]: pam_unix(sudo:auth): conversation failed
Dec 18 15:00:49 riggs sudo[1417]: pam_unix(sudo:auth): auth could not identify password for [riggs]
Dec 18 15:00:49 riggs sudo[1417]: pam_unix(sudo:auth): auth could not identify password for [riggs]
Dec 18 15:01:12 riggs pulseaudio[1129]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service ‘org.bluez’: timed out (service_start_timeout=25000ms)
Thank you very much, my friend, I really appreciate your help with this. I also found information on problems like this from a few years ago and some very recent ones, so I read about it in old forums of various sites, and it seems that it has happened on several occasions when there have been changes in the AMD bios to give support for new CPU’s.
I’ll wait a bit longer for a bios update from AMD to fix that, I can’t downgrade my bios anyway, at least not on an Asus Rog motherboard.