You are not logged in.

#1 2020-06-01 20:41:49

elParaguayo
Member
Registered: 2018-03-30
Posts: 43

Error message during boot: do_IRQ: 1.55 No irq handler for vector

I'm getting an error message during boot which is slightly annoying as I'm trying to run silent boot on my HTPC. The message says

do_IRQ: 1.55 No irq handler for vector

.

From what I can tell, this is an "emergency" level item, so setting the loglevel kernel parameter doesn't fix this (and I can't imagine it's good practice to hide emergency level items in any case).

I don't think it's causing any particular issues on my system as I can boot in fine but I would like to get to the bottom of this.

I've seen a couple of posts on this forum with a similar issue but the one marked [solved] suggested using "acpi=noirq" as a kernel parameter. I tried that and it didn't change the outcome.

Some relevant information about my system:

My motherboard is a Gigabyte GA-870A-UD3.
dmesg: http://ix.io/2o44
lspci -k: http://ix.io/2o3i
journalctl -b: http://ix.io/2o43

Any tips on how to resolve this would be greatly appreciated.

Offline

#2 2020-06-03 21:31:34

elParaguayo
Member
Registered: 2018-03-30
Posts: 43

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

I've tried to do some more digging on this but not sure if I'm getting anywhere.

Based on a particular google result, I recompiled the kernel with the "CONFIG_GENERIC_IRQ_DEBUGFS" kernel option enabled (first time doing that so good learning experience!) and then searched the debugfs for this particular vector:

[elpara@htpc ~]$ sudo ls /sys/kernel/debug/irq/irqs                           
0  10  12  14  16  18  2   24  26  28  3   31  33  35  5  7  9
1  11  13  15  17  19  22  25  27  29  30  32  34  4   6  8
[elpara@htpc ~]$ sudo grep "Vector" /sys/kernel/debug/irq/irqs/{0..35}
/sys/kernel/debug/irq/irqs/0:     Vector:    48
/sys/kernel/debug/irq/irqs/1:     Vector:    37
/sys/kernel/debug/irq/irqs/3:     Vector:     0
/sys/kernel/debug/irq/irqs/4:     Vector:     0
/sys/kernel/debug/irq/irqs/5:     Vector:     0
/sys/kernel/debug/irq/irqs/6:     Vector:     0
/sys/kernel/debug/irq/irqs/7:     Vector:    43
/sys/kernel/debug/irq/irqs/8:     Vector:    36
/sys/kernel/debug/irq/irqs/9:     Vector:    33
/sys/kernel/debug/irq/irqs/10:     Vector:     0
/sys/kernel/debug/irq/irqs/11:     Vector:     0
/sys/kernel/debug/irq/irqs/12:     Vector:     0
/sys/kernel/debug/irq/irqs/13:     Vector:     0
/sys/kernel/debug/irq/irqs/14:     Vector:    40
/sys/kernel/debug/irq/irqs/15:     Vector:    41
/sys/kernel/debug/irq/irqs/16:     Vector:    43
/sys/kernel/debug/irq/irqs/17:     Vector:    39
/sys/kernel/debug/irq/irqs/18:     Vector:    42
/sys/kernel/debug/irq/irqs/19:     Vector:    40
grep: /sys/kernel/debug/irq/irqs/20: No such file or directory
grep: /sys/kernel/debug/irq/irqs/21: No such file or directory
/sys/kernel/debug/irq/irqs/22:     Vector:    42
grep: /sys/kernel/debug/irq/irqs/23: No such file or directory
/sys/kernel/debug/irq/irqs/24:     Vector:    33
/sys/kernel/debug/irq/irqs/25:     Vector:    34
/sys/kernel/debug/irq/irqs/26:     Vector:    34
/sys/kernel/debug/irq/irqs/27:     Vector:    35
/sys/kernel/debug/irq/irqs/28:     Vector:    35
/sys/kernel/debug/irq/irqs/29:     Vector:    36
/sys/kernel/debug/irq/irqs/30:     Vector:    37
/sys/kernel/debug/irq/irqs/31:     Vector:    38
/sys/kernel/debug/irq/irqs/32:     Vector:    38
/sys/kernel/debug/irq/irqs/33:     Vector:    39
/sys/kernel/debug/irq/irqs/34:     Vector:    41
/sys/kernel/debug/irq/irqs/35:     Vector:    44

No mention of Vector 55. No idea where to go from here. Does anyone have any ideas?

Interestingly, I don't get this message on Xubuntu 16.04 (the old HTPC os I'm using) - can't recall off-hand which kernel version it's on.

Offline

#3 2020-06-03 22:28:52

loqs
Member
Registered: 2014-03-06
Posts: 12,091

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Does adding the kernel parameter nomsi have any effect?

Offline

#4 2020-06-04 05:25:38

