[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1706201120190.1869@nanos>
Date: Tue, 20 Jun 2017 11:22:05 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Borislav Petkov <bp@...en8.de>
cc: "Shah, Nehal-bakulchandra" <Nehal-bakulchandra.Shah@....com>,
LKML <linux-kernel@...r.kernel.org>,
Linus Walleij <linus.walleij@...aro.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"Xue, Ken" <Ken.Xue@....com>,
"S-k, Shyam-sundar" <Shyam-sundar.S-k@....com>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH] pinctrl/amd: Use regular interrupt instead of chained
On Mon, 19 Jun 2017, Borislav Petkov wrote:
> On Fri, May 26, 2017 at 09:33:10AM +0000, Shah, Nehal-bakulchandra wrote:
> > Hi Thomas,
> >
> > Thanks for the prompt reply. Agree on points.
> >
> > we will validate at our end and shall provide the update.
>
> Any news on the issue? Resolution?
>
> I still have a user reporting "irq 7: nobody cared (try booting with the
> "irqpoll" option)" pointing to amd_gpio_irq_handler(), even with Thomas'
> patch.
>
> See https://bugzilla.suse.com/show_bug.cgi?id=1034261
>
> So something's still not completely fine yet.
Well, that's kinda expected.
If the interrupt _IS_ screaming because the hardware is buggered, then the
nobody cared thing will detect it and switch it off. That's all what we can
do, aside of not loading the driver at all.
But that's way better than silently locking up the box forever.
Thanks
tglx
Powered by blists - more mailing lists