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

toki1990 · 2020-12-10 15:47:32

SupKurtJ wrote:

toki1990 wrote:
SupKurtJ wrote:
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:
https://ibb.co/GVLZ1xG
Your screenshot doesn't work...

https://imgur.com/CKpjgYv

Riggs · 2020-12-20 17:32:35

toki1990 wrote:

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.c
i'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:
https://ibb.co/GVLZ1xG

You can try add this to boot: “noapic"

Hope helps

TheCraiggers · 2020-12-21 02:19:55

Turning off the IOMMU and/or APIC seems to be a big deal for something that doesn't seem to be causing issues as far as anybody can tell. Has anybody actually noticed system instability from this?

mabod · 2020-12-21 10:52:06

No. I havent noticed any negative effects regarding these messages.

Deactivating the IOMMU in the BIOS is not a big deal from my point of view. Simple office PCs hardly use the IOMMU. It is mainly used for virtual environments and passthrough of hardware (GPU etc.). That is probably the reason why nobody has reported side effects of these error messages so far. May be somebody who is doing GPU passthrough with qemu will notice something.

Anyways, I have deactivate IOMMU in BIOS and all is good.

toki1990 · 2020-12-23 19:40:53

Riggs wrote:

toki1990 wrote:
SupKurtJ wrote:
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:
https://ibb.co/GVLZ1xG
You can try add this to boot: “noapic"
Hope helps

i tried. not solution. but thanks for reply. no irq handler for vector message is cleaned. but boot sometimes stuck. i tried linux-next-git kernel. its showing mce hardware error when booting.

Last edited by toki1990 (2021-01-04 20:23:44)

toki1990 · 2021-01-01 17:19:05

i tried agesa 1.1.9.0 included last beta bios of my motherboard ( tuf gaming b450m pro s ). this bios not including fix ( v2601 ). i'm changed my cpu. My new cpu is ryzen 9 5900x. there is no random reboots. but linux system sometimes stuck at boot.

Last edited by toki1990 (2021-01-01 17:19:35)

mabod · 2021-01-05 06:14:19

I just updated my BIOS to the latest beta version with AEGESA 1.1.9.0 and the boot messages "No irq handler for vector" are all gone. The journal is clean.

mobo: MSI MPG X570 GAMING EDGE WIFI
BIOS: 7C37v1D2(Beta version) (2021-01-04)

SupKurtJ · 2021-01-07 10:06:22

Gigabyte bios still on 1.1.0.0 D .... I have to wait for this version AGESA 1.1.9.0 and confirm if this version solve this trouble.

ratcheer · 2021-01-07 17:19:52

I just got a new BIOS for my Asus TUF X-570 motherboard, version 3202 dated 01/04/21. I still get the IRQ handler messages when booting.

But, at least my PC will now reboot.

toki1990 · 2021-01-07 21:04:37

i tried lastest agesa 1.1.9.0 included bios (v2602) for my "tuf gaming b450m pro s". not solution.

toki1990 · 2021-01-13 16:52:45

i tried lastest agesa 1.2.0.0 included bios (v2801) for my motherboard. not solution. i sended message to asus support. (they are always not help). their support is crap

SupKurtJ · 2021-02-01 23:26:12

