[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1903061112350.1646@nanos.tec.linutronix.de>
Date: Wed, 6 Mar 2019 11:14:41 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Hans de Goede <hdegoede@...hat.com>
cc: Borislav Petkov <bp@...en8.de>,
"Lendacky, Thomas" <Thomas.Lendacky@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Subject: Re: False positive "do_IRQ: #.55 No irq handler for vector" messages
on AMD ryzen based laptops
Hans,
On Wed, 6 Mar 2019, Hans de Goede wrote:
> On 05-03-19 20:54, Borislav Petkov wrote:
> > On Tue, Mar 05, 2019 at 08:40:02PM +0100, Hans de Goede wrote:
> > > Finger pointing at the firmware if there are multiple vendors involved
> > > is really not going to help here. Esp. since most OEMs will just respond
> > > with "the machine works fine with Windows"
> >
> > Yes, because windoze simply doesn't report that spurious IRQ, most
> > likely.
>
> So maybe we need to lower the priority of the do_IRQ error from pr_emerg
> to pr_err then ? That will stop throwing the errors in the users face each
> boot on distros which have chosen to set the quiet loglevel to such a level
> that pr_err messages are not shown on the console (*).
Well, we rather try to understand and fix the issue.
So if Tom's theory holds, then the patch below should cure it.
Thanks,
tglx
8<---------------------
--- a/arch/x86/kernel/apic/apic.c
+++ b/arch/x86/kernel/apic/apic.c
@@ -1642,6 +1642,7 @@ static void end_local_APIC_setup(void)
*/
void apic_ap_setup(void)
{
+ clear_local_APIC();
setup_local_APIC();
end_local_APIC_setup();
}
Powered by blists - more mailing lists