The sr300 hardware reset will result usb host controller die

[kath]

We use TX2 with the BSP package L4T_r2810. The project information is following:

8G RAM

32G EMMC

Ubuntu 16.4 with kinetic-ros

SR300 is a usb device connecting with TX2 usb

.

But in our project sometimes the NETDEV WATCHDOG occurs in eth1 then the whole usb host controllers die. In addition the issue can be reproduced just 5s after the SR300 send the hardware reset command.

And when we run other ros applications except the sr300 application the usb controller will always in normal state.

Please help to give some advices for these issue . Thanks

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824523] NETDEV WATCHDOG: eth1 (r8152): transmit queue 0 timed out

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824548] ------------[ cut here ]------------

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824552] WARNING: at ffffffc0009b3d3c [verbose debug info unavailable]

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824555] Modules linked in: cp210x fuse rndis_host uvcvideo videobuf2_vmalloc bcmdhd pci_tegra bluedroid_pm

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824568]

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824573] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.38 #1

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824576] Hardware name: quill (DT)

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824578] task: ffffffc0011f4ec0 ti: ffffffc0011e4000 task.ti: ffffffc0011e4000

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824586] PC is at dev_watchdog+0x2ac/0x2bc

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824589] LR is at dev_watchdog+0x2ac/0x2bc

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824592] pc : [<ffffffc0009b3d3c>] lr : [<ffffffc0009b3d3c>] pstate: 60000045

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824594] sp : ffffffc0011e7b40

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824597] x29: ffffffc0011e7b40 x28: ffffffc06bd193b8

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824601] x27: ffffffc0011bbab8 x26: 0000000000000280

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824605] x25: 00000000ffffffff x24: 0000000000000000

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824608] x23: ffffffc06bd193a0 x22: ffffffc001366000

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824611] x21: ffffffc1e0fb2400 x20: ffffffc06bd19000

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824614] x19: ffffffc0011ea000 x18: 0000000000000a03

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824617] x17: 0000007f92133f68 x16: ffffffc0001d77c0

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824620] x15: 001dcd6500000000 x14: 0ffffffffffffffe

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824623] x13: 0000000000000028 x12: ffffffc001204000

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824626] x11: 0000000000000006 x10: 0000000000000000

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824629] x9 : 000000000000045d x8 : 756575712074696d

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824632] x7 : 0000000000000000 x6 : ffffffc0013a4438

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824634] x5 : 0000000000000000 x4 : 0000000000000000

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824637] x3 : 0000000000000000 x2 : 0000000000000102

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824640] x1 : ffffffc0011e4000 x0 : 0000000000000039

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824642]

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824645] ---[ end trace cd74197b3ae6af7a ]---

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.824648] Call trace:

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827092] [<ffffffc0009b3d3c>] dev_watchdog+0x2ac/0x2bc

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827101] [<ffffffc0001055e4>] call_timer_fn+0x50/0x1bc

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827105] [<ffffffc000105910>] run_timer_softirq+0x1ac/0x2a4

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827112] [<ffffffc0000a8974>] __do_softirq+0x10c/0x368

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827116] [<ffffffc0000a8e28>] irq_exit+0x84/0xdc

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827122] [<ffffffc0000f45e4>] __handle_domain_irq+0x6c/0xb4

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827126] [<ffffffc0000815dc>] gic_handle_irq+0x5c/0xb4

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827130] [<ffffffc000084740>] el1_irq+0x80/0xf8

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827137] [<ffffffc0007c8b64>] cpuidle_enter+0x18/0x20

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827141] [<ffffffc0000e7a74>] call_cpuidle+0x28/0x50

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827143] [<ffffffc0000e7c18>] cpu_startup_entry+0x17c/0x340

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827150] [<ffffffc000b126b0>] rest_init+0x84/0x8c

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827157] [<ffffffc0010a297c>] start_kernel+0x39c/0x3b0

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827160] [<0000000080b18000>] 0x80b18000

Jul 30 22:06:41 tegra-ubuntu kernel: [26369.827176] r8152 2-3:1.0 eth1: Tx timeout

Jul 30 22:06:42 tegra-ubuntu kernel: [26370.960515] xhci-tegra 3530000.xhci: xHCI host not responding to stop endpoint command.

Jul 30 22:06:42 tegra-ubuntu kernel: [26370.960524] xhci-tegra 3530000.xhci: Assuming host is dying, halting host.

[MartyG]

An SR300 user in a discussion in the link below also had a problem in 2017 where NETDEV WATCHDOG was timing out and reported it on the RealSense GitHub site.

https://github.com/IntelRealSense/librealsense/issues/409

.If the advice given in that discussion does not solve your problem, I recommend creating a new case on the GitHub by visiting its front page and clicking the 'New Issue' button to repost your question there. Thanks!

https://github.com/IntelRealSense/librealsense/issues/