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 08:42:52 +0200 [thread overview]
Message-ID: <20250813084252.4dcd1dc5@foxbook> (raw)
In-Reply-To: <bea9aa71d198ba7def318e6701612dfe7358b693.camel@nordisch.org>
On Wed, 13 Aug 2025 03:58:07 +0200, Marcus Rückert wrote:
> dmesg |grep 'usb 1-2' ; dmesg |grep 'descriptor read'
> [ 2.686292] [ T787] usb 1-2: new full-speed USB device number 3
> using xhci_hcd
> [ 3.054496] [ T787] usb 1-2: New USB device found, idVendor=31e3,
> idProduct=1322, bcdDevice= 2.30
> [ 3.054499] [ T787] usb 1-2: New USB device strings: Mfr=1,
> Product=2, SerialNumber=3
> [ 3.054500] [ T787] usb 1-2: Product: Wooting 60HE+
> [ 3.054501] [ T787] usb 1-2: Manufacturer: Wooting
OK, so you had a keyboard in this port during the last boot. Is this
keyboard always connected to the same port? There is no bus 1 port 2
device on your earlier lsusb output, so it was either not connected
there or not detected due to malfunction.
> journalctl --since 2025-07-01 --grep "reset full-speed USB device
> number"
>
> Jul 24 15:56:34 kernel: usb 1-2: reset full-speed USB device number 14
> using xhci_hcd
> Jul 24 15:56:35 kernel: usb 1-2: reset full-speed USB device number 14
> using xhci_hcd
> Jul 24 15:56:36 kernel: usb 1-2: reset full-speed USB device number 14
> using xhci_hcd
> Jul 24 15:56:37 kernel: usb 1-2: reset full-speed USB device number 14
> using xhci_hcd
> Jul 31 19:53:02 kernel: usb 1-2: reset full-speed USB device number 50
> using xhci_hcd
> Jul 31 19:53:03 kernel: usb 1-2: reset full-speed USB device number 50
> using xhci_hcd
> Jul 31 19:53:04 kernel: usb 1-2: reset full-speed USB device number 50
> using xhci_hcd
> Jul 31 19:53:04 kernel: usb 1-2: reset full-speed USB device number 50
> using xhci_hcd
> Aug 06 16:51:34 kernel: usb 1-2: reset full-speed USB device number 12
> using xhci_hcd
> Aug 06 16:51:35 kernel: usb 1-2: reset full-speed USB device number 12
> using xhci_hcd
> Aug 06 16:51:36 kernel: usb 1-2: reset full-speed USB device number 12
> using xhci_hcd
> Aug 06 16:51:36 kernel: usb 1-2: reset full-speed USB device number 12
> using xhci_hcd
So this port was getting reset in the past. Can you also check:
- how many of those resets were followed by "HC died"
- if all "HC died" events were caused by resets of port usb 1-2
(or some other port)
And for the record, what exactly was the original problem which you
reported to Suse and believe to be caused by a kernel upgrade? Was it
"HC died" and loss of multiple devices, or just the keyborad failing
to work and spamming "reset USB device numebr x", or something else?
Regards,
Michal
next prev parent reply other threads:[~2025-08-13 6:43 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
2025-08-13 1:58 ` Marcus Rückert
2025-08-13 6:42 ` Michał Pecio [this message]
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=20250813084252.4dcd1dc5@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