[BUG] UAS protocol hangs on Realtek RTL9210B (0bda:9210, bcdDevice f0.01)

[Nils Reuter <nils.reuter@gmx.net>]

Hello,

I would like to report a persistent UAS protocol issue with a Realtek 
RTL9210B based M.2 enclosure.

*Hardware Environment:*

  *

    Enclosure: Ugreen SKU 15813 (Model CM767)

  *

    Bridge Chip: Realtek RTL9210B (ID 0bda:9210, bcdDevice f0.01)

  *

    Drive: Transcend TS512GMTS430S (SATA M.2)

  *

    System: Debian / OpenMediaVault (Linux omv 6.18.12+deb13-amd64)

  *

    Kernel: 6.18.12-amd64

*Problem Description:* Under heavy I/O load (e.g., backup operations), 
the device experience UAS protocol hangs. The kernel log shows multiple 
|uas_eh_abort_handler| events, followed by SCSI read/write errors and a 
device reset (error -71). Eventually, the device is offlined or 
remounted as read-only.

SMART logs show incrementing UDMA CRC errors (Attribute 199) during 
these events, even though the hardware (cable/SSD) tests fine on other 
platforms.

*Logs:*

|[timestamp] sd 1:0:0:0: [sdb] tag#18 uas_eh_abort_handler 0 uas-tag 15 
inflight: CMD IN [timestamp] usb 2-1-port3: cannot reset (err = -71) 
[timestamp] sd 1:0:0:0: Device offlined - not ready after error recovery |

*Workaround:* The device works perfectly stable when UAS is disabled via 
usb-storage quirks: |options usb-storage quirks=0bda:9210:u|

*Request:* Please consider adding this device (0bda:9210 with bcdDevice 
f0.01) to the kernel's UAS quirks list to ensure out-of-the-box 
stability for other users.

Best regards, Nils Reuter


-- 
Nils Reuter
Houbirggasse 7
90482 Nürnberg

nils.reuter@gmx.net