From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from Galois.linutronix.de ([146.0.238.70]:42510 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751985AbdFTJWL (ORCPT ); Tue, 20 Jun 2017 05:22:11 -0400 Date: Tue, 20 Jun 2017 11:22:05 +0200 (CEST) From: Thomas Gleixner To: Borislav Petkov cc: "Shah, Nehal-bakulchandra" , LKML , Linus Walleij , "linux-gpio@vger.kernel.org" , "Xue, Ken" , "S-k, Shyam-sundar" , "stable@vger.kernel.org" Subject: Re: [PATCH] pinctrl/amd: Use regular interrupt instead of chained In-Reply-To: <20170619161323.pjdrh6l33pqix32x@pd.tnic> Message-ID: References: <20170619161323.pjdrh6l33pqix32x@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: stable-owner@vger.kernel.org List-ID: 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