From: "Michał Pecio" <michal.pecio@gmail.com>
To: "Marcus Rückert" <kernel@nordisch.org>
Cc: "Mathias Nyman" <mathias.nyman@linux.intel.com>,
"Jiri Slaby" <jirislaby@kernel.org>,
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: Wed, 13 Aug 2025 00:02:48 +0200 [thread overview]
Message-ID: <20250813000248.36d9689e@foxbook> (raw)
In-Reply-To: <4fd2765f5454cbf57fbc3c2fe798999d1c4adccb.camel@nordisch.org>
On Tue, 12 Aug 2025 20:15:13 +0200, Marcus Rückert wrote:
> On Tue, 2025-08-12 at 13:48 +0300, Mathias Nyman wrote:
> > > > [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
> >
> > Tear down xhci.
>
> so usb is not dead completely. I can connect my keyboard to the
> charging cable of my mouse and it starts working again. but it seems
> all my devices hanging on that part of the usb tree are dead
> (DAC/keyboard)
You have multiple USB buses on multiple xHCI controllers. Controller
responsible for bus 1 goes belly up and its devices are lost, but the
rest keeps working.
It would make sense to figure out what was this device on port 2 of
bus 1 which triggered the failure. Your lsusb output shows no such
device, so it was either disconnected, connected to another port or
it malfunctioned and failed to enumerate at the time. Do you know?
What's the output of these commands right now?
dmesg |grep 'usb 1-2'
dmesg |grep 'descriptor read'
Do you have logs? Can you look at them to see if it was always
"usb 1-2" causing trouble in the past?
> lspci is here
>
> https://bugzilla.opensuse.org/show_bug.cgi?id=1247895#c3
>
> Mainboard is a ASUS ProArt X870E-CREATOR WIFI
Thanks. Unfortunately I don't have this exact chipset, but it's
an AMD chipset made by ASMedia, as suspected.
The situation is somewhat similar (though different) to this bug:
https://bugzilla.kernel.org/show_bug.cgi?id=220069
Random failures for no clear reason, apparently triggered by some
repetitive background activity. Very annoying.
next prev parent reply other threads:[~2025-08-12 22:02 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
2025-08-12 10:48 ` Mathias Nyman
2025-08-12 18:15 ` Marcus Rückert
2025-08-12 22:02 ` Michał Pecio [this message]
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=20250813000248.36d9689e@foxbook \
--to=michal.pecio@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kernel@nordisch.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