bugzilla-daemon@bugzilla.kernel.org writes:
> After AMD released AGESA 1.0.0.2 there are an increasing amount of reports
> regarding the below error messages during boot after the bios was updated.
>
> It seems that the use of a current bios version with AGESA 1.0.0.2 is the
> common factor.

Cute.

> kernel: smpboot: CPU0: AMD Ryzen 7 3700X 8-Core Processor (family: 0x17,
> model:
> 0x71, stepping: 0x0)
> kernel: x86: Booting SMP configuration:
> kernel: .... node  #0, CPUs:        #1
> kernel: do_IRQ: 1.55 No irq handler for vector
> kernel:   #2
> kernel: do_IRQ: 2.55 No irq handler for vector
> kernel:   #3
> kernel: do_IRQ: 3.55 No irq handler for vector
> kernel:   #4
> kernel: do_IRQ: 4.55 No irq handler for vector
> kernel:   #5
> kernel: do_IRQ: 5.55 No irq handler for vector
> kernel:   #6
> kernel: do_IRQ: 6.55 No irq handler for vector
> kernel:   #7
> kernel: do_IRQ: 7.55 No irq handler for vector
> kernel:   #8
> kernel: do_IRQ: 8.55 No irq handler for vector
> kernel:   #9
> kernel: do_IRQ: 9.55 No irq handler for vector
> kernel:  #10
> kernel: do_IRQ: 10.55 No irq handler for vector
> kernel:  #11 #12 #13 #14 #15

So CPU 1-10 all receive an interrupt vector which they don't have a
handler for. CPUs 11-15 not. Nothing what rings a bell here and I'm
pretty sure that at this stage nothing in the kernel has set up anything
on vector 55. This looks like BIOS having set up some interrupt vector
for some device and then failed to tear it down properly before handing
off to the kernel.

As the reports seem to agree that this is related to the BIOS update,
this wants to be looked at from the firmware people. CC'ed Tom @amd,
maybe he can relay it to the relevant people there.

> Additional bug reports:
>
>
> https://www.reddit.com/r/Fedora/comments/hvdhq2/kernal_579_problem_12345123456_do_irq_no_irq/

Reddit as a information source for bug hunting. That's what I truly
need. :)

Please note that this error still persists with the current AGESA 1.1.0.0


The error log has changed slightly though:

kernel: __common_interrupt: 1.55 No irq handler for vector
kernel:   #2
kernel: __common_interrupt: 2.55 No irq handler for vector
kernel:   #3
kernel: __common_interrupt: 3.55 No irq handler for vector
kernel:   #4
kernel: __common_interrupt: 4.55 No irq handler for vector
kernel:   #5
kernel: __common_interrupt: 5.55 No irq handler for vector
kernel:   #6
kernel: __common_interrupt: 6.55 No irq handler for vector
kernel:   #7
kernel: __common_interrupt: 7.55 No irq handler for vector
kernel:   #8
kernel: __common_interrupt: 8.55 No irq handler for vector
kernel:   #9
kernel: __common_interrupt: 9.55 No irq handler for vector
kernel:  #10
kernel: __common_interrupt: 10.55 No irq handler for vector
kernel:  #11 #12 #13 #14 #15


I have tried to report this issue to AMD, but their bug reporting tools seems to be run by bots and did it not understand the problem.

I'm being told this should be fixed in AGESA 1.1.8.0 so if anyone can confirm, that would be great. Provided the OEM vendors update AGESA in their BIOS, that is...

Thx.

Hello,
I'm using Ryzen 5950 with Gigabyte MB and updated to Agesa 1.2.0.0 and those messages still occur. Even worse, I get messages like
>upowerd[933]: did not recognise USB path
>/sys/devices/pci0000:00/0000:00:03.1/0000:09:00.3/i2c-0/0-0008/power_supply/ucsi-source-psy-0-00081,
>please report

Sound and mouse are lagging. 

Regards

@pj that's not encouraging. What chipset is that?

I'm using Gigabyte X570 Aorus xtreme. Had 'broken bios' messages prior to Agesa 1.2.0.0/1.1.0.0D but it never caused problems like I have now.

@Luigi Baldoni
So could you give me an advice what to do now? Whom could I ask for help?

Regards

Updated the BIOS with agesa 1.2.0.0 on my Asrock B550 Pro4 and the error message has disappeared.

No detectable side effect so far.