I have a similar problem with an ASMedia device.
Ubuntu 20.04.3 LTS
Linux idallen-oak 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
I have a StarTech SDOCK4U33 4-slot USB 3 hard drive dock using ASMedia Technology:
Bus 004 Device 007: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge
Bus 004 Device 008: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge
Bus 004 Device 009: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge
Bus 004 Device 010: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge
If I reboot my Linux machine, the dock causes these USB errors during the boot:
Jan 18 21:56:52 idallen-oak kernel: [ 13.254357] usb 4-3: device descriptor read/8, error -110
Jan 18 21:57:03 idallen-oak kernel: [ 24.398290] xhci_hcd 0000:00:14.0: Abort failed to stop command ring: -110
Jan 18 21:57:03 idallen-oak kernel: [ 24.400554] xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
Jan 18 21:57:03 idallen-oak kernel: [ 24.402820] xhci_hcd 0000:00:14.0: HC died; cleaning up
Losing that controller at boot means many of my other USB devices are
not detected.
If I unplug the hard drive dock USB cable, the machine boots fine. If I
then plug in the dock USB cable after the machine is up and running,
the above error happens (and I again lose many other USB devices).
Surely plugging in a USB device should not cause the whole controller
to fail and lose all the other working USB devices?
If I power off all of the drives in the hard drive dock and then
power them on, that seems to reset the dock and then everything works
fine again when I reboot. The dock is correctly detected at boot and
everything works. If I then reboot with the dock running, the problem
returns until I power cycle the dock and reboot again.
There is something about this dock that xhci_hcd doesn't like when the
dock is left powered on across a reboot.
More details (syslog, etc.) upon request.