Messages in this thread | | | Date | Sat, 24 Feb 2018 09:59:11 +0100 (CET) | From | Thomas Gleixner <> | Subject | Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1 |
| |
On Sat, 24 Feb 2018, Paul Menzel wrote: > Am 23.02.2018 um 20:09 schrieb Borislav Petkov: > > On Fri, Feb 23, 2018 at 07:18:34PM +0100, Thomas Gleixner wrote: > > > Borislav is seeing similar issues on larger AMD machines. The interrupt > > > seems to come from BIOS/microcode during bringup of secondary CPUs and we > > > have no idea why. > > > > Paul, can you boot 4.14 and grep your dmesg for something like: > > > > [ 0.000000] spurious 8259A interrupt: IRQ7. > > > ? > > No, I do not see that. Please find the logs attached.
From your 4.14 log:
Feb 19 09:48:06.843173 kodi kernel: CPU 0 irqstacks, hard=e9b0a000 soft=e9b0c000 Feb 19 09:48:06.843216 kodi kernel: spurious 8259A interrupt: IRQ7. Feb 19 09:48:06.843258 kodi kernel: Console: colour VGA+ 80x25
So this has been there in 4.14 already just the detection mechanism has changed due to the modifications of the interrupt vector management code. It's not a real issue, just annoying ....
Thanks,
tglx
| |