From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221340] uas driver hangs and causes usb reset
Date: Fri, 10 Apr 2026 04:56:47 +0000 [thread overview]
Message-ID: <bug-221340-208809-qLxbitgZeE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221340-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221340
Michał Pecio (michal.pecio@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michal.pecio@gmail.com
--- Comment #3 from Michał Pecio (michal.pecio@gmail.com) ---
There is also Unmap/Read sub-channel in this log.
By "hang", do you mean that no I/O happens for 30 seconds or some other time
before these messages show up?
BTW, if you run (as root)
echo 'func handle_tx_event +p' >/proc/dynamic_debug/control
do you see anything new appear in dmesg at this time?
That would point to some "action" at xHCI layer, though I suppose it's also
possible that nothing interesting happens and the device simply never responds
to some commands under some circumstances.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-04-10 4:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 20:56 [Bug 221340] New: uas driver hangs and causes usb reset bugzilla-daemon
2026-04-09 21:24 ` [Bug 221340] " bugzilla-daemon
2026-04-09 21:43 ` bugzilla-daemon
2026-04-10 4:56 ` bugzilla-daemon [this message]
2026-04-10 16:45 ` bugzilla-daemon
2026-04-10 19:55 ` bugzilla-daemon
2026-04-11 13:03 ` bugzilla-daemon
2026-04-11 22:11 ` bugzilla-daemon
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=bug-221340-208809-qLxbitgZeE@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.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