I get this message on boot
I don't know how it got there or how to remove it
From what I have read on other forums, this is not a problem assuming boot and operation therafter is OK. From websearch using "common_interrupt: 1.55 No irq handler for vector Ubuntu 22.04"
Do you have AMD components as this was mentioned in some reports I read.
Are you able to uodate your BIOS, as that is a possible way out of these mesages.
Yes it's AMD and I updated the bios not too long ago
Interesting post here:
I know I'm not that smart when it comes to linux, but I'm pretty sure I don't have this option Boot into single user mode: During boot
From the last post in the link you provided
I have now tried various suggestions and have not progressed, since it has no effect on the current boot of the system, I drop it, the PC works without problems
You can add loglevel=3 to your grub file, save the file, then update grub with sudo update-grub to inhibit low level warnings at boot.
1 Like
Hmm I don't know what I'm doing wrong, but I must have done something at some point.
My default grub looks like this now and I still get the same error
No... I do not think you have done it wrong. This is an iommu error that AMD has had persist for quite a while. It just seems as though the loglevel of that message is greater than 3, meaning you are still displayed it in spite of limiting the verbose log level warnings.
If you cannot ignore the brief error message (I cannot...), then you might try some different grub parameters handling iommu exchange.
You currently have "loglevel=3 quiet splash"
You can try "iommu=noforce quiet splash"
If that is not enough;
"iommu=soft quiet splash"
Or disable iommu:
"iommu=off quiet splash"
Some users have had luck using either the noapic or acpi=off parameters. APIC is Advanced Program-something Interrupt Controller (or something like that) and ACPI is Advanced Config for Power Interface. Some hardware firmware has out of bounds values which cause all kinds of different issues, so disabling either of these can halt those issues.
The consequence of disabling them is that a user will need to Hard Shutdown (Hold down the power button) to turn the computer off since the shutdown command will not work- APIC and ACPI allow that the server can turn itself off which it can no longer do if disabled.
Hopefully I did not inundate you with too much information in one post.
When you edit the grub file, please remember that each time, you must save the changes then run
sudo update-grub
for the changes to take effect on next reboot.
Now I have tried your suggestions and still have the same error message, but now I got new errors
I am totally confused I will admit.
The bootloader is probably stored in the Bios, so I think you might be able to reset the Bios? Am I completely crazy?
Were you using dconf-editor?
Can you detail what exact changes you made?
I do not think we need to worry about the bootloader at this time.
Yes, BIOS settings often have settings for APIC, IOMMU and APIC, though you can manage these with your Grub File just as easily.
I couldn't get into the bootloader using Right Shift or Left Shift, nor by using ESC.
So I searched online for a way to get in
I used terminal sudo -H gedit /etc/default/grub
Inside grub I tried each of your suggestions, refreshing grub after each try, but I stopped at "immou=noforce", I want a working power off button
I noticed in your screenshot earlier that your Grub Timeout is set to 0, which is the likely cause of this.
The iommu=off or the noapic parameters are the ones that can potentially cause the need for hard reboots.
The ones you tried still allow that message through?
ohh I didn't try those two, I'll just try those two. What should I set the timeout for?
Any value greater than three, really. I have mine set to 10 since ten seconds is plenty of time and I am not worried about my computer booting up ten seconds later than Warp Speed.
I changed the timeout to 5 and I tried immo=off and the error message disappeared.
Many thanks for your patience
1 Like
We have established the cause... AMD has a bug with iommo. Have you tested if your shutdown command or PowerOff button in the Application menu will shut down the computer with that parameter enabled?
Yes, everything works perfectly, thanks to you
1 Like