elParaguayo
Member
Registered: 2018-03-30
Posts: 43

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

loqs wrote:

Does adding the kernel parameter nomsi have any effect?

Thanks loqs. I assume you mean:

pci=nomsi

which I saw in a couple of posts. If so, yes, I tried it as I had a similar line my lspci (see bottom of this post) and it didn't stop the error message.

I tried it before the custom kernel so I've just retried it again to see if there was any change to the irqs outputs. The main difference was that it reduced the number of them:

[elpara@htpc ~]$ sudo ls /sys/kernel/debug/irq/irqs
0  1  10  11  12  13  14  15  16  17  18  19  2  22  3  4  5  6  7  8  9
[elpara@htpc ~]$ sudo grep "Vector" /sys/kernel/debug/irq/irqs/{0..22}
/sys/kernel/debug/irq/irqs/0:     Vector:    48
/sys/kernel/debug/irq/irqs/1:     Vector:    34
/sys/kernel/debug/irq/irqs/3:     Vector:     0
/sys/kernel/debug/irq/irqs/4:     Vector:     0
/sys/kernel/debug/irq/irqs/5:     Vector:     0
/sys/kernel/debug/irq/irqs/6:     Vector:     0
/sys/kernel/debug/irq/irqs/7:     Vector:    37
/sys/kernel/debug/irq/irqs/8:     Vector:    33
/sys/kernel/debug/irq/irqs/9:     Vector:    33
/sys/kernel/debug/irq/irqs/10:     Vector:     0
/sys/kernel/debug/irq/irqs/11:     Vector:     0
/sys/kernel/debug/irq/irqs/12:     Vector:     0
/sys/kernel/debug/irq/irqs/13:     Vector:     0
/sys/kernel/debug/irq/irqs/14:     Vector:    36
/sys/kernel/debug/irq/irqs/15:     Vector:    36
/sys/kernel/debug/irq/irqs/16:     Vector:    38
/sys/kernel/debug/irq/irqs/17:     Vector:    35
/sys/kernel/debug/irq/irqs/18:     Vector:    34
/sys/kernel/debug/irq/irqs/19:     Vector:    35
grep: /sys/kernel/debug/irq/irqs/20: No such file or directory
grep: /sys/kernel/debug/irq/irqs/21: No such file or directory
/sys/kernel/debug/irq/irqs/22:     Vector:    37

dmesg output from this boot: http://ix.io/2oeD

Here's the lspci output (when booting with pci=nomsi) which shows the similar lines to the post suggesting this as a fix:

[elpara@htpc ~]$ sudo lspci -kv
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RX790 Host Bridge
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RX790 Host Bridge
        Flags: bus master, 66MHz, medium devsel, latency 32, NUMA node 0
        Memory at <ignored> (64-bit, non-prefetchable)
        Capabilities: [c4] HyperTransport: Slave or Primary Interface
        Capabilities: [40] HyperTransport: Retry Mode
        Capabilities: [54] HyperTransport: UnitID Clumping
        Capabilities: [9c] HyperTransport: #1a

00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RD790 PCI to PCI bridge (external gfx0 port A) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 18, NUMA node 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 0000c000-0000cfff [size=4K]
        Memory behind bridge: fb000000-fcffffff [size=32M]
        Prefetchable memory behind bridge: 00000000c0000000-00000000dfffffff [size=512M]
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Root Port (Slot-), MSI 00
        Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [b0] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RD790 PCI to PCI bridge (external gfx0 port A)
        Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Capabilities: [110] Virtual Channel
        Kernel driver in use: pcieport

00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (PCI express gpp port A) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
        I/O behind bridge: 0000b000-0000bfff [size=4K]
        Memory behind bridge: fda00000-fdafffff [size=1M]
        Prefetchable memory behind bridge: 00000000fd500000-00000000fd5fffff [size=1M]
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Root Port (Slot-), MSI 00
        Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [b0] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (PCI express gpp port A)
        Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Capabilities: [110] Virtual Channel
        Kernel driver in use: pcieport

00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (PCI express gpp port E) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0
        Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
        I/O behind bridge: 0000e000-0000efff [size=4K]
        Memory behind bridge: fd400000-fd4fffff [size=1M]
        Prefetchable memory behind bridge: 00000000fdf00000-00000000fdffffff [size=1M]
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Root Port (Slot-), MSI 00
        Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [b0] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (PCI express gpp port E)
        Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Capabilities: [110] Virtual Channel
        Kernel driver in use: pcieport

00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (PCI express gpp port F) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 18, NUMA node 0
        Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
        I/O behind bridge: 0000d000-0000dfff [size=4K]
        Memory behind bridge: fde00000-fdefffff [size=1M]
        Prefetchable memory behind bridge: 00000000fdd00000-00000000fddfffff [size=1M]
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Root Port (Slot-), MSI 00
        Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [b0] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (PCI express gpp port F)
        Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Capabilities: [110] Virtual Channel
        Kernel driver in use: pcieport

