Here is the lsusb on the client when the device fails to attach --------------------------------------- michael@ubuntu:~$ lsusb Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Here is the lsusb on the host before use ----------------------------------------------------- pi@raspberrypi:~ $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 045e:02e6 Microsoft Corp. Wireless XBox Controller Dongle Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub On Sat, 24 Jul 2021 at 02:29, Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx> wrote: > > On 7/21/21 8:27 PM, Michael wrote: > > You can pass through any bluetooth dongle (or xbox wireless dongle) through usbip and it will cause this issue. > > > > For example, here is one of my customers https://www.virtualhere.com/comment/9432#comment-9432 <https://www.virtualhere.com/comment/9432#comment-9432> with the issue. > > > > The device is in the VDEV_ST_USED state when a reset occurs and so its never re-enabled > > > > Furthermore there is a bug in the line pr_err("vhci_device speed not set\n"); > > (L479) because resetting a full-speed device is not an error. > > > > Can you provide me the full demsg from host and client including the part > where device is attached? I assume usbip tools from Linux sources are used? > > Also send me lsusb output on host and client > > thanks, > -- Shuah
