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: <61f2fc82-4eee-8678-c37a-dc300dde4edf@molgen.mpg.de>
Date:   Sat, 24 Feb 2018 09:06:19 +0100
From:   Paul Menzel <pmenzel@...gen.mpg.de>
To:     Borislav Petkov <bp@...en8.de>,
        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

Dear Thomas, dear Borislav,


Sorry for not attaching the logs.

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.


Kind regards,

Paul

View attachment "20180219–linux_4.14.17–journalctl-k.txt" of type "text/plain" (234757 bytes)

View attachment "20180224–linux_4.15.4–journalctl-k.txt" of type "text/plain" (153341 bytes)