From: Juhyung Park <qkrwngud825@gmail.com>
To: Hongling Zeng <zenghongling@kylinos.cn>, stern@rowland.harvard.edu
Cc: linux-usb@vger.kernel.org, usb-storage@lists.one-eyed-alien.net,
zhongling0719@126.com, gregkh@linuxfoundation.org
Subject: Re: [PATCH v6 2/3] usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS
Date: Mon, 31 Oct 2022 15:17:48 +0900 [thread overview]
Message-ID: <fa0556e5-e154-a4e6-6b18-4996a01d2f10@gmail.com> (raw)
In-Reply-To: <1663210188-5485-1-git-send-email-zenghongling@kylinos.cn>
Hi,
I'm speaking from my own experience but RTL9210 is arguably the most
reliable NVMe-to-USB converter available.
Compared to solutions from JMicron (multiple revisions) and ASMedia,
RTL9210 gave the lowest power consumption (from implementing proper
power management commands) and the least headache.
I personally own multiple enclosures and not one gave a single UAS error
from multiple platforms (Android, Intel, AMD) for years, but with this
commit now, it effectively disables UAS for all RTL9210 enclosures.
Would it be possible to apply this quirk only to a specific firmware
(range)? RTL9210 have a lot of possible firmware combinations:
https://www.station-drivers.com/index.php/en/component/remository/Drivers/Realtek/NVMe-USB-3.1/lang,en-gb/
RTL9210 was available since 2019 and the fact that this quirk came up
this late leads me to believe that this is not a widespread issue and
it'll be a shame if all of RTL9210s are blacklisted from UAS with Linux
from now on :(
If any additional information is required, please let me know.
Thanks,
On 9/15/22 11:49, Hongling Zeng wrote:
> The UAS mode of Hiksemi USB_HDD is reported to fail to work on several
> platforms with the following error message, then after re-connecting the
> device will be offlined and not working at all.
>
> [ 592.518442][ 2] sd 8:0:0:0: [sda] tag#17 uas_eh_abort_handler 0 uas-tag 18
> inflight: CMD
> [ 592.527575][ 2] sd 8:0:0:0: [sda] tag#17 CDB: Write(10) 2a 00 03 6f 88 00 00
> 04 00 00
> [ 592.536330][ 2] sd 8:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1
> inflight: CMD
> [ 592.545266][ 2] sd 8:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 07 44 1a 88 00
> 00 08 00
>
> These disks have a broken uas implementation, the tag field of the status
> iu-s is not set properly,so we need to fall-back to usb-storage.
>
> Signed-off-by: Hongling Zeng <zenghongling@kylinos.cn>
> ---
> Change for v1
> - Change the email real name and the code worng place.
>
> Change for v2
> -Change spelling error.
>
> Change for v3
> -Add acked-by
>
> Change for v4
> -Fix version error
>
> Change for v5
> -change version
>
> Change for v6
> -Change the git message for patch 3
> ---
> drivers/usb/storage/unusual_uas.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/usb/storage/unusual_uas.h b/drivers/usb/storage/unusual_uas.h
> index a6bf87a..8a18d58 100644
> --- a/drivers/usb/storage/unusual_uas.h
> +++ b/drivers/usb/storage/unusual_uas.h
> @@ -149,6 +149,13 @@ UNUSUAL_DEV(0x0bc2, 0xab2a, 0x0000, 0x9999,
> USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> US_FL_NO_ATA_1X),
>
> +/* Reported-by: Hongling Zeng <zenghongling@kylinos.cn> */
> +UNUSUAL_DEV(0x0bda, 0x9210, 0x0000, 0x9999,
> + "Hiksemi",
> + "External HDD",
> + USB_SC_DEVICE, USB_PR_DEVICE, NULL,
> + US_FL_IGNORE_UAS),
> +
> /* Reported-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> */
> UNUSUAL_DEV(0x13fd, 0x3940, 0x0000, 0x9999,
> "Initio Corporation",
next prev parent reply other threads:[~2022-10-31 6:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 2:49 [PATCH v6 2/3] usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS Hongling Zeng
2022-09-15 19:32 ` Alan Stern
[not found] ` <2fcdca5a-2deb-66ca-fd1d-c3ba719b19af@126.com>
2022-09-16 17:21 ` Alan Stern
2022-09-18 12:25 ` zhongling0719
2022-09-22 8:17 ` nana
2022-09-22 15:16 ` Alan Stern
2022-10-31 6:17 ` Juhyung Park [this message]
2022-11-09 10:40 ` Greg KH
2022-11-12 7:45 ` zhongling0719
2022-11-12 7:56 ` Greg KH
2023-01-09 12:00 ` Juhyung Park
2023-01-09 11:58 ` Juhyung Park
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=fa0556e5-e154-a4e6-6b18-4996a01d2f10@gmail.com \
--to=qkrwngud825@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
--cc=zenghongling@kylinos.cn \
--cc=zhongling0719@126.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;
as well as URLs for NNTP newsgroup(s).