00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] (rev 40) (prog-if 01 [AHCI 1.0])
        Subsystem: Gigabyte Technology Co., Ltd GA-MA770-DS3rev2.0 Motherboard
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 19, NUMA node 0
        I/O ports at ff00 [size=8]
        I/O ports at fe00 [size=4]
        I/O ports at fd00 [size=8]
        I/O ports at fc00 [size=4]
        I/O ports at fb00 [size=16]
        Memory at fe02f000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [50] MSI: Enable- Count=1/4 Maskable- 64bit+
        Capabilities: [70] SATA HBA v1.0
        Capabilities: [a4] PCI Advanced Features
        Kernel driver in use: ahci
        Kernel modules: ahci

00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller (prog-if 10 [OHCI])
        Subsystem: Gigabyte Technology Co., Ltd SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18, NUMA node 0
        Memory at fe02e000 (32-bit, non-prefetchable) [size=4K]
        Kernel driver in use: ohci-pci
        Kernel modules: ohci_pci

00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller (prog-if 20 [EHCI])
        Subsystem: Gigabyte Technology Co., Ltd SB7x0/SB8x0/SB9x0 USB EHCI Controller
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17, NUMA node 0
        Memory at fe02d000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [c0] Power Management version 2
        Capabilities: [e4] Debug port: BAR=1 offset=00e0
        Kernel driver in use: ehci-pci
        Kernel modules: ehci_pci

00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller (prog-if 10 [OHCI])
        Subsystem: Gigabyte Technology Co., Ltd SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18, NUMA node 0
        Memory at fe02c000 (32-bit, non-prefetchable) [size=4K]
        Kernel driver in use: ohci-pci
        Kernel modules: ohci_pci

00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller (prog-if 20 [EHCI])
        Subsystem: Gigabyte Technology Co., Ltd SB7x0/SB8x0/SB9x0 USB EHCI Controller
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17, NUMA node 0
        Memory at fe02b000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [c0] Power Management version 2
        Capabilities: [e4] Debug port: BAR=1 offset=00e0
        Kernel driver in use: ehci-pci
        Kernel modules: ehci_pci

00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 42)
        Flags: 66MHz, medium devsel, NUMA node 0
        Kernel modules: i2c_piix4, sp5100_tco

00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller (rev 40) (prog-if 8a [ISA Compatibility mode controller, supports both channels switched to PCI native mode, supports bus mastering])
        Subsystem: Gigabyte Technology Co., Ltd SB7x0/SB8x0/SB9x0 IDE Controller
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17, NUMA node 0
        Memory at 000001f0 (32-bit, non-prefetchable) [virtual] [size=8]
        Memory at 000003f0 (type 3, non-prefetchable) [virtual]
        Memory at 00000170 (32-bit, non-prefetchable) [virtual] [size=8]
        Memory at 00000370 (type 3, non-prefetchable) [virtual]
        I/O ports at fa00 [virtual] [size=16]
        Kernel driver in use: pata_atiixp
        Kernel modules: pata_atiixp, pata_acpi, ata_generic

00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40)
        Subsystem: Gigabyte Technology Co., Ltd SBx00 Azalia (Intel HDA)
        Flags: bus master, slow devsel, latency 32, IRQ 16, NUMA node 0
        Memory at fe024000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel

00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller
        Flags: bus master, 66MHz, medium devsel, latency 0, NUMA node 0

00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40) (prog-if 01 [Subtractive decode])
        Flags: bus master, VGA palette snoop, 66MHz, medium devsel, latency 64, NUMA node 0
        Bus: primary=00, secondary=05, subordinate=05, sec-latency=64
        I/O behind bridge: 0000a000-0000afff [size=4K]
        Memory behind bridge: fdc00000-fdcfffff [size=1M]
        Prefetchable memory behind bridge: fdb00000-fdbfffff [size=1M]

00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller (prog-if 10 [OHCI])
        Subsystem: Gigabyte Technology Co., Ltd SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18, NUMA node 0
        Memory at fe02a000 (32-bit, non-prefetchable) [size=4K]
        Kernel driver in use: ohci-pci
        Kernel modules: ohci_pci

00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0
        Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
        I/O behind bridge: 00009000-00009fff [size=4K]
        Memory behind bridge: fd900000-fd9fffff [size=1M]
        Prefetchable memory behind bridge: 00000000fd800000-00000000fd8fffff [size=1M]
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Root Port (Slot+), MSI 00
        Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [b0] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0)
        Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Kernel driver in use: pcieport

