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: <20180223190950.GJ4981@pd.tnic>
Date:   Fri, 23 Feb 2018 20:09:50 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     Paul Menzel <pmenzel+linux-irq@...gen.mpg.de>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1

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.

?

Thx.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.