From: Jiayi Li <lijiayi@kylinos.cn>
To: Michal Pecio <michal.pecio@gmail.com>
Cc: Oliver Neukum <oneukum@suse.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org,
usb-storage@lists.one-eyed-alien.net,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] usb: uas: quiesce SCSI before stopping endpoints on driver unbind
Date: Mon, 21 Sep 2026 17:44:14 +0800 [thread overview]
Message-ID: <60d7692e-4d8e-4b94-b45d-a530bc2cff72@kylinos.cn> (raw)
In-Reply-To: <20260921092615.7402711d.michal.pecio@gmail.com>
Hi Michal,
> This is actually an anomaly, transfer events should always point
> to valid rings. Device sendig bogus Stream ID would be code 34:
> Invalid Stream ID Error.
>
> Is this an ASMedia host controller? PCI ID doesn't looke like one...
The original controller was not ASMedia. It was a Zhaoxin xHCI
controller, PCI ID 1d17:9204.
I have now reproduced the same post-rebind failure with the same USB
storage bridge (USB ID 2109:0715) and workload on an Intel xHCI
controller (PCI ID 8086:a2af). This additional run used
6.14.0-27-generic.
The relevant post-bind log is:
scsi host7: uas
scsi 7:0:0:0: tag#4 data cmplt err -75 uas-tag 1 inflight: CMD
scsi 7:0:0:0: tag#4 CDB: Inquiry 12 00 00 00 24 00
scsi 7:0:0:0: tag#4 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
scsi host7: uas_eh_device_reset_handler success
...
scsi 7:0:0:0: tag#7 CDB: Test Unit Ready 00 00 00 00 00 00
scsi host7: uas_eh_device_reset_handler success
sd 7:0:0:0: Device offlined - not ready after error recovery
There was no "Transfer event 26 for unknown stream ring" message in the
Intel run. Therefore, I agree that event 26 is anomalous, but it is not
required for the storage failure and appears to be a secondary symptom
specific to the original run. The first post-bind failure is the
Data-In completion error on INQUIRY, and the same error occurs on both
controllers.
Thanks,
Jiayi
next prev parent reply other threads:[~2026-09-21 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 1:23 Jiayi Li
2026-09-20 2:34 ` Alan Stern
2026-09-21 2:58 ` Jiayi Li
2026-09-21 7:26 ` Michal Pecio
2026-09-21 9:44 ` Jiayi Li [this message]
2026-09-21 10:24 ` Oliver Neukum
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=60d7692e-4d8e-4b94-b45d-a530bc2cff72@kylinos.cn \
--to=lijiayi@kylinos.cn \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michal.pecio@gmail.com \
--cc=oneukum@suse.com \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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®