You are not logged in.
The message changed as a result of code clean up see https://github.com/torvalds/linux/commi … 41b1382eb4
Offline
Does anyone got rid of those messages?
I found no solution on my x570-e-gaming + 3950x Ryzen.
Regards
Offline
I created a workaround for this... I changed line 254 in arch/x86/kernel/irq.c from:
pr_emerg_ratelimited("%s: %d.%u No irq handler for vector\n",
to
pr_err_ratelimited("%s: %d.%u No irq handler for vector\n",
That way using loglevel=3 on the kernel cmdline you don't see this silly error message.
It may not be the best or preferred way of doing things, but it works for me. And it's still sending an error message, just not as an emergency error message.
And Gonzo2028, this is on my MSI x570 Edge with 3900x.
Here's a patch file:
https://mudz.org/no-irq-handler-for-vector.patch
Last edited by skeetre (2020-10-09 14:59:54)
Offline
Hi,
My motherboard it's a GIGABYTE X570 I AORUS PRO WIFI (rev. 1.0).
I have the same error with latest update (F20, F21, F30) :
F30 9,61 MB 2020/09/15 Update AMD AGESA ComboV2 1.0.8.1 for AMD Ryzen 5000 processors support
F21 9,49 MB 2020/08/20 Improve memory compatibility
F20 9,49 MB 2020/07/10 Update AMD AGESA ComboV2 1.0.0.2 for 3rd Gen AMD Ryzen XT series processors and New Gen AMD Ryzen with Radeon Graphics processors support
Fix AMD security vulnerabilities for SMM Callout Privilege Escalation
Error message :
do_IRQ: 1.55 No irq handler for vector
do_IRQ: 2.55 No irq handler for vector
do_IRQ: 3.55 No irq handler for vector
do_IRQ: 4.55 No irq handler for vector
do_IRQ: 5.55 No irq handler for vector
do_IRQ: 8.55 No irq handler for vector
do_IRQ: 9.55 No irq handler for vector
do_IRQ: 10.55 No irq handler for vector
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP8._DSM], AE_ALREADY_EXISTS (20200110/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200110/psobject-220)
Offline
Ok,
So I have been experiencing the same error with almost the same board. I actually have the Gigabyte X570 Aorus Elite Rev 1.0. Running the BIOS version F30 right now. I don't know anything to help this right now but it seems to me that it is a regression since the F11 version of the BIOS. I forwarded this information in a support request to Gigabyte. Maybe they will do something about it, but as with most support requests like this it is just a shot in the dark. It could take 7 days according to the site. So if there is no answer in the following week we know our answer.
Offline
I had the same error on MSI X570 MEG ACE. Disabling IOMMU in the BIOS gets rid of the message for me.
Offline
Hey,
I'm seeing the same message after upgrading the BIOS (f11 -> f30) on an X570 Aorus Elite. Not experiencing any additional issues.
Tried disabling IOMMU, but no dice.
Last edited by greenleafvolatile (2020-11-18 10:24:20)
Offline
I have newest BIOS containing AGESA ComboAm4v2PI 1.1.0.0 Patch C. Maybe that's why we have different results.
You could try disabling CPU Virtualization alltogether if you don't need it? See if that stops the error message.
Offline
I had the same error on MSI X570 MEG ACE. Disabling IOMMU in the BIOS gets rid of the message for me.
Gigabyte Aorus Elite B550, disabling IOMMU also get rid of this message and boot is 10-15 seconds faster.
Offline
I have gotten a response to my ticket at gigabyte. Looks like they are working on it.
Dear customer,
Thank you for emailing GIGABYTE.
We would like to help you on this issue.We are looking into the issue and will come back to you ASAP after figuring it out clearly.
Thanks for your patience.
Regards
GIGABYTE Team
Offline
I have an MSI B450 TOMAHAWK MAX ATX AM4, but disabling IOMMU didn't work.
"I even found myself driving by convenience stores... that weren't on the way home."
Offline
I have gotten a response too by Gigabyte support :
Dear customer,
Our team can duplicated the problem.
Needs to be fixed by AMD.
We will reflect this issue to AMD
Thank you for emailing GIGABYTE.
We would like to help you on this issue.
We are looking into the issue and will come back to you ASAP after figuring it out clearly.
Thanks for your patience.
Regards
GIGABYTE Team
Offline
I try the latest bios version of my GIGABYTE X570 I AORUS PRO WIFI (rev. 1.0) motherboard (F31e 2020/10/29 - AMD AGESA ComboV2 1.1.0.0 C).
And the errors still here.
[ 0.000000] __common_interrupt: 1.55 No irq handler for vector
[ 0.113261] #2
[ 0.000000] __common_interrupt: 2.55 No irq handler for vector
[ 0.113419] #3
[ 0.000000] __common_interrupt: 3.55 No irq handler for vector
[ 0.116748] #4
[ 0.000000] __common_interrupt: 4.55 No irq handler for vector
[ 0.118888] #5
[ 0.000000] __common_interrupt: 5.55 No irq handler for vector
[ 0.120078] #6
[ 0.000000] __common_interrupt: 6.55 No irq handler for vector
[ 0.123415] #7
[ 0.000000] __common_interrupt: 7.55 No irq handler for vector
[ 0.125552] #8
[ 0.000000] __common_interrupt: 8.55 No irq handler for vector
[ 0.126772] #9
[ 0.000000] __common_interrupt: 9.55 No irq handler for vector
[ 0.130081] #10
[ 0.000000] __common_interrupt: 10.55 No irq handler for vector
After that, I tested to disable IOMMU.
And it work. Errors do not appear anymore.
SVM option if disabled or enabled, it does not affect the problem.
It is only if IOMMU is Auto or Enabled, the issue appear.
Last edited by SupKurtJ (2020-11-21 10:58:48)
Offline
Hey,
I'm seeing the same message after upgrading the BIOS (f11 -> f30) on an X570 Aorus Elite. Not experiencing any additional issues.
Tried disabling IOMMU, but no dice.
Try a bios with the latest AMD AGESA ComboV2 1.1.0.0 C like the F31e or more if available. And tell me if the issue still here, after disabling IOMMU on the bios of course.
Last edited by SupKurtJ (2020-11-21 10:29:29)
Offline
Hi,
I have a Gigabyte A520M H with a R3 3100.
I have the same problem with the latest BIOS (F11g [with AGESA 1.1.0.0 C]).
Unable to get rid of it with IOMMU disabled and/or "pci=noaer pci=nomsi".
Offline
Hi,
I have a Gigabyte A520M H with a R3 3100.
I have the same problem with the latest BIOS (F11g [with AGESA 1.1.0.0 C]).
Unable to get rid of it with IOMMU disabled and/or "pci=noaer pci=nomsi".
Can you add this on your grub amd_iommu=off ?
Last edited by SupKurtJ (2020-11-21 11:08:07)
Offline
Luh wrote:Hi,
I have a Gigabyte A520M H with a R3 3100.
I have the same problem with the latest BIOS (F11g [with AGESA 1.1.0.0 C]).
Unable to get rid of it with IOMMU disabled and/or "pci=noaer pci=nomsi".Can you add this on your grub amd_iommu=off ?
Same problem, with "pci=noaer pci=nomsi amd_iommu=off" and IOMMU disabled in the BIOS.
Offline
The only difference it is your chipset AMD A520. I do not know why whis an X570 chipset, this workaround works.
Anyway, we have to wait for them to solve this issue....
Last edited by SupKurtJ (2020-11-21 13:25:24)
Offline
I can confirm this problem with X570 and Ryzen 9 5900X. An old BIOS with old AGESA Version works fine, a new one seems broken. I worked around this by adding:
`acpi=noirq` to my boot parameters, which solves the issue and results in a stable system.
However, IRQs will now be sent to all cores to be handled (instead of just to one core), which leads to a minor (for me not noticeable) performance impact. Still better than random reboots for sure.
Let's wait for AMD to fix it ...
Last edited by ptrxyz (2020-11-22 17:46:53)
Offline
Same issue here after updating the bios of my ASUS ROG Strix X570-E Gaming (Ryzen 3600X) from the one the Mobo shipped with a year ago to the latest(Version 2812 Beta Version) 2 days ago.
But so far my system has been stable.
Offline
I sent a message to AMD here https://www.amd.com/en/support/contact-email-form
Last edited by SupKurtJ (2020-11-24 16:26:39)
Offline
i have same problem with 'asus tuf gaming b450m pro s, ryzen 7 3700x'. boot showing "no irq handler for vector" message for 9-10 times. i'm using kernel 5.10rc5. i'm using last bios of my motherboard. i'm using bios Version 2409.
pls focus. my bios agesa is combov2 1.1.8.0. newer than 1.1.0.0.c
i'm tried acpi=noirq. "no irq handler for vector" message is gone. but i have random reboots again.
Last edited by toki1990 (2020-12-06 20:00:27)
Offline
i have same problem with 'asus tuf gaming b450m pro s, ryzen 7 3700x'. boot showing "no irq handler for vector" message for 9-10 times. i'm using kernel 5.10rc5. i'm using last bios of my motherboard. i'm using bios Version 2409.
pls focus. my bios agesa is combov2 1.1.8.0. newer than 1.1.0.0.ci'm tried acpi=noirq. "no irq handler for vector" message is gone. but i have random reboots again.
So you can just disable IOMMU for now on the bios.
I've sent an email to AMD, and they did not reply me.
Are you sure it is the version 1.1.8.0 ? Because the last version is 1.1.0.0 D...
Last edited by SupKurtJ (2020-12-08 11:04:35)
Offline
toki1990 wrote:i have same problem with 'asus tuf gaming b450m pro s, ryzen 7 3700x'. boot showing "no irq handler for vector" message for 9-10 times. i'm using kernel 5.10rc5. i'm using last bios of my motherboard. i'm using bios Version 2409.
pls focus. my bios agesa is combov2 1.1.8.0. newer than 1.1.0.0.ci'm tried acpi=noirq. "no irq handler for vector" message is gone. but i have random reboots again.
So you can just disable IOMMU for now on the bios.
I've sent an email to AMD, and they did not reply me.
Are you sure it is the version 1.1.8.0 ? Because the last version is 1.1.0.0 D...
i tried IOMMU. not solution.
screenshot of my uefi screen:
Offline
SupKurtJ wrote:toki1990 wrote:i have same problem with 'asus tuf gaming b450m pro s, ryzen 7 3700x'. boot showing "no irq handler for vector" message for 9-10 times. i'm using kernel 5.10rc5. i'm using last bios of my motherboard. i'm using bios Version 2409.
pls focus. my bios agesa is combov2 1.1.8.0. newer than 1.1.0.0.ci'm tried acpi=noirq. "no irq handler for vector" message is gone. but i have random reboots again.
So you can just disable IOMMU for now on the bios.
I've sent an email to AMD, and they did not reply me.
Are you sure it is the version 1.1.8.0 ? Because the last version is 1.1.0.0 D...
i tried IOMMU. not solution.
screenshot of my uefi screen:
Your screenshot doesn't work...
Offline