linux-kernel - Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.21.1802231914590.1437@nanos.tec.linutronix.de>
Date:   Fri, 23 Feb 2018 19:18:34 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Paul Menzel <pmenzel+linux-irq@...gen.mpg.de>
cc:     LKML <linux-kernel@...r.kernel.org>, Borislav Petkov <bp@...en8.de>
Subject: Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

Paul,

On Fri, 23 Feb 2018, Paul Menzel wrote:
> 
> On the ASRock E350M1 (AMD A50M), since Linux 4.15 I get the message below.
> 
>     do_IRQ: 1.55 No irq handler for vector

Thanks for the report, but the single line of dmesg w/o any context is not
really helpful. Can you please provide a larger piece of dmesg which shows
in which context this happens.

I assume that this happens during early boot right when CPU1 is brought up,
right?

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.

Thanks,

	tglx