Re: usbip: Kernel oops when trying to bind devices from Windows client

[Shuah Khan <skhan@linuxfoundation.org>]

On 1/4/26 16:13, Marco Schuschnig wrote:
> Hello all,
> 
> I am trying to get usbip working with a Raspberry Pi Zero 2 W
> (Raspberry Pi OS / Debian Trixie, kernel 6.2.47) as host and a Windows
> 10 machine as client (using usbip-win2 0.9.7.3). The device to be
> shared is a "145f:0276 Trust GXT 165 Gaming Mouse".

Are you using vhci_hcd equivalent on Windows and usbip_host on
Linux? This won't work because usbip_host and vhci_hcd have to
be both Linux systems.

> 
> Upon attaching from the Windows machine, the Raspberry Pi
> kernel-oopses pretty much immediately. Sometimes, the Pi locks up hard
> until it is either power-cycled or the watchdog kicks in, sometimes it
> keeps running. In the latter case, when attempting to detach on the
> Windows machine, another kernel oops follows like in the attached
> stacktrace (sec. 158).
> 
> The issue is fully reproducible, the attached stacktrace was produced
> with usbip_debug_flag=0xFFFFFFFF.
> 
> An issue with the hardware can be ruled out, as when using a Raspberry
> Pi 5 as client (same kernel version) the usbip connection works
> flawlessly. 

Yes this is a supported configuration.

Incidentally, when using the Raspberry Pi 5 as host
> together with the Windows 10 machine as client, usbip works just fine.

I am surprised this works. What's the kernel version Raspberry Pi 5?
> I have tested with the same results an USB keyboard and an Android
> smartphone to rule out a misbehaving USB device.
> 
> It might be possible that the culprit is something Windows does to USB
> devices or a bug in the usbip-win2 package, but even if Windows sends
> corrupt USB packets, these should IMHO not lead to a kernel-oops.

The reason is Windows usbip client and Linux host aren't compatible.
We don't test this case and support this case.

thanks,
-- Shuah