Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1570524 > unrolled thread
| Started by | Takashi Iwai <tiwai@suse.de> |
|---|---|
| First post | 2017-01-31 10:40 +0100 |
| Last post | 2017-01-31 10:40 +0100 |
| Articles | 1 — 1 participant |
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.
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
| From | Takashi Iwai <tiwai@suse.de> |
|---|---|
| Date | 2017-01-31 10:40 +0100 |
| Subject | Re: workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response |
| Message-ID | <t5D4R-7sP-7@gated-at.bofh.it> |
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 top | Article view | linux.kernel
csiph-web