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:   Fri, 23 Feb 2018 19:18:34 +0100 (CET)
From:   Thomas Gleixner <tglx@linutronix.de>
To:     Paul Menzel <pmenzel+linux-irq@molgen.mpg.de>
cc:     LKML <linux-kernel@vger.kernel.org>, Borislav Petkov <bp@alien8.de>
Subject: Re: `do_IRQ: 1.55 No irq handler for vector` on ASRock E350M1
In-Reply-To: <8bb6b660-ce08-37a7-d1ab-38a690595856@molgen.mpg.de>
Message-ID: <alpine.DEB.2.21.1802231914590.1437@nanos.tec.linutronix.de>
References: <8bb6b660-ce08-37a7-d1ab-38a690595856@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

Paul,

On Fri, 23 Feb 2018, Paul Menzel wrote:
> 
> On the ASRock E350M1 (AMD A50M), since Linux 4.15 I get the message below.
> 
>     do_IRQ: 1.55 No irq handler for vector

Thanks for the report, but the single line of dmesg w/o any context is not
really helpful. Can you please provide a larger piece of dmesg which shows
in which context this happens.

I assume that this happens during early boot right when CPU1 is brought up,
right?

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.

Thanks,

	tglx