USB warm rebooting issue

Hi,

I am using intel D415 camera. i saw after warm reboot (sudo reboot). the usb camera does not work. is there workaround that we can reset usb or do cold reboot the system as code reboot seem work fine.

please see attached log

Hi,
It should work to perform power cycle to the embedded hub and check if enumeration happens.
Please check
https://elinux.org/L4T_Jetson/r32.3.x_patch
[Jetson Nano]Power control

thanks Dane,

which patch do i need apply ?? below two related to Nano ??

[TX2]Not enough host controller resources for new device state xbox 360 controller through USB hub - broken in Jetpack 4.x, works in Jetpack 3.x (Not enough host c...

[Jetson Nano]Power control USB Power control

[Jetson Nano]Do USB2 compliance test on USB hub Jetson Nano USB2.0 Tuning Guide ~ Bus error (core dumped)

hi Dane,

I run power_cycle prior to sudo reboot. it does not help after reboot I still got below err

[ 67.847920] usb 2-1.3: Device not responding to setup address.
[ 68.070446] usb 2-1.3: Device not responding to setup address.
[ 68.282399] usb 2-1.3: device not accepting address 92, error -71
[ 68.418836] usb 2-1.3: Device not responding to setup address.
[ 68.646932] usb 2-1.3: Device not responding to setup address.
[ 68.858425] usb 2-1.3: device not accepting address 93, error -71
[ 69.313728] usb 2-1.3: Device not responding to setup address.
[ 69.541913] usb 2-1.3: Device not responding to setup address.
[ 69.754375] usb 2-1.3: device not accepting address 94, error -71
[ 69.896497] usb 2-1.3: Device not responding to setup address.
[ 70.124578] usb 2-1.3: Device not responding to setup address.
[ 70.338149] usb 2-1.3: device not accepting address 95, error -71
[ 70.347131] usb 2-1-port3: unable to enumerate USB device
[ 70.641163] usb 2-1.3: Device not responding to setup address.
[ 70.869403] usb 2-1.3: Device not responding to setup address.
[ 71.085977] usb 2-1.3: device not accepting address 96, error -71
[ 71.217608] usb 2-1.3: Device not responding to setup address.
[ 71.446155] usb 2-1.3: Device not responding to setup address.
[ 71.658204] usb 2-1.3: device not accepting address 97, error -71
[ 72.112636] usb 2-1.3: Device not responding to setup address.
[ 72.341065] usb 2-1.3: Device not responding to setup address.
[ 72.554184] usb 2-1.3: device not accepting address 98, error -71
[ 72.695396] usb 2-1.3: Device not responding to setup address.
[ 72.918757] usb 2-1.3: Device not responding to setup address.
[ 73.130343] usb 2-1.3: device not accepting address 99, error -71
[ 73.136928] usb 2-1-port3: unable to enumerate USB device

do a hotplug camera does fixed the issue. otherwise all usb input are freezed.

Hi @terry8uwg2,

I have seen the same behaviour when using a D415 Realsense camera. You can do a bind/unbind to the camera USB port. Please refer to the following guide: https://developer.ridgerun.com/wiki/index.php?title=How_to_reset_USB_port_on_Jetson

Hi Thanks.

so do you do unbind before sudo reboot ??

@terry8uwg2

You can do the unbind then the bind, and the camera should work without needing to reboot the jetson.

okay thanks. will give a try

@fabian.solano many thanks for sharing suggestion.

@DaneLLL

the original signiature “device not accepting address 96, error -71” seems go aways . but after few hundreds of warm reboot. i found system can not boot. hdmi stuck at NVIDIA splah logo screen.

uart log stop at here .

Hit any key to stop autoboot: 0
MMC: no card present
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1…
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
733 bytes read in 85 ms (7.8 KiB/s)
1: primary kernel
Retrieving file: /boot/initrd
5487751 bytes read in 242 ms (21.6 MiB/s)
Retrieving file: /boot/Image
34191368 bytes read in 807 ms (40.4 MiB/s)
append: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_inft

Flattened Device Tree blob at 83100000

Booting using the fdt blob at 0x83100000
reserving fdt memory region: addr=80000000 size=20000
Using Device Tree in place at 0000000083100000, end 000000008317770a

Starting kernel …

[ 1.097860] tegradc tegradc.1: dpd enable lookup fail:-19

@DaneLLL my previous post is after applying [Jetson Nano]Power control.

Hi @kayccc i also tried unbind and bind as you suggested . but the command seems does not run. i used below command.

sudo chmod 666 /sys/bus/usb/drivers/usb/bind /sys/bus/usb/drivers/usb/unbind
should I use
echo “2-1.3” | sudo tee /sys/bus/usb/drivers/usb/unbind
or
echo “2-1” | sudo tee /sys/bus/usb/drivers/usb/unbind

neither them execute for me

Thanks,

Hi @terry8uwg2,

You should use the USB label that you can identify when you connect the camera.

First delete log by using
sudo dmesg -c

Then connect the camera and
dmesg

There you can identify which USB label you should use. In the example from the link I provided
echo "2-1" | sudo tee /sys/bus/usb/drivers/usb/unbind

was used because camera was detected in port 2-1

Regards,
Fabian