From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id AC73FC6FD1D for ; Wed, 15 Mar 2023 15:01:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232822AbjCOPBh (ORCPT ); Wed, 15 Mar 2023 11:01:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46524 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232877AbjCOPBS (ORCPT ); Wed, 15 Mar 2023 11:01:18 -0400 Received: from netrider.rowland.org (netrider.rowland.org [192.131.102.5]) by lindbergh.monkeyblade.net (Postfix) with SMTP id 2DE7E1A49E for ; Wed, 15 Mar 2023 08:00:29 -0700 (PDT) Received: (qmail 836918 invoked by uid 1000); 15 Mar 2023 10:53:23 -0400 Date: Wed, 15 Mar 2023 10:53:23 -0400 From: Alan Stern To: Mathias Nyman Cc: Brian Morrison , linux-usb@vger.kernel.org, Linux kernel regressions list , Chen Xingdi , Takashi Iwai , Moritz Fischer , Christian Lamparter , Vinod Koul Subject: Re: USB regression in kernel 6.2.2 Message-ID: <3d0a0429-a634-4c18-82e8-72028d8226d0@rowland.harvard.edu> References: <20230307132120.5897c5af@deangelis.fenrir.org.uk> <20230309200415.118777d2@deangelis.fenrir.org.uk> <20230312000316.2955d55a@deangelis.fenrir.org.uk> <20230314140008.79a90c38@deangelis.fenrir.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Wed, Mar 15, 2023 at 01:19:16PM +0200, Mathias Nyman wrote: > On 14.3.2023 16.00, Brian Morrison wrote: > > On Mon, 13 Mar 2023 12:06:59 +0200 > > Mathias Nyman wrote: > > > > > > > > > In your v6.2 logs the usb bus numbers are interleaved, in the v6.1 > > > they are not. xhci driver registers two usb buses per host, one > > > High-Speed and one SuperSpeed. > > > > > > This change could be due to 6.2 commit: > > > > > > 4c2604a9a689 usb: xhci-pci: Set PROBE_PREFER_ASYNCHRONOUS > > > > > > Not sure why it would cause this regression, but worth testing it. > > > > I have now reverted the above commit, it's only the one line in > > xhci-pci.c and it took a couple of hours to rebuild my kernel rpms which > > wasn't too bad. > > > > With this change all of my USB devices are present again and the 3 > > /dev/ttyUSB* nodes are all present and usable. > > > > Thanks for testing. > So setting PROBE_PREFER_ASYNCHRONOUS does trigger this issue for Renesas xHCI. > > Was it so that with the devices connected to the Intel host everything worked > on 6.2 kernel? > > Just to make sure that this is a vendor specific host issue and not generic xhci > driver issue. > > If we can't quickly figure out the real reason for this then we just have to > revert that patch. > > > I found this in the linux-usb list archives: > > > > https://www.spinics.net/lists/kernel/msg4569289.html > > > > and the first part of this patch series here: > > > > https://www.spinics.net/lists/kernel/msg4569288.html > > > > Should both of these patches be reverted? I assume so but I don't think > > I have anything that uses an ehci device to test it. > > > > Probably just the xhci one. I haven't heard of any ehci issues. > > Alan (cc) would know better if there are any new odd ehci issues that can > be traced back to the async probe change. I haven't heard of any problems with EHCI. Alan Stern