You are not logged in.
Hello all together,
on a new system with an asus prime x570-pro board on latest bios versions and all below ones I tried so far,
I get the message:
Jan 11 13:30:40 pk kernel: __common_interrupt: 1.55 No irq handler for vector
Jan 11 13:30:40 pk kernel: __common_interrupt: 2.55 No irq handler for vector
Jan 11 13:30:40 pk kernel: __common_interrupt: 3.55 No irq handler for vector
Jan 11 13:30:40 pk kernel: __common_interrupt: 4.55 No irq handler for vector
Jan 11 13:30:40 pk kernel: __common_interrupt: 5.55 No irq handler for vector
Jan 11 13:30:40 pk kernel: __common_interrupt: 6.55 No irq handler for vector
Jan 11 13:30:40 pk kernel: __common_interrupt: 7.55 No irq handler for vector
Jan 11 13:30:40 pk kernel: __common_interrupt: 8.55 No irq handler for vector
Jan 11 13:30:40 pk kernel: __common_interrupt: 9.55 No irq handler for vector
Jan 11 13:30:40 pk kernel: __common_interrupt: 10.55 No irq handler for vector
I tried to set a few kernel parameters, but to no avail, yet.
With acpi=noirq I cannot even boot (the error message there sound like coming from my nvidia card).
All other things I have read did not solve the issue.
Can anyone help out?
Asus Prime X570-Pro | Ryzen 9 3900X | Fractac Design Ion+ 660P | Thermaltake View 71 TG RGB+ |
Asus GTX 1660 Super | 2x 16GB GSkill DDR4 3600 16-19-19-39 | 1TB WD Black SN850 PCIe 4.0 SSD
Offline
Occurs on initialization of multi-core processors and has been around for a long time (used to be called differently) .
It appears to be harmless though.
https://unix.stackexchange.com/question … its-number has some background info.
Also https://bbs.archlinux.org/viewtopic.php?id=256227 for expereince of other users seeing this.
Last edited by Lone_Wolf (2021-01-11 13:11:41)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
Okay, thanks.
Is there any way to disable this though or shall I just wait until some future bios update might fix this?
Asus Prime X570-Pro | Ryzen 9 3900X | Fractac Design Ion+ 660P | Thermaltake View 71 TG RGB+ |
Asus GTX 1660 Super | 2x 16GB GSkill DDR4 3600 16-19-19-39 | 1TB WD Black SN850 PCIe 4.0 SSD
Offline
When I tried the newest BIOS for my board in December and had those error messages, I remember the messages were the most extreme loglevel "0" = "emerg" = emergency. You have to use "loglevel=0" to disable them. You won't see any errors anymore if you do that, so that might be a bit concerning.
Offline
Thank you - this is the only thing actually working!
But a bit concerning it is indeed.
Well, since I have fallback snapshots, I think I can leave it like that for now.
Thanks again!
Asus Prime X570-Pro | Ryzen 9 3900X | Fractac Design Ion+ 660P | Thermaltake View 71 TG RGB+ |
Asus GTX 1660 Super | 2x 16GB GSkill DDR4 3600 16-19-19-39 | 1TB WD Black SN850 PCIe 4.0 SSD
Offline