From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 68EAD1859 for ; Wed, 26 Apr 2023 06:03:01 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 7344D1FDC9; Wed, 26 Apr 2023 06:02:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1682488979; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=XG58qb6Xrf429xde8p4UcRbRNUl6NjoDosi2Mwf5mpU=; b=Hs7wAkLJD/z8Clfq5Na/G2Hm9tBxF7GBkJaW1SKlCj0bItvSXf/B9IcHzLd4HFUEdfNnMq W4XQThIaSrKZp6sL7iw63ITe8gvwWB1111MxfwRXCr+3z38fFqSq1u/9G/yKctJDmcAUll 14vtuJ2a7ibYWj5lc5qavl9OwG1cGpc= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1682488979; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=XG58qb6Xrf429xde8p4UcRbRNUl6NjoDosi2Mwf5mpU=; b=AQwdlRNlhp6fQd0E0bvRU3PKOHY1j48czYLrP5t8VEb8d/L0+H2FTS3iKGIqX5XERx3f+i CUijhJRwUpL7axCQ== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 47D8513421; Wed, 26 Apr 2023 06:02:59 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id N9S9DpO+SGSaTgAAMHmgww (envelope-from ); Wed, 26 Apr 2023 06:02:59 +0000 Date: Wed, 26 Apr 2023 08:02:58 +0200 Message-ID: <87mt2vtc31.wl-tiwai@suse.de> From: Takashi Iwai To: Geraldo Nascimento Cc: Jakub Kicinski , Takashi Iwai , alsa-devel@alsa-project.org, linux-usb@vger.kernel.org, Greg Kroah-Hartman , regressions@lists.linux.dev Subject: Re: USB sound card freezes USB after resume from suspend In-Reply-To: References: <20230425111924.05cf8b13@kernel.org> <87pm7rtdul.wl-tiwai@suse.de> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0 Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII On Wed, 26 Apr 2023 07:46:47 +0200, Geraldo Nascimento wrote: > > Hello Jakub and Takashi, > > On Wed, Apr 26, 2023 at 07:24:50AM +0200, Takashi Iwai wrote: > > On Tue, 25 Apr 2023 20:19:24 +0200, > > Jakub Kicinski wrote: > > > > > > Hi! > > > > > > For a few weeks now I can't use any USB devices if I suspend my laptop > > > with my USB sound card active and resuming it without it connected. > > Takashi, did you pay attention to the workflow of triggering Jakub's > bug? He suspends the computer with the sound card active, disconnects > the sound card and expects to resume his computer back to an usable > state. It's a pretty normal procedure for many people; most of USB type-C docks have a USB audio built-in, and people remove the machine from the dock after suspend. So that's an operation that is seen everyday everywhere. Still I haven't heard this issue, and it implies that it's either something new or specific to the machine or the environment. Or we've been just lucky... Takashi > IMHO this is a very believable report and I can see something going > possibly wrong with this workflow. I understand you need the bisection > from Jakub to get a clearer picture, I was just emphasizing the point > that Jakub seems to be disconnecting the USB sound card during suspend > and then resuming, at least that's what I was able to understand. > > Thanks, > Geraldo Nascimento > > > > > > > USB worker threads seems to be sitting in: > > > > > > [<0>] snd_pcm_dev_disconnect+0x1e8/0x280 [snd_pcm] > > > [<0>] snd_device_disconnect_all+0x42/0x80 [snd] > > > [<0>] snd_card_disconnect+0x128/0x290 [snd] > > > [<0>] usb_audio_disconnect+0x11a/0x2c0 [snd_usb_audio] > > > [<0>] usb_unbind_interface+0x8c/0x270 > > > [<0>] device_release_driver_internal+0x1b2/0x230 > > > [<0>] bus_remove_device+0xd8/0x150 > > > [<0>] device_del+0x18b/0x410 > > > [<0>] usb_disable_device+0xc6/0x1e0 > > > [<0>] usb_disconnect+0xda/0x2c0 > > > [<0>] usb_disconnect+0xbf/0x2c0 > > > [<0>] usb_disconnect+0xbf/0x2c0 > > > [<0>] usb_disconnect+0xbf/0x2c0 > > > [<0>] hub_event+0xf01/0x1cd0 > > > [<0>] process_one_work+0x1c4/0x3d0 > > > [<0>] worker_thread+0x4d/0x380 > > > [<0>] kthread+0xe6/0x110 > > > [<0>] ret_from_fork+0x29/0x50 > > > > > > Which is: > > > > > > snd_pcm_dev_disconnect (/usr/src/debug/kernel-6.2.12/linux-6.2.12-300.fc38.x86_64/sound/core/pcm.c:818 /usr/src/debug/kernel-6.2.12/linux-6.2.12-300.fc38.x86_64/sound/core/pcm.c:812 /usr/src/debug/kernel-6.2.12/linux-6.2.12-300.fc38.x86_64/sound/core/pcm.c:1129) snd_pcm > > > > > > It happens on Fedora 37 and Fedora 38, it seems to have coincided with > > > the 6.2 kernel but I'm not 100% sure. > > > > > > The USB devices come back after half an hour or so, silently. > > > There's nothing of note in dmesg. > > > > AFAIK, there has been no similar report, so far. > > > > Is it a regression? If yes, could you figure out which kernel version > > starts showing the problem (or at best bisection)? > > > > > > thanks, > > > > Takashi >