mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ambareesh Balaji <ambareeshbalaji@gmail.com>
To: Michal Pecio <michal.pecio@gmail.com>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: xhci: Tear down host on Reset Endpoint and Set TR Dequeue timeout
Date: Wed,  4 Nov 2026 21:41:35 +0000	[thread overview]
Message-ID: <20261104214135.396018-1-ambareeshbalaji@gmail.com> (raw)
In-Reply-To: <20261104105003.3ca4a3ac.michal.pecio@gmail.com>

On Wed, 4 Nov 2026 10:50:03 +0100, Michal Pecio wrote:
> If this happens on real HW then it's a different thing. Having logs
> of this anomaly would surely help untangling what happens there.
>
> Were you seeing these issues before 7.3? That release made changes to
> the handling of URBs on disconnected devices, which caused some people
> problems even in absence of host controller bugs.

Makes sense, thanks for pointing that out. I'll send the logs and the
xHCI trace as soon as I capture one, and I will treat it as a separate
issue from this patch.

Yes, I saw these hangs before 7.3 as well, so I do not think it is a
7.3 regression. I have no logs from those earlier occurrences, so I
can only vouch for the symptom (the device drops off the bus and the
hang needs a reboot), not that it is the same code path.

Scarlett also likes to reset/disconnect with -71 and -110 errors fairly
often. The kernel generally re-enumerates it, but once in a while I do
see the disconnect get stuck.

Regards,
Ambareesh

      reply	other threads:[~2026-11-04 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04  1:27 Ambareesh Balaji
2026-11-04  9:15 ` Michal Pecio
2026-11-04  9:36   ` Ambareesh Balaji
2026-11-04  9:50     ` Michal Pecio
2026-11-04 21:41       ` Ambareesh Balaji [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=20261104214135.396018-1-ambareeshbalaji@gmail.com \
    --to=ambareeshbalaji@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=michal.pecio@gmail.com \
    /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

all inboxes | Powered by JetHome®