Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1569810
| From | Vlastimil Babka <vbabka@suse.cz> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response |
| Date | 2017-01-30 16:10 +0100 |
| Message-ID | <t5lKG-5uN-35@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> |
| Organization | linux.* mail to news gateway |
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.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response Vlastimil Babka <vbabka@suse.cz> - 2017-01-25 13:30 +0100
Re: workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response Takashi Iwai <tiwai@suse.de> - 2017-01-25 16:20 +0100
Re: workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response Vlastimil Babka <vbabka@suse.cz> - 2017-01-25 18:10 +0100
Re: workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response Takashi Iwai <tiwai@suse.de> - 2017-01-25 18:10 +0100
Re: workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response Vlastimil Babka <vbabka@suse.cz> - 2017-01-30 16:10 +0100
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