Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Sat, 24 Feb 2018 09:59:11 +0100 (CET)
From:   Thomas Gleixner <tglx@linutronix.de>
To:     Paul Menzel <pmenzel@molgen.mpg.de>
cc:     Borislav Petkov <bp@alien8.de>,
        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
In-Reply-To: <61f2fc82-4eee-8678-c37a-dc300dde4edf@molgen.mpg.de>
Message-ID: <alpine.DEB.2.21.1802240941190.1825@nanos.tec.linutronix.de>
References: <8bb6b660-ce08-37a7-d1ab-38a690595856@molgen.mpg.de> <alpine.DEB.2.21.1802231914590.1437@nanos.tec.linutronix.de> <20180223190950.GJ4981@pd.tnic> <61f2fc82-4eee-8678-c37a-dc300dde4edf@molgen.mpg.de>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.
Feb 19 09:48:06.843258 kodi kernel: Console: colour VGA+ 80x25

So this has been there in 4.14 already just the detection mechanism has
changed due to the modifications of the interrupt vector management code.
It's not a real issue, just annoying ....

Thanks,

	tglx