Hi,
I tried the latest version of my Gigabyte motherboard 33a, with AGESA 1.2.0.0 (https://download.gigabyte.com/FileList/ … i_f33a.zip), and all is working well now.
This version solve the trouble.

mabod · 2021-02-02 06:47:44

SupKurtJ wrote:

Hi,
I tried the latest version of my Gigabyte motherboard 33a, with AGESA 1.2.0.0 (https://download.gigabyte.com/FileList/ … i_f33a.zip), and all is working well now.
This version solve the trouble.

I can confirm. No more "No irq handler for vector" messages with BIOS F33a on my X570 AORUS ULTRA

torrenator · 2021-02-03 19:10:47

I can confirm it as well for the Gigabyte X570 Aorus Elite with version F33a

Luh · 2021-02-04 19:12:20

Yup, I can confirm too. No more errors with Gigabyte A520M H, bios F13a.

mcloaked · 2021-02-04 19:47:21

Asrock has not yet updated their BIOS for my motherboard - but hopefully that will happen before long but it sounds like the Gigabyte BIOS update has solved the issue. Presumably the main fix came from AMD (AGESA), and has been passed to OEMs to implement in their BIOS releases upcoming.

ien · 2021-02-10 19:31:44

Asus released bios 2807 for TUF B450-plus gaming yesterday. It has AGESA V2 PI 1.2.0.0, but I still get "no irq.." messages at boot.

toki1990 · 2021-02-10 20:30:25

ien wrote:

Asus released bios 2807 for TUF B450-plus gaming yesterday. It has AGESA V2 PI 1.2.0.0, but I still get "no irq.." messages at boot.

Same problem for ASUS. Asus releasted bios 2807 for TUF Gaming B450M PRO S. I still get "no irq..." message at boot.

blueman · 2021-02-25 18:47:32

toki1990 wrote:

ien wrote:
Asus released bios 2807 for TUF B450-plus gaming yesterday. It has AGESA V2 PI 1.2.0.0, but I still get "no irq.." messages at boot.
Same problem for ASUS. Asus releasted bios 2807 for TUF Gaming B450M PRO S. I still get "no irq..." message at boot.

ROG Crosshair VIII Hero with latest BIOS Version 3204 is also affected.

sher424 · 2021-02-27 17:07:56

B550 GAMING X Rev 1.0 and F13c (with AGESA 1.2.0.0) firmware solve this problem in my case.

Прошивка B550 GAMING X Rev 1.0 на F13c (with AGESA 1.2.0.0) решила эту проблему в моём случае.

Last edited by sher424 (2021-02-27 17:09:34)

Aloysius · 2021-03-02 07:45:27

sher424 wrote:

B550 GAMING X Rev 1.0 and F13c (with AGESA 1.2.0.0) firmware solve this problem in my case.
Прошивка B550 GAMING X Rev 1.0 на F13c (with AGESA 1.2.0.0) решила эту проблему в моём случае.

Hi, any side-effects?

sher424 · 2021-03-07 05:00:44

Aloysius wrote:

Hi, any side-effects?

I didn't find any side effects.
Is there any way to find them or test them?

Last edited by sher424 (2021-03-07 07:42:51)

Aloysius · 2021-03-07 08:28:05

sher424 wrote:

Aloysius wrote:
Hi, any side-effects?
I didn't find any side effects.
Is there any way to find them or test them?

Thanks, I updated myself and haven't encountered any problem.

Scrumplex · 2021-03-14 15:26:09

I am running a 3900X on an ASUS ROG B450-F Gaming II. My UEFI is on the latest version (4204) with AGESA 1.2.0.0 (ComboV2PI_1200).

I still get these message on boot.

cyberdummy · 2021-03-17 10:01:40

Updated my ASUS ROG Strix B550-I Gaming with BIOS version 2003 (AMD AM4 AGESA V2 PI 1.2.0.1) released on 2021/03/15 and message has gone.

Arch Linux

#51 2020-12-10 15:47:32

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

#52 2020-12-20 17:32:35

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

#53 2020-12-21 02:19:55

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

#54 2020-12-21 10:52:06

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

#55 2020-12-23 19:40:53

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

#56 2021-01-01 17:19:05

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

#57 2021-01-05 06:14:19

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

#58 2021-01-07 10:06:22

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

#59 2021-01-07 17:19:52

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

#60 2021-01-07 21:04:37

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

#61 2021-01-13 16:52:45

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

#62 2021-02-01 23:26:12

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

#63 2021-02-02 06:47:44

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

#64 2021-02-03 19:10:47

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

#65 2021-02-04 19:12:20

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

#66 2021-02-04 19:47:21

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

#67 2021-02-10 19:31:44

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

#68 2021-02-10 20:30:25

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

#69 2021-02-25 18:47:32

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

#70 2021-02-27 17:07:56

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

#71 2021-03-02 07:45:27

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

#72 2021-03-07 05:00:44

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

#73 2021-03-07 08:28:05

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

#74 2021-03-14 15:26:09

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

#75 2021-03-17 10:01:40

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

Board footer