From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751540AbdAaJfS (ORCPT ); Tue, 31 Jan 2017 04:35:18 -0500 Received: from mx2.suse.de ([195.135.220.15]:47981 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751499AbdAaJfD (ORCPT ); Tue, 31 Jan 2017 04:35:03 -0500 Date: Tue, 31 Jan 2017 10:35:00 +0100 Message-ID: From: Takashi Iwai To: Vlastimil Babka Cc: Jaroslav Kysela , alsa-devel@alsa-project.org, LKML Subject: Re: workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response In-Reply-To: References: <855fe8a9-4167-e193-d3d1-45e9d39630b1@suse.cz> <798b5572-f02b-e58d-9996-f3ecb4f15e1a@suse.cz> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.1 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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