00:15.1 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0
        Bus: primary=00, secondary=07, subordinate=07, sec-latency=0
        I/O behind bridge: 00008000-00008fff [size=4K]
        Memory behind bridge: fd700000-fd7fffff [size=1M]
        Prefetchable memory behind bridge: 00000000fd600000-00000000fd6fffff [size=1M]
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Root Port (Slot+), MSI 00
        Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [b0] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1)
        Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Kernel driver in use: pcieport

00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller (prog-if 10 [OHCI])
        Subsystem: Gigabyte Technology Co., Ltd SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18, NUMA node 0
        Memory at fe029000 (32-bit, non-prefetchable) [size=4K]
        Kernel driver in use: ohci-pci
        Kernel modules: ohci_pci

00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller (prog-if 20 [EHCI])
        Subsystem: Gigabyte Technology Co., Ltd SB7x0/SB8x0/SB9x0 USB EHCI Controller
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17, NUMA node 0
        Memory at fe028000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [c0] Power Management version 2
        Capabilities: [e4] Debug port: BAR=1 offset=00e0
        Kernel driver in use: ehci-pci
        Kernel modules: ehci_pci

00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration
        Flags: fast devsel, NUMA node 0
        Capabilities: [80] HyperTransport: Host or Secondary Interface

00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map
        Flags: fast devsel, NUMA node 0

00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller
        Flags: fast devsel, NUMA node 0

00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control
        Flags: fast devsel, NUMA node 0
        Capabilities: [f0] Secure device <?>
        Kernel driver in use: k10temp
        Kernel modules: k10temp

00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control
        Flags: fast devsel, NUMA node 0

01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) (prog-if 00 [VGA controller])
        Subsystem: Micro-Star International Co., Ltd. [MSI] GT218 [GeForce 210]
        Flags: bus master, fast devsel, latency 0, IRQ 18, NUMA node 0
        Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
        Memory at c0000000 (64-bit, prefetchable) [size=256M]
        Memory at de000000 (64-bit, prefetchable) [size=32M]
        I/O ports at cf00 [size=128]
        Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
        Capabilities: [60] Power Management version 3
        Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [78] Express Endpoint, MSI 00
        Capabilities: [b4] Vendor Specific Information: Len=14 <?>
        Capabilities: [100] Virtual Channel
        Capabilities: [128] Power Budgeting <?>
        Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
        Kernel driver in use: nouveau
        Kernel modules: nouveau

01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)
        Subsystem: Micro-Star International Co., Ltd. [MSI] High Definition Audio Controller
        Flags: bus master, fast devsel, latency 0, IRQ 18, NUMA node 0
        Memory at fcffc000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [60] Power Management version 3
        Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [78] Express Endpoint, MSI 00
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel

02:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
        Subsystem: Device 6280:0011
        Flags: bus master, fast devsel, latency 0, IRQ 3, NUMA node 0
        Memory at fda00000 (64-bit, non-prefetchable) [size=1M]
        Capabilities: [40] MSI: Enable- Count=1/32 Maskable- 64bit+
        Capabilities: [50] Express Endpoint, MSI 00
        Capabilities: [74] Power Management version 2
        Capabilities: [80] Vendor Specific Information: Len=50 <?>
        Capabilities: [100] Vendor Specific Information: ID=0000 Rev=0 Len=088 <?>
        Kernel modules: saa716x_tbs_dvb

03:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03) (prog-if 30 [XHCI])
        Subsystem: Gigabyte Technology Co., Ltd uPD720200 USB 3.0 Host Controller
        Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0
        Memory at fd4fe000 (64-bit, non-prefetchable) [size=8K]
        Capabilities: [50] Power Management version 3
        Capabilities: [70] MSI: Enable- Count=1/8 Maskable- 64bit+
        Capabilities: [90] MSI-X: Enable- Count=8 Masked-
        Capabilities: [a0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number ff-ff-ff-ff-ff-ff-ff-ff
        Capabilities: [150] Latency Tolerance Reporting
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci

04:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 03) (prog-if 01 [AHCI 1.0])
        Subsystem: Gigabyte Technology Co., Ltd Motherboard
        Flags: bus master, fast devsel, latency 0, IRQ 18, NUMA node 0
        Memory at fdefe000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [68] Power Management version 2
        Capabilities: [50] Express Legacy Endpoint, MSI 01
        Kernel driver in use: ahci
        Kernel modules: ahci

04:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 03) (prog-if 85 [PCI native mode-only controller, supports bus mastering])
        Subsystem: Gigabyte Technology Co., Ltd Motherboard
        Flags: bus master, fast devsel, latency 0, IRQ 19, NUMA node 0
        I/O ports at df00 [size=8]
        I/O ports at de00 [size=4]
        I/O ports at dd00 [size=8]
        I/O ports at dc00 [size=4]
        I/O ports at db00 [size=16]
        Capabilities: [68] Power Management version 2
        Kernel driver in use: pata_jmicron
        Kernel modules: pata_jmicron, pata_acpi, ata_generic

05:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI])
        Subsystem: Gigabyte Technology Co., Ltd Motherboard
        Flags: bus master, medium devsel, latency 32, IRQ 22, NUMA node 0
        Memory at fdcff000 (32-bit, non-prefetchable) [size=2K]
        Memory at fdcf8000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [44] Power Management version 2
        Kernel driver in use: firewire_ohci
        Kernel modules: firewire_ohci

06:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02) (prog-if 01 [AHCI 1.0])
        Subsystem: Gigabyte Technology Co., Ltd Motherboard
        Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0
        Memory at fd9fe000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [68] Power Management version 2
        Capabilities: [50] Express Legacy Endpoint, MSI 01
        Kernel driver in use: ahci
        Kernel modules: ahci

06:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02) (prog-if 85 [PCI native mode-only controller, supports bus mastering])
        Subsystem: Gigabyte Technology Co., Ltd Motherboard
        Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0
        I/O ports at 9f00 [size=8]
        I/O ports at 9e00 [size=4]
        I/O ports at 9d00 [size=8]
        I/O ports at 9c00 [size=4]
        I/O ports at 9b00 [size=16]
        Capabilities: [68] Power Management version 2
        Kernel driver in use: pata_jmicron
        Kernel modules: pata_jmicron, pata_acpi, ata_generic

07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
        Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet
        Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0
        I/O ports at 8e00 [size=256]
        Memory at fd6ff000 (64-bit, prefetchable) [size=4K]
        Memory at fd6f8000 (64-bit, prefetchable) [size=16K]
        Expansion ROM at fd700000 [virtual] [disabled] [size=128K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 01
        Capabilities: [ac] MSI-X: Enable- Count=4 Masked-
        Capabilities: [cc] Vital Product Data
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 03-00-00-00-68-4c-e0-00
        Kernel driver in use: r8169
        Kernel modules: r8169

A couple of differences to that post, my board isn't using a VIA chipset and I have the line:

Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+

where they have

Capabilities: [88] HyperTransport: MSI Mapping Enable- Fixed+

I don't know how important the +/- is after the Enable.

Offline

#5 2020-06-05 07:49:08

elParaguayo
Member
Registered: 2018-03-30
Posts: 43

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

I've also tried latest linux kernel (5.6.15.arch1-1) but still get the same message.

In terms of debugging this, is it worth unplugging devices (USB devices, TV Tuner PCI card) to see if that stops the messages and, if so, reconnecting one by one to see which triggers this error?

On the plus side, it doesn't seem to cause any issue to my system so far although, admittedly, it's not doing much at the moment (just booting to login prompt) as I'm gradually installing the bits I need for the HTPC.

Offline

#6 2020-06-05 16:57:11

elParaguayo
Member
Registered: 2018-03-30
Posts: 43

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

For those that are interested in this, I found a thread on the Linux kernel mailing list about this issue. The error seems to arise when a multiple CPU cores are initalised (in my case, the 1 before the .55 is for the second core). Sadly the majority of the discussion in that thread is way beyond my understanding but the general gist seems to be that this is a harmless message due to some AMD or BIOS issue.

elParaguayo wrote:

Interestingly, I don't get this message on Xubuntu 16.04 (the old HTPC os I'm using) - can't recall off-hand which kernel version it's on.

Turns out, this isn't quite true... From another thread on LKML it looks like the error was previously reported as

spurious 8259A interrupt: IRQ7.

