From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Forest <forestix@gaga.casa>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Stefan Eichenberger <stefan.eichenberger@toradex.com>,
Pawel Laszczak <pawell@cadence.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [REGRESSION][BISECTED] usb: hub: total system freeze after running adb
Date: Tue, 18 Nov 2025 11:21:18 +0200 [thread overview]
Message-ID: <cc788286-c327-4b1f-adb4-8494c0145d74@linux.intel.com> (raw)
In-Reply-To: <qc0nhk9c6l0a08bkfeplrm3qjssgrjkvkp@sonic.net>
Hi
On 11/17/25 22:18, Forest wrote:
> #regzbot introduced 8f5b7e2bec1c
>
> Running adb (android debug bridge) commands causes the entire system to
> freeze some time later.
>
> The freeze usually occurs within two hours of running adb, but not always.
> Stopping adb's persistent background process with `adb kill-server` seems to
> avoid the freeze. (However, this is not always possible, since the system
> sometimes freezes just a few seconds after adb is launched.)
>
> It occurs even when no android devices are connected to the system.
>
> I am unsure whether user activity affects how soon the freeze happens.
>
> Observations when it happens:
>
> - No messages are written to dmesg or syslog.
> - Virtual console switching no longer works.
> - SysRq key commands no longer work, as far as I can tell.
> - Whatever was on the display remains intact.
> - Any already-playing audio enters a short loop, as though the motherboard's
> sound device is playing from a ring buffer that no longer gets updated.
>
> I have reproduced it on mainline (6.18.0-rc5) and various older kernel
> versions as early as 6.12.48, built with Debian config files and
> `make olddefconfig`. Tested using Debian Stable 13.2 (trixie), and its
> adb 1:34.0.5-12 package.
>
> Git bisect identifies the culprit:
> commit 8f5b7e2bec1c36578fdaa74a6951833541103e27
> 2025-06-11 14:24:41 +0300
> usb: hub: fix detection of high tier USB3 devices behind suspended hubs
>
> Reverting that commit (along with two later commits that build upon it)
> seems to fix the problem in the mainline and longterm kernels that I tried.
Could you share some info about this setup:
lspci -nnv -d ::0c03
lsusb -t
Enabling usb core and xhci dynamic debug could share some light on this:
mount -t debugfs none /sys/kernel/debug
echo 'module xhci_hcd =p' >/sys/kernel/debug/dynamic_debug/control
echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control
< Reproduce issue >
Send output of dmesg
If the bisected patch is the issue then disabling runtime suspend could help.
For all usb* roothubs:
echo on > /sys/bus/usb/devices/usb*/power/control
Does it affect anything?
Thanks
Mathias
next prev parent reply other threads:[~2025-11-18 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 20:18 [REGRESSION][BISECTED] usb: hub: total system freeze after running adb Forest
2025-11-18 9:21 ` Mathias Nyman [this message]
2025-11-20 22:04 ` Forest
2025-12-02 18:44 ` Forest
2025-12-03 23:41 ` Mathias Nyman
2025-12-05 1:56 ` Forest
2025-12-05 14:57 ` Mathias Nyman
2025-11-18 9:59 ` Michal Pecio
2025-11-20 22:18 ` Forest
2025-12-04 8:23 ` Michal Pecio
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=cc788286-c327-4b1f-adb4-8494c0145d74@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=forestix@gaga.casa \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pawell@cadence.com \
--cc=regressions@lists.linux.dev \
--cc=stefan.eichenberger@toradex.com \
--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