Linux USB
 help / color / mirror / Atom feed
From: Christian Eggers <ceggers@arri.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Khazhy Kumykov <khazhy@google.com>,
	Oliver Neukum <oneukum@suse.com>,
	USB mailing list <linux-usb@vger.kernel.org>,
	<regressions@lists.linux.dev>
Subject: Re: [REGRESSION] Re: [PATCH 1/3] USB: core: Unite old scheme and new scheme descriptor reads
Date: Tue, 12 Dec 2023 09:01:47 +0100	[thread overview]
Message-ID: <5737917.DvuYhMxLoT@n95hx1g2> (raw)
In-Reply-To: <c89fa5da-171f-48cc-ac9a-7949c45b5e54@rowland.harvard.edu>

Hi Alan,

On Monday, 11 December 2023, 17:21:56 CET, Alan Stern wrote:
> On Mon, Dec 11, 2023 at 11:40:38AM +0100, Christian Eggers wrote:
> > Last week I upgraded within the 5.15-stable branch. Since upstream commit
> > 85d07c556216 ("USB: core: Unite old scheme and new scheme descriptor reads"),
> > there are problems detecting a directly attached USB hub. I identified this
> > commit by bisecting and get the same result during upgrading within the 6.1-stable
> > branch.
> > 
> > Hardware: ARMv7 NXP i.MX6ULL with directly attached USB hub (Microchip USB4916).
> > Log messages:
> > 
> > [    6.150881] usb 1-1: new high-speed USB device number 2 using ci_hdrc
> > [    6.215484] usb 1-1: device descriptor read/8, error -71
> > [    6.377532] usb 1-1: device descriptor read/8, error -71
> 
> Is the old_scheme_first module parameter for the usbcore module set?  
> 
> That and the USB_PORT_QUIRK_OLD_SCHEME are the only things I can see 
> which would cause those errors -- and apparently this quirk never gets 
> set in current kernels.
that was the problem! In previous attempts to reduce the boot time of my system
I have set USB_PORT_QUIRK_OLD_SCHEME for specific combinations of bus/port numbers.

After reverting this, the warnings don't appear anymore, so everything is fine now.

Thanks for identifying the problem and sorry for the noise.

regards,
Christian




  reply	other threads:[~2023-12-12  8:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 19:09 [PATCH 0/3] USB: core: Don't overwrite device descriptor during reinitialization Alan Stern
2023-08-04 19:10 ` [PATCH 1/3] USB: core: Unite old scheme and new scheme descriptor reads Alan Stern
2023-08-04 19:12   ` [PATCH 2/3] USB: core: Change usb_get_device_descriptor() API Alan Stern
2023-08-04 19:14     ` [PATCH 3/3] USB: core: Fix race by not overwriting udev->descriptor in hub_port_init() Alan Stern
2023-12-11 10:40   ` [REGRESSION] Re: [PATCH 1/3] USB: core: Unite old scheme and new scheme descriptor reads Christian Eggers
2023-12-11 16:21     ` Alan Stern
2023-12-12  8:01       ` Christian Eggers [this message]
2023-08-08  8:47 ` [PATCH 0/3] USB: core: Don't overwrite device descriptor during reinitialization Greg KH
2023-08-10  0:28 ` Thinh Nguyen
2023-08-10  1:47   ` Alan Stern
2023-08-10 16:34     ` Alan Stern
2023-08-10 22:39       ` Thinh Nguyen
2023-08-11  1:52         ` Alan Stern
2023-08-11 17:05           ` Thinh Nguyen
2023-08-11 17:38             ` [PATCH] USB: core: Fix oversight in SuperSpeed initialization Alan Stern
2023-08-12  8:05               ` Greg KH
2023-08-12 15:28                 ` Alan Stern
2024-03-05  8:20 ` [REGRESSION] Re: [PATCH 0/3] USB: core: Don't overwrite device descriptor during reinitialization Jan Čermák
2024-03-06 21:08   ` Alan Stern
2024-03-07 16:17     ` Jan Čermák
2024-03-07 19:34       ` Alan Stern
2024-03-11  9:58         ` Jan Čermák
2024-03-11 14:43           ` Alan Stern
2024-03-12  8:57             ` Jan Čermák
2024-03-12 20:47               ` Alan Stern
2024-03-16 20:35               ` Alan Stern
2024-03-19 11:54                 ` Jan Čermák
2024-03-19 16:03                   ` Alan Stern
2024-03-27 13:24                     ` Jan Čermák
2024-03-27 14:21                       ` Alan Stern
2024-03-28 15:44                         ` Alexander Dahl
2024-03-28 16:16                           ` Alan Stern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5737917.DvuYhMxLoT@n95hx1g2 \
    --to=ceggers@arri.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=khazhy@google.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=regressions@lists.linux.dev \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox