From: "Michał Pecio" <michal.pecio@gmail.com>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: "Mathias Nyman" <mathias.nyman@linux.intel.com>,
gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
stern@rowland.harvard.edu, stable@vger.kernel.org,
"Łukasz Bartosik" <ukaszb@chromium.org>,
"Oliver Neukum" <oneukum@suse.com>
Subject: Re: [PATCH] usb: hub: Don't try to recover devices lost during warm reset.
Date: Mon, 11 Aug 2025 23:28:15 +0200 [thread overview]
Message-ID: <20250811232815.393c7bb9@foxbook> (raw)
In-Reply-To: <fc3e5cf5-a346-4329-a66e-5d28cb4fe763@kernel.org>
On Mon, 11 Aug 2025 08:16:06 +0200, Jiri Slaby wrote:
> This was reported to break the USB on one box:
> > [Wed Aug 6 16:51:33 2025] [ T355745] usb 1-2: reset full-speed USB device number 12 using xhci_hcd
> > [Wed Aug 6 16:51:34 2025] [ T355745] usb 1-2: device descriptor read/64, error -71
> > [Wed Aug 6 16:51:34 2025] [ T355745] usb 1-2: device descriptor read/64, error -71
> > [Wed Aug 6 16:51:34 2025] [ T355745] usb 1-2: reset full-speed USB device number 12 using xhci_hcd
> > [Wed Aug 6 16:51:34 2025] [ T355745] usb 1-2: device descriptor read/64, error -71
> > [Wed Aug 6 16:51:35 2025] [ T355745] usb 1-2: device descriptor read/64, error -71
> > [Wed Aug 6 16:51:35 2025] [ T355745] usb 1-2: reset full-speed USB device number 12 using xhci_hcd
> > [Wed Aug 6 16:51:35 2025] [ T355745] usb 1-2: Device not responding to setup address.
> > [Wed Aug 6 16:51:35 2025] [ T355745] usb 1-2: Device not responding to setup address.
> > [Wed Aug 6 16:51:35 2025] [ T355745] usb 1-2: device not accepting address 12, error -71
> > [Wed Aug 6 16:51:35 2025] [ T355745] usb 1-2: WARN: invalid context state for evaluate context command.
> > [Wed Aug 6 16:51:36 2025] [ T355745] usb 1-2: reset full-speed USB device number 12 using xhci_hcd
> > [Wed Aug 6 16:51:36 2025] [ C10] xhci_hcd 0000:0e:00.0: ERROR unknown event type 2
> > [Wed Aug 6 16:51:36 2025] [ T355745] usb 1-2: Device not responding to setup address.
> > [Wed Aug 6 16:51:37 2025] [ C10] xhci_hcd 0000:0e:00.0: ERROR unknown event type 2
> > [Wed Aug 6 16:52:50 2025] [ T362645] xhci_hcd 0000:0e:00.0: Abort failed to stop command ring: -110
> > [Wed Aug 6 16:52:50 2025] [ T362645] xhci_hcd 0000:0e:00.0: xHCI host controller not responding, assume dead
> > [Wed Aug 6 16:52:50 2025] [ T362645] xhci_hcd 0000:0e:00.0: HC died; cleaning up
> > [Wed Aug 6 16:52:50 2025] [ T359046] usb 1-1: USB disconnect, device number 13
> > [Wed Aug 6 16:52:50 2025] [ T355745] xhci_hcd 0000:0e:00.0: Timeout while waiting for setup device command
> > [Wed Aug 6 16:52:50 2025] [ T362645] usb 2-3: USB disconnect, device number 2
> > [Wed Aug 6 16:52:50 2025] [ T362839] cdc_acm 1-5:1.5: acm_port_activate - usb_submit_urb(ctrl irq) failed
> > [Wed Aug 6 16:52:50 2025] [ T355745] usb 1-2: device not accepting address 12, error -62
> > [Wed Aug 6 16:52:50 2025] [ T359046] usb 1-2: USB disconnect, device number 12
> > [Wed Aug 6 16:52:50 2025] [ T359046] usb 1-3: USB disconnect, device number 4
> > [Wed Aug 6 16:52:50 2025] [ T359046] usb 1-3.1: USB disconnect, device number 6
> > [Wed Aug 6 16:52:50 2025] [ T359046] usb 1-4: USB disconnect, device number 16
> > [Wed Aug 6 16:52:50 2025] [ T359046] usb 1-5: USB disconnect, device number 15
> > [Wed Aug 6 16:52:50 2025] [ T359046] usb 1-7: USB disconnect, device number 8
Is the problem that this USB device fails to work, or that it takes
down the whole bus while failing to work as usual?
The latter issue looks like some ASMedia xHCI controller being unhappy
about something. What does 'lspci' say about this 0e:00.0?
So far I failed to repro this on v6.16.0 with a few of my ASMedias and
a dummy device which never responds to any packet.
Can you mount debugfs and get these two files after the HC goes dead?
/sys/kernel/debug/usb/xhci/0000:0e:00.0/command-ring/trbs
/sys/kernel/debug/usb/xhci/0000:0e:00.0/event-ring/trbs
Regards,
Michal
next prev parent reply other threads:[~2025-08-11 21:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 13:39 [PATCH] usb: hub: Don't try to recover devices lost during warm reset Mathias Nyman
2025-07-15 17:48 ` Greg KH
2025-07-15 18:54 ` Alan Stern
2025-08-11 6:16 ` Jiri Slaby
2025-08-11 11:06 ` Jiri Slaby
2025-08-11 19:24 ` Alan Stern
2025-08-11 21:28 ` Michał Pecio [this message]
2025-08-12 10:48 ` Mathias Nyman
2025-08-12 18:15 ` Marcus Rückert
2025-08-12 22:02 ` Michał Pecio
2025-08-13 1:58 ` Marcus Rückert
2025-08-13 6:42 ` Michał Pecio
2025-08-13 9:14 ` Marcus Rückert
2025-08-13 9:48 ` Michał Pecio
2025-08-13 10:05 ` Marcus Rückert
2025-08-14 5:41 ` Michał Pecio
2025-08-13 10:13 ` Mathias Nyman
2025-08-13 2:11 ` Marcus Rückert
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=20250811232815.393c7bb9@foxbook \
--to=michal.pecio@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=oneukum@suse.com \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=ukaszb@chromium.org \
/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;
as well as URLs for NNTP newsgroup(s).