Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1670517 > unrolled thread

Re: [PATCH] pinctrl/amd: Use regular interrupt instead of chained

Started byThomas Gleixner <tglx@linutronix.de>
First post2017-06-20 11:30 +0200
Last post2017-06-20 11:40 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH] pinctrl/amd: Use regular interrupt instead of chained Thomas Gleixner <tglx@linutronix.de> - 2017-06-20 11:30 +0200
    Re: [PATCH] pinctrl/amd: Use regular interrupt instead of chained Borislav Petkov <bp@alien8.de> - 2017-06-20 11:40 +0200

#1670517 — Re: [PATCH] pinctrl/amd: Use regular interrupt instead of chained

FromThomas Gleixner <tglx@linutronix.de>
Date2017-06-20 11:30 +0200
SubjectRe: [PATCH] pinctrl/amd: Use regular interrupt instead of chained
Message-ID<tUnDX-6Ll-1@gated-at.bofh.it>
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

[toc] | [next] | [standalone]


#1670546

FromBorislav Petkov <bp@alien8.de>
Date2017-06-20 11:40 +0200
Message-ID<tUnNF-6PZ-39@gated-at.bofh.it>
In reply to#1670517
On Tue, Jun 20, 2017 at 11:22:05AM +0200, Thomas Gleixner wrote:
> 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.

Sounds to me we should route this fix to stable.

Looking at Linus' branch:

https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/commit/?h=fixes&id=ba714a9c1dea85e0bf2899d02dfeb9c70040427c

patch isn't tagged for stable.

Should it be?

It certainly is an improvement of the situation.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web