From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932266AbdA3PCt (ORCPT ); Mon, 30 Jan 2017 10:02:49 -0500 Received: from mx2.suse.de ([195.135.220.15]:39756 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932155AbdA3PCl (ORCPT ); Mon, 30 Jan 2017 10:02:41 -0500 Subject: Re: workqueue lockup due to process_unsol_events stuck in azx_rirb_get_response To: Takashi Iwai References: <855fe8a9-4167-e193-d3d1-45e9d39630b1@suse.cz> <798b5572-f02b-e58d-9996-f3ecb4f15e1a@suse.cz> Cc: Jaroslav Kysela , alsa-devel@alsa-project.org, LKML From: Vlastimil Babka Message-ID: Date: Mon, 30 Jan 2017 16:02:38 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.