HID device crash the xhci kernel driver

[rpineau]

I was testing a TEMPerHUM usb device and it did crash the usb xhci driver. Once that crash happens, all devices on the usb ports are gone and unplugging/replugging them doesn't bring them back.
The device register itself as an HID device so the kernel assume it's a keyboard... but it's not.

Code: Select all

Feb  9 12:06:15 localhost kernel: [56177.650843@4] hid-generic 0003:413D:2107.0001: input,hidraw0: USB HID v1.11 Keyboard [HID 413d:2107] on usb-xhci-hcd.0.auto-1.2/input0
Feb  9 12:06:25 localhost kernel: [56187.779707@4] xhci-hcd xhci-hcd.0.auto: xHCI host not responding to stop endpoint command.
Feb  9 12:06:25 localhost kernel: [56187.779714@4] xhci-hcd xhci-hcd.0.auto: Assuming host is dying, halting host.
Feb  9 12:06:25 localhost kernel: [56187.795776@4] xhci-hcd xhci-hcd.0.auto: Host not halted after 16000 microseconds.
Feb  9 12:06:25 localhost kernel: [56187.795808@4] xhci-hcd xhci-hcd.0.auto: Non-responsive xHCI host is not halting.
Feb  9 12:06:25 localhost kernel: [56187.795812@4] xhci-hcd xhci-hcd.0.auto: Completing active URBs anyway.
Feb  9 12:06:25 localhost kernel: [56187.795860@4] xhci-hcd xhci-hcd.0.auto: HC died; cleaning up

The same device did the same thing on a Odroid Xu4, but registered fine on 2 different Raspberry PI (a 3B+ and a 4B+).
So it looks like it might be an issue with Odroid kernels
On my N2 I'm running kernel 4.9.210-66

[odroid]

What happens if you connect the device to the OTG port via otg-to-host adapter?
Also check this article.
https://maikel.tiny-host.nl/it-related- ... -on-linux/

[rpineau]

The article is interesting.. but until the device stops crashing the xhci driver it's of very little help.
I'll see if I can borrow it again and test on the OTG port (I gave it back to the friend who lended it to me.. not sure when I can get it back).
The weird thing is that it also did the same on my XU4 but not on the 2 RPIs

[odroid]

Did you try connecting the sensor to the USB 2.0 port on the XU4?
Since we don't have the same device, it is very hard to know what's wrong.

[rpineau]

I connected it to one the usb3 ports, I should have tried the usb2 as it's on a different controller. I understand that without the actual device it's hard to know what's going on.
I might just buy a new one to do more testing. This is the one I tested : https://www.amazon.com/gp/product/B00HW ... M9QJBMR7AY
Rodolphe