public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Pecio <michal.pecio@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Oliver Neukum <oneukum@suse.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	Hillf Danton <hdanton@sina.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-usb@vger.kernel.org
Subject: Re: Deadlock in usb subsystem on shutdown, 6.18.3+
Date: Thu, 29 Jan 2026 10:28:19 +0100	[thread overview]
Message-ID: <20260129102819.77378628.michal.pecio@gmail.com> (raw)
In-Reply-To: <737b2608-3b62-0e8b-9c78-44cca4d078be@candelatech.com>

On Tue, 20 Jan 2026 09:29:56 -0800, Ben Greear wrote:

> >>> On 1/14/26 07:13, Alan Stern wrote:  
> >>>> Unfortunately, we have no to tell from the log you collected
> >>>> which host controller driver encountered this problem.  Nor,
> >>>> unless you can replicate the problem, any way to track down
> >>>> exactly where in that driver the bug is -- or even any way to
> >>>> tell whether a proposed fix actually solves the problem.

Considering this looks like x86-64 I think we can make an educated
guess that the usual suspect was involved.

The guess could be confirmed by running 'lsusb -v' to see if there
is anything *other* than xhci-hcd on this machine at all.

I have seen shutdown hangs many times when I broke this driver in
various ways that caused URBs not to be given back. The unlink
mechanism is complex, with many steps to possibly go wrong.

> We are not able to reproduce the problem.  If we are able to
> reproduce, we'll take more precise notes and provide what details
> we can find.

Chances are you may not see it again, but if you want to hunt for this
bug I would suggest setting the system to enable dynamic debug before
every shutdown. Particularly xhci_hcd module debug if you can confirm
that this is the HCD in use.

It is possible to have those symptoms at shutdown due to a problem that
already began before shutdown, but maybe went unnoticed.

Regards,
Michal

      reply	other threads:[~2026-01-29  9:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14  0:21 Deadlock in usb subsystem on shutdown, 6.18.3+ Ben Greear
2026-01-14  2:45 ` Hillf Danton
2026-01-14 14:36   ` Ben Greear
2026-01-14 15:13     ` Alan Stern
2026-01-14 17:51       ` Ben Greear
2026-01-14 19:26         ` Alan Stern
2026-01-14 20:14           ` Oliver Neukum
2026-01-20 17:29             ` Ben Greear
2026-01-29  9:28               ` Michal Pecio [this message]

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=20260129102819.77378628.michal.pecio@gmail.com \
    --to=michal.pecio@gmail.com \
    --cc=greearb@candelatech.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.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