You are not logged in.
I've been playing with my ESP32, and sometimes it happens that all the usb ports (including usb C) on my Lenovo V15 G3 stop working after some time. I cant know for sure if it has to do with me plugging or unplugging the ESP32, but its happening with this device specifically. Other USB devices (usb hub with usb, hdmi, ethernet, STLinkV2, and arduinos) dont make the xHCI controller die. This is what I can see on dmesg when the controller dies:
...
[ 2449.935850] usb 3-9: USB disconnect, device number 6
[ 2451.604821] usb 3-9: new full-speed USB device number 7 using xhci_hcd
[ 2451.731238] usb 3-9: New USB device found, idVendor=1a86, idProduct=55d4, bcdDevice= 4.44
[ 2451.731256] usb 3-9: New USB device strings: Mfr=0, Product=2, SerialNumber=3
[ 2451.731260] usb 3-9: Product: USB Single Serial
[ 2451.731263] usb 3-9: SerialNumber: 5829058041
[ 2451.734011] cdc_acm 3-9:1.0: ttyACM0: USB ACM device
[ 3253.308927] xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command
[ 3253.308953] xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
[ 3253.308972] xhci_hcd 0000:00:14.0: HC died; cleaning up
[ 3253.309003] usb 3-8: USB disconnect, device number 2
[ 3253.309134] xhci_hcd 0000:00:14.0: Timeout while waiting for stop endpoint command
[ 3253.310142] usb 3-9: USB disconnect, device number 7
[ 3253.310610] usb 3-10: USB disconnect, device number 3After that, everything USB related disappears, even the webcam. lsusb outputs:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubI dont know where to start looking on. Its not something about power managment or suspension, since I've had the laptop running (without using the ESP32) for a week straight, with suspensions in between.
Offline
Similar issue here on lenova x240 with disconnection of ports but not sure of cause
[58099.769298] xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command
[58099.769329] xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
[58099.769421] xhci_hcd 0000:00:14.0: Timeout while waiting for stop endpoint command
[58099.769444] xhci_hcd 0000:00:14.0: HC died; cleaning up
[58099.769526] usb 2-3: USB disconnect, device number 2
[58099.769550] usb 2-3.4: USB disconnect, device number 4
[58099.769566] usb 2-3.4.1: USB disconnect, device number 6
[58099.769802] usb 3-3: USB disconnect, device number 2
[58099.771214] usb 2-3.4.2: USB disconnect, device number 9
[58099.779608] Bluetooth: hci0: sending frame failed (-19)
[58099.798280] Bluetooth: hci0: sending frame failed (-19)
[58099.804141] usb 2-3.4.3: USB disconnect, device number 8
[58099.817628] Bluetooth: hci0: sending frame failed (-19)
[58099.835592] Bluetooth: hci0: sending frame failed (-19)
[58099.891243] usb 2-4: USB disconnect, device number 16
[58099.891719] cdc_mbim 2-4:1.6 wwp0s20u4i6: unregister 'cdc_mbim' usb-0000:00:14.0-4, CDC MBIM
[58099.900824] usb 2-7: USB disconnect, device number 5
[58099.913143] usb 2-8: USB disconnect, device number 7
[58099.995667] wireplumber[1302]: segfault at 0 ip 0000768ba19028ab sp 00007ffde93f7158 error 4 in libc.so.6[16e8ab,768ba17b8000+171000] likely on CPU 1 (core 0, socket 0)
[58099.995685] Code:Offline
I've come across another device that "kills" the xHCI controller. It's a development board that uses both USB (for comms) and an external supply, but the thing is that the board can pull power from the USB (quite a lot appearently), thus killing the controller.
I'm pretty sure this has to do with an overcurrent protection of the controller itself. I say this because on my esp32 project I'm using components that get close to the 300-400mA consumption (which is in theory close to the USB limit), and I've only noticed the issue with that specific project, not all the esp32s I have...
The overcurrent protection somehow resets the controller and seems to never be initialized again.
I'm looking on how can I get logs that spit more information about the reasons of disconnection of usb devices
Offline