and, indeed, if I search dmesg on my HTPC (on Xubuntu 16.04 kernel: 4.4.0-131-generic #157-Ubuntu) I do have that exact line

elpara@HTPC:~$ dmesg | grep spurious
[    0.000000] spurious 8259A interrupt: IRQ7.

Interestingly, that message is loglevel 7 on 4.4.0-131

Fri 2020-06-05 07:47:00.677205 BST [s=4446acb3f56c4f308bd950538434062c;i=a3;b=5d0c311ef8004b0eac887fc4bca39aa2;m=
    _BOOT_ID=5d0c311ef8004b0eac887fc4bca39aa2
    _MACHINE_ID=29d992c72fcb47678b52d1b3ff5a47b0
    _HOSTNAME=HTPC
    _SOURCE_MONOTONIC_TIMESTAMP=0
    _TRANSPORT=kernel
    SYSLOG_FACILITY=0
    SYSLOG_IDENTIFIER=kernel
    PRIORITY=7
    MESSAGE=spurious 8259A interrupt: IRQ7.

but is now loglevel 0 on latest kernels. That's quite an escalation.

So, I suspect there's no quick fix for the message and it's safe to ignore. I'd just prefer not to see it at all.


EDIT: Apologies - just realised, I should have edited previous post rather than post this as new one.

Last edited by elParaguayo (2020-06-05 16:57:54)

Offline

#7 2020-06-05 18:13:15

loqs
Member
Registered: 2014-03-06
Posts: 12,091

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

You could try the proposed patch from https://lkml.org/lkml/2019/3/7/212

Offline

#8 2020-06-05 18:13:21

Gosi
Member
From: Vienna, Austria
Registered: 2010-02-25
Posts: 75

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Jun 01 19:55:49 htpc kernel: DMI: Gigabyte Technology Co., Ltd. GA-870A-UD3/GA-870A-UD3, BIOS F4 11/10/2010

There is an F5 version available, but i doubt it will help.

Offline

#9 2020-06-05 18:37:19

elParaguayo
Member
Registered: 2018-03-30
Posts: 43

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

loqs wrote:

You could try the proposed patch from https://lkml.org/lkml/2019/3/7/212

Yes, although that post says the patch didn't work so I wouldn't hold out much hope. Also, it took about 5 hours to compile the kernel last time so I'm not desperate to do it again but no harm in trying.

Gosi wrote:

There is an F5 version available, but i doubt it will help.

I doubt it too! It's about 9 years old and this issue is still around. I'm also not desperate to update the BIOS unless I really have to.

Offline

#10 2020-06-05 18:44:38

loqs
Member
Registered: 2014-03-06
Posts: 12,091

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

elParaguayo wrote:

Also, it took about 5 hours to compile the kernel last time so I'm not desperate to do it again but no harm in trying.

Have you enabled parallel compilation?  To reduce the compile time?

Offline

#11 2020-06-05 19:26:45

elParaguayo
Member
Registered: 2018-03-30
Posts: 43

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

loqs wrote:
elParaguayo wrote:

Also, it took about 5 hours to compile the kernel last time so I'm not desperate to do it again but no harm in trying.

Have you enabled parallel compilation?  To reduce the compile time?

Sadly, yes. I used the nproc line from that link. Not sure how long it would have taken without it.

It's fine, I can always leave it running overnight.

Offline

#12 2020-06-06 09:10:26

elParaguayo
Member
Registered: 2018-03-30
Posts: 43

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Well, this compiled much quicker than last time (I just changed the file in the source folder and rebuilt with makepkg (using --noextract)).

The message was still there on boot.

I can hide it if I change loglevel kernel parameter to 0 but that, for some reason, stops plymouth working (when the error message was on the screen, you could see the resolution change before plymouth started but that's not happening now). I'll have a little play with the parameters but may start a new thread on that.

However, for this particular issue, it feels like we've gone as far as we can. Appreciate the support.

Offline

#13 2020-06-06 14:13:34

loqs
Member
Registered: 2014-03-06
Posts: 12,091

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

You could contact upstream see if they have any other suggestions for resolving the issue in the kernel or if it is just considered a firmware bug.

Offline

#14 2020-06-24 12:06:10

mabod
Member
Registered: 2016-09-09
Posts: 2

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Although I am a Manjaro user I want to mention here that just today this issue popped up with the BIOS upgrade that I did today. I installed new beta BIOS 7C37v193(Beta version) for my MSI MPG X570 GAMING EDGE WIFI board. I did not have any errors or issues with the previous beta 7C37v192(Beta version) which I was running for several weeks now.

This new BIOS 7C37v193(Beta version) is coming with "Updated AMD AGESA ComboAm4v2PI 1.0.0.2" as the only change and the messages I get with that are:

Jun 24 11:29:29 manjaro kernel: .... node  #0, CPUs:        #1
Jun 24 11:29:29 manjaro kernel: do_IRQ: 1.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #2
Jun 24 11:29:29 manjaro kernel: do_IRQ: 2.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #3
Jun 24 11:29:29 manjaro kernel: do_IRQ: 3.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #4
Jun 24 11:29:29 manjaro kernel: do_IRQ: 4.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #5
Jun 24 11:29:29 manjaro kernel: do_IRQ: 5.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #6
Jun 24 11:29:29 manjaro kernel: do_IRQ: 6.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #7
Jun 24 11:29:29 manjaro kernel: do_IRQ: 7.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #8
Jun 24 11:29:29 manjaro kernel: do_IRQ: 8.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #9
Jun 24 11:29:29 manjaro kernel: do_IRQ: 9.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:  #10
Jun 24 11:29:29 manjaro kernel: do_IRQ: 10.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:  #11 #12 #13 #14 #15

I seee this with kernel 5.4.48 and 5.7.5 with a  Ryzen 7 3700X.

kernel command line parameter "pci=nomsi,noaer" does not help. It is not booting with nomsi and noaer alone makes no difference.

Offline

#15 2020-06-24 20:40:53

jarek1983
Member
Registered: 2020-05-23
Posts: 4

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

mabod wrote:

Although I am a Manjaro user I want to mention here that just today this issue popped up with the BIOS upgrade that I did today. I installed new beta BIOS 7C37v193(Beta version) for my MSI MPG X570 GAMING EDGE WIFI board. I did not have any errors or issues with the previous beta 7C37v192(Beta version) which I was running for several weeks now.

This new BIOS 7C37v193(Beta version) is coming with "Updated AMD AGESA ComboAm4v2PI 1.0.0.2" as the only change and the messages I get with that are:

Jun 24 11:29:29 manjaro kernel: .... node  #0, CPUs:        #1
Jun 24 11:29:29 manjaro kernel: do_IRQ: 1.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #2
Jun 24 11:29:29 manjaro kernel: do_IRQ: 2.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #3
Jun 24 11:29:29 manjaro kernel: do_IRQ: 3.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #4
Jun 24 11:29:29 manjaro kernel: do_IRQ: 4.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #5
Jun 24 11:29:29 manjaro kernel: do_IRQ: 5.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #6
Jun 24 11:29:29 manjaro kernel: do_IRQ: 6.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #7
Jun 24 11:29:29 manjaro kernel: do_IRQ: 7.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #8
Jun 24 11:29:29 manjaro kernel: do_IRQ: 8.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:   #9
Jun 24 11:29:29 manjaro kernel: do_IRQ: 9.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:  #10
Jun 24 11:29:29 manjaro kernel: do_IRQ: 10.55 No irq handler for vector
Jun 24 11:29:29 manjaro kernel:  #11 #12 #13 #14 #15

I seee this with kernel 5.4.48 and 5.7.5 with a  Ryzen 7 3700X.

kernel command line parameter "pci=nomsi,noaer" does not help. It is not booting with nomsi and noaer alone makes no difference.

Hello,

Don't mean to hijack the thread, but I just updated bios on my MSI x570 MB (with Ryzen 3800X) to version 7C35v196(beta) and started to get the same errors (was running previous beta for a couple of weeks without this error present, but with random crashes due to mce microcode errors and thought that I would try this new version).

 uname -r
5.7.5-zen1-1-zen 

journalctl -p 3 -b

cze 24 22:18:50 archlinux kernel: do_IRQ: 1.55 No irq handler for vector
cze 24 22:18:50 archlinux kernel: do_IRQ: 2.55 No irq handler for vector
cze 24 22:18:50 archlinux kernel: do_IRQ: 3.55 No irq handler for vector
cze 24 22:18:50 archlinux kernel: do_IRQ: 4.55 No irq handler for vector
cze 24 22:18:50 archlinux kernel: do_IRQ: 5.55 No irq handler for vector
cze 24 22:18:50 archlinux kernel: do_IRQ: 6.55 No irq handler for vector
cze 24 22:18:50 archlinux kernel: do_IRQ: 7.55 No irq handler for vector
cze 24 22:18:50 archlinux kernel: do_IRQ: 8.55 No irq handler for vector
cze 24 22:18:50 archlinux kernel: do_IRQ: 9.55 No irq handler for vector
cze 24 22:18:50 archlinux kernel: do_IRQ: 10.55 No irq handler for vector
cze 24 22:18:50 archlinux kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP8._DSM], AE_ALREADY_EXISTS (20200326/dswload2-326)
cze 24 22:18:50 archlinux kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200326/psobject-220)

Best regards!
Jarek

Offline

#16 2020-06-24 23:01:33

GeorgeJP
Member
From: Czech Republic
Registered: 2020-01-28
Posts: 44

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

I have these messages for years.

You can add kernel command line parameter

apic=verbose

to see some additional info in dmesg:

[    0.241131] smp: Bringing up secondary CPUs ...
[    0.241131] x86: Booting SMP configuration:
[    0.241131] .... node  #0, CPUs:      #1
[    0.000451] masked ExtINT on CPU#1
[    0.000451] do_IRQ: 1.55 No irq handler for vector
[    0.241131]  #2
[    0.000451] masked ExtINT on CPU#2
[    0.000451] do_IRQ: 2.55 No irq handler for vector
[    0.241131]  #3
[    0.000451] masked ExtINT on CPU#3
[    0.000451] do_IRQ: 3.55 No irq handler for vector
[    0.241131] smp: Brought up 1 node, 4 CPUs
[    0.241131] smpboot: Max logical packages: 1
[    0.241131] smpboot: Total of 4 processors activated (16774.87 BogoMIPS)

Unfortunalelly there is no new firmware for my NB, solutions like pci=nomsi,noaer and some others, which I found, are not functional on my system.

Interesting thing is, that some (approx. 1 out of 100) boots are performed OK and all cores get irq handler. If I compare dmesg's, I can't see any significant difference.

Computer should work OK, only silent boot is destroyed with these annoying messages. I think, that kernel guys have more serious things to solve, so workaround for this issue will not be available.

Offline

#17 2020-07-02 22:18:43

slip
Member
Registered: 2019-09-09
Posts: 7

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

mabod wrote:

Although I am a Manjaro user I want to mention here that just today this issue popped up with the BIOS upgrade that I did today.

I did the same thing on my ROG Strix X570-E Gaming with the 3950x and I'm experiencing the same thing now as well. Hopefully something else comes up to shed a little more light on it beyond just accepting it.

Last edited by slip (2020-07-02 22:19:47)

Offline

#18 2020-07-28 16:38:58

gururise
Member
Registered: 2011-11-03
Posts: 28

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

[    0.704073] smp: Bringing up secondary CPUs ...
[    0.704130] x86: Booting SMP configuration:
[    0.704130] .... node  #0, CPUs:        #1
[    0.316906] do_IRQ: 1.55 No irq handler for vector
[    0.706200]   #2
[    0.316906] do_IRQ: 2.55 No irq handler for vector
[    0.708310]   #3
[    0.316906] do_IRQ: 3.55 No irq handler for vector
[    0.709592]   #4
[    0.316906] do_IRQ: 4.55 No irq handler for vector
[    0.712926]   #5
[    0.316906] do_IRQ: 5.55 No irq handler for vector
[    0.715088]   #6
[    0.316906] do_IRQ: 6.55 No irq handler for vector
[    0.716263]   #7
[    0.316906] do_IRQ: 7.55 No irq handler for vector
[    0.719593]   #8
[    0.316906] do_IRQ: 8.55 No irq handler for vector
[    0.721745]   #9
[    0.316906] do_IRQ: 9.55 No irq handler for vector
[    0.722924]  #10
[    0.316906] do_IRQ: 10.55 No irq handler for vector
[    0.726267]  #11 #12 #13 #14 #15 #16 #17 #18 #19 #20 #21 #22 #23
[    0.755078] smp: Brought up 1 node, 24 CPUs

Same thing happening on my new Ryzen 3900X and Gigabyte Aorus Ultra (Latest F20 bios) motherboard. Running KERNEL 5.7.10-arch1-1

Offline

#19 2020-07-31 13:40:26

ottojimb
Member
Registered: 2020-07-31
Posts: 1

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Same here with Ryzen 3900X and X570 Aorus Elite Wifi, Kernel: 5.7.11-arch1-1. It was with the latest bios for the MOBO (F20), when I downgrade to F11 it doesn't happened again.

Offline

#20 2020-08-03 23:40:25

skeltonmicro
Member
Registered: 2020-03-28
Posts: 5

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

gururise wrote:

Same thing happening on my new Ryzen 3900X and Gigabyte Aorus Ultra (Latest F20 bios) motherboard. Running KERNEL 5.7.10-arch1-1

On Aorus Elite x570 and I'm having the same issue on the same bios update. Didn't have an issue until then.

Offline

#21 2020-08-05 01:40:46

alsomesauce
Member
Registered: 2020-08-05
Posts: 1

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Getting the same thing since I updated to F20 on Gigabyte X570 Xtreme. 3950x if it matters but it looks like it doesn't.  That was the BIOS update for AMD AGESA ComboV2 1.0.0.2.

Got a way more stable memory OC out of that BIOS version though so I'll just live with it I guess.

Offline

#22 2020-08-05 22:46:41

gpisic
Member
Registered: 2020-06-16
Posts: 7

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Can confirm, same error appears for me too after BIOS update to AMD AGESA ComboAm4v2PI 1.0.0.2 (7C37vA8) on my MSI MPG X570 GAMING PLUS mobo. Before that i never saw that error.

Offline

#23 2020-08-08 12:24:28

simonpedro
Member
Registered: 2020-08-08
Posts: 1

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Just to add more variety to the bug, the same here on a vanilla debian 10.5 on my old lenovo g475 desktop. No problem at all, boot time has been increased by a few seconds

Offline

#24 2020-08-08 17:06:30

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 17,513

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Jesus wept.  Enough of the "Me too" posts.   We believe you, this is happening.   So, dig into the problem -- do some bisections -- isolate it.  Or wait.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#25 2020-08-11 22:30:54

GeorgeJP
Member
From: Czech Republic
Registered: 2020-01-28
Posts: 44

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Most relevant description of problem is probably here : https://unix.stackexchange.com/question … its-number
File arch/x86/kernel/irq.c is changed in kernel 5.8 and error message now looks like this:

__common_interrupt: 1.55 No irq handler for vector

It looks, that some work is in progress ...

Offline

Board footer

Powered by FluxBB