linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Paul Menzel <pmenzel+linux-irq@molgen.mpg.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1
Date: Fri, 23 Feb 2018 20:09:50 +0100	[thread overview]
Message-ID: <20180223190950.GJ4981@pd.tnic> (raw)
In-Reply-To: <alpine.DEB.2.21.1802231914590.1437@nanos.tec.linutronix.de>

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.

  reply	other threads:[~2018-02-23 19:10 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 [this message]
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
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=20180223190950.GJ4981@pd.tnic \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmenzel+linux-irq@molgen.mpg.de \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).