Comment 4 for bug 1979886

The success with 22.04 xHCI depends on the hardware vintage. 2016– 3.1 hardware seems to work better than 2012 3.0 hardware

xHCI fails with particular devices and a combination of host hardware and single-tier intermediate hubs has to be tested out. Some host hardware and endpoint device combinations cannot be made to work for xHCI 22.04

To avoid the xHCI dead bug that shuts down all usb on the host, the troubled device should be connected via an intermediate hub, preferably a Realtek chip hub

Although usb supports 7 tiers of hubs, possibly no device works with 2 or more tiers for 22.04 xHCI

04e8:61f5 at 10 Gb/s direct to host with 2018 hardware experiences disconnect within 24 hours 5.15.0-40-generic xHCI
Jul 2 13:18:19 x kernel: [77760.394807] usb 6-2: USB disconnect, device number 3

Although one 0bda:8153 works on a dedicated port 5 Gb/s 2012 hardware 5.15.0-40-generic xHCI, a second device fails within than 7 hours:
Jul 02 21:25:53 c32z kernel: usb 4-2: USB disconnect, device number 3
Jul 02 21:25:53 c32z kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
— after that the device fails to be recognized even after a reboot although it works on an identical host-clone set-up
— the second device could finally be made working by inserting a 0bda:0423 hub, now exhibiting an uptime exceeding 10 hours

No VIA devices 2109: appears to work with 2012 hardware for any hub layout

It appears xHCI is not tested for more than 1 tier of hubs and I believe this has never worked for xHCI as opposed to ehci