Re: workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response

From	Takashi Iwai <tiwai@suse.de>
Newsgroups	linux.kernel
Subject	Re: workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response
Date	2017-01-31 10:40 +0100
Message-ID	<t5D4R-7sP-7@gated-at.bofh.it> (permalink)
References	<t3uS5-1Hz-11@gated-at.bofh.it> <t3xwC-3oV-17@gated-at.bofh.it> <t3zf4-4ws-7@gated-at.bofh.it> <t3zf4-4ws-5@gated-at.bofh.it> <t5lKG-5uN-35@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Mon, 30 Jan 2017 16:02:38 +0100,
Vlastimil Babka wrote:
> 
> On 01/25/2017 06:06 PM, Takashi Iwai wrote:
> > The code path is related with the runtime PM, so it's likely depending
> > on the device state, e.g. long-time pause or such.  I don't think Win
> > 10 plays a role, but who knows.
> >
> > In anyway, let me know if this helps.  Basically I can merge it even
> > for now, as the fix shouldn't give a regression.  But of course it'd
> > be better to have a test result :)
> 
> OK so unfortunately it now happened with the patch.

Hm, do you get the very same stack trace?

It's strange because azx_rirb_get_response() has the timeout of 1
second in its loop, so it can't wait forever.


Takashi

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response Takashi Iwai <tiwai@suse.de> - 2017-01-31 10:40 +0100

csiph-web