No irq handler error on boot

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.

Please help :heart:

Hi and welcome to the forum :+1:

Please see:


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

1 Like

Thanks for your reply! Apologies for not including that info.

inxi -Fazy output:

System:
  Kernel: 5.9.11-3-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.9-x86_64 
  root=UUID=0e6977a0-b23d-41cf-981e-eac5c3946c84 rw iommu=pt idle=nomwait 
  quiet apparmor=1 security=apparmor 
  resume=UUID=c8d67015-33ae-4f15-a517-fd090bf6290e udev.log_priority=3 
  Desktop: KDE Plasma 5.20.4 tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM 
  Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: Gigabyte model: B450 AORUS ELITE serial: <filter> 
  UEFI: American Megatrends v: F60c date: 10/29/2020 
CPU:
  Info: Quad Core model: AMD Ryzen 3 3200G with Radeon Vega Graphics bits: 64 
  type: MCP arch: Zen+ family: 17 (23) model-id: 18 (24) stepping: 1 
  microcode: 8108109 L2 cache: 2048 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 28759 
  Speed: 2170 MHz min/max: 1400/3600 MHz boost: enabled Core speeds (MHz): 
  1: 2038 2: 2914 3: 1231 4: 1231 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: 
  disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: AMD Picasso vendor: Gigabyte driver: amdgpu v: kernel 
  bus ID: 06:00.0 chip ID: 1002:15d8 
  Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: modesetting 
  alternate: ati,fbdev,vesa display ID: :0 screens: 1 
  Screen-1: 0 s-res: 1920x1080 s-dpi: 114 s-size: 427x240mm (16.8x9.4") 
  s-diag: 490mm (19.3") 
  Monitor-1: HDMI-1 res: 1920x1080 dpi: 93 size: 527x296mm (20.7x11.7") 
  diag: 604mm (23.8") 
  OpenGL: renderer: AMD Radeon Vega 8 Graphics (RAVEN DRM 3.39.0 
  5.9.11-3-MANJARO LLVM 11.0.0) 
  v: 4.6 Mesa 20.2.3 direct render: Yes 
Audio:
  Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel 
  v: kernel bus ID: 06:00.1 chip ID: 1002:15de 
  Device-2: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel 
  v: kernel bus ID: 06:00.6 chip ID: 1022:15e3 
  Sound Server: ALSA v: k5.9.11-3-MANJARO 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Gigabyte driver: r8169 v: kernel port: f000 bus ID: 03:00.0 
  chip ID: 10ec:8168 
  IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 670.70 GiB used: 33.10 GiB (4.9%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda vendor: Western Digital model: WDS240G2G0A-00JH30 
  size: 223.57 GiB block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
  serial: <filter> rev: 0400 scheme: GPT 
  ID-2: /dev/sdb vendor: Western Digital model: WDS480G2G0B-00EPW0 
  size: 447.13 GiB block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
  serial: <filter> rev: 0400 scheme: GPT 
Partition:
  ID-1: / raw size: 32.00 GiB size: 31.25 GiB (97.65%) used: 20.64 GiB (66.1%) 
  fs: ext4 dev: /dev/sda2 
  ID-2: /home raw size: 183.07 GiB size: 179.20 GiB (97.88%) 
  used: 12.46 GiB (7.0%) fs: ext4 dev: /dev/sda3 
Swap:
  Kernel: swappiness: 10 (default 60) cache pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/sda1 
Sensors:
  System Temperatures: cpu: 42.9 C mobo: N/A gpu: amdgpu temp: 42.0 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 237 Uptime: 5h 25m Memory: 13.61 GiB used: 3.66 GiB (26.9%) 
  Init: systemd v: 246 Compilers: gcc: 10.2.0 Packages: 1356 pacman: 1354 
  lib: 365 flatpak: 0 snap: 2 Shell: Zsh v: 5.8 running in: konsole 
  inxi: 3.1.08

Here are the errors, I included some stuff around them too:

[    0.115222] Performance Events: Fam17h+ core perfctr, AMD PMU driver.
[    0.115226] ... version:                0
[    0.115226] ... bit width:              48
[    0.115226] ... generic registers:      6
[    0.115227] ... value mask:             0000ffffffffffff
[    0.115227] ... max period:             00007fffffffffff
[    0.115227] ... fixed-purpose events:   0
[    0.115228] ... event mask:             000000000000003f
[    0.115266] rcu: Hierarchical SRCU implementation.
[    0.115432] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[    0.115640] smp: Bringing up secondary CPUs ...
[    0.115729] x86: Booting SMP configuration:
[    0.115730] .... node  #0, CPUs:        #1
**[    0.000000] __common_interrupt: 1.55 No irq handler for vector**
**[    0.116671]   #2**
**[    0.000000] __common_interrupt: 2.55 No irq handler for vector**
**[    0.116753]   #3**
**[    0.000000] __common_interrupt: 3.55 No irq handler for vector**
[    0.120048] smp: Brought up 1 node, 4 CPUs
[    0.120048] smpboot: Max logical packages: 8
[    0.120048] smpboot: Total of 4 processors activated (28757.25 BogoMIPS)
[    0.120581] devtmpfs: initialized
[    0.120581] x86/mm: Memory block size: 128MB
[    0.120747] PM: Registering ACPI NVS region [mem 0x0a200000-0x0a20afff] (45056 bytes)
[    0.120747] PM: Registering ACPI NVS region [mem 0x3c85d000-0x3ced0fff] (6766592 bytes)
[    0.120747] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns
[    0.120747] futex hash table entries: 8192 (order: 7, 524288 bytes, linear)
[    0.120747] pinctrl core: initialized pinctrl subsystem

Lets hope that info is enough for those with knowledge about the reason of those errors.
(This topic is not among my expertise :wink:)

add this
“noapic rcu_nocbs=0_07” to boot kernel

1 Like

Thank you it worked!

If you would, could you give a brief description of what is going on and what this fix does? ELI5 :grin:

1 Like

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. :+1:

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)

add this to boot
“noapic"

for sp5100-tco , blacklist this module driver

1 Like

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.

the new kernel 5.10 has fixed this for me!!!

1 Like

Thanks for the info, I going to try it :slight_smile:

Happy new year!

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