From: Borislav Petkov <bp@alien8.de>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Paul Menzel <pmenzel@molgen.mpg.de>,
Paul Menzel <pmenzel+linux-irq@molgen.mpg.de>,
LKML <linux-kernel@vger.kernel.org>,
Yazen Ghannam <yazen.ghannam@amd.com>
Subject: Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1
Date: Mon, 26 Feb 2018 17:31:02 +0100 [thread overview]
Message-ID: <20180226163102.GM4377@pd.tnic> (raw)
In-Reply-To: <c84da3a5-107c-2ddc-d108-ebb33df49719@amd.com>
On Mon, Feb 26, 2018 at 10:14:10AM -0600, Tom Lendacky wrote:
> On 2/24/2018 2:59 AM, Thomas Gleixner wrote:
> > 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.
>
> I think I remember seeing something like this previously and it turned out
> to be a BIOS bug. All the AP's were enabled to work with the legacy 8259
> interrupt controller. In an SMP system, only one processor in the system
> should be configured to handle legacy 8259 interrupts (ExtINT delivery
> mode - see Intel's SDM, Volume 3, section 10.5.1, Delivery Mode). Once
> the BIOS was fixed, the spurious interrupt message went away.
>
> I believe at some point during UEFI, the APs were exposed to an ExtINT
> interrupt. Since they were configured to handle ExtINT delivery mode and
> interrupts were not yet enabled, the interrupt was left pending. When the
> APs were started by the OS and interrupts were enabled, the interrupt
> triggered. Since the original pending interrupt was handled by the BSP,
> there was no longer an interrupt actually pending, so the 8259 responds
> with IRQ 7 when queried by the OS. This occurred for each AP.
Interesting - is this something that can happen on Zen too?
Because I have such reports too.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-02-26 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 15:29 `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1 Paul Menzel
2018-02-23 18:18 ` Thomas Gleixner
2018-02-23 19:09 ` Borislav Petkov
2018-02-24 8:06 ` Paul Menzel
2018-02-24 8:59 ` Thomas Gleixner
2018-02-26 16:14 ` Tom Lendacky
2018-02-26 16:31 ` Borislav Petkov [this message]
2018-02-26 16:37 ` Morton, Eric
2018-02-26 16:42 ` Tom Lendacky
2018-03-29 7:21 ` Kai Heng Feng
2018-03-29 8:29 ` Paul Menzel
2018-03-29 20:57 ` Morton, Eric
2018-02-26 16:39 ` Tom Lendacky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180226163102.GM4377@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel+linux-irq@molgen.mpg.de \
--cc=pmenzel@molgen.mpg.de \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=yazen.ghannam@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox