Comment # 2 on bug 1203718 from Anonymous User

Well, it turns out my last comment aged badly:

I have just repeated my test procedure (essentially verifying one of my borg
archives) in various configurations with the following results:
1. When I connect my external case to my laptop's USB 3.2 Gen 1 port, both
usb-storage and uas will not have to reset the device.
2. When I connect my external case to my laptop's Thunderbolt 3 port, which
falls back to USB 3.2 Gen 2, there are no device resets when using uas either
(and I skipped testing usb-storage).
3. Only when I connect my external case via my USB 3.2 Gen 2 hub from Delock,
see my above comment, to my laptop's Thunderbolt 3 port, both usb-storage and
uas will trigger the device resets reported above.

So I guess this is either a problem with the hub itself or with this particular
combination of hub and external case. Unfortunately, I am not sure how I can
proceed to help with resolving the observed issues when using the hub there
certainly were no messages in /var/log/messages hinting at the hub itself. The
only discernible difference is that while the external case does not support
USB power delivery (and has to be powered via an AC adapter), the hub does
support it. Can this interfere with the packets received by the usb-storage and
uas drivers?