tegra-xusb-mbox: Controller firmware hang

Hey doksmf,

Were you able to figure out what was going on?? I’m running into the same issue running into the same issue. Please see the relevant section of the kernel log.

Feb 11 08:42:34 tegra-ubuntu kernel: [  886.221089] 509-17000000.gp10b, pid 1165, refs: 2: 
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.225933] channel status:  in use idle not busy
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.230969] RAMFC : TOP: 0000000000000000 PUT: 0000000000000000 GET: 0000000000000000 FETCH: 0000000000000000
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.230969] HEADER: 60400000 COUNT: 00000000
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.230969] SYNCPOINT 00000000 00000000 SEMAPHORE 00000000 00000000 00000000 00000000
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.252977] 
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.254480] 510-17000000.gp10b, pid 1165, refs: 2: 
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.259299] channel status:  in use idle not busy
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.264328] RAMFC : TOP: 0000000000000000 PUT: 0000000000000000 GET: 0000000000000000 FETCH: 0000000000000000
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.264328] HEADER: 60400000 COUNT: 00000000
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.264328] SYNCPOINT 00000000 00000000 SEMAPHORE 00000000 00000000 00000000 00000000
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.286427] 
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.287930] 511-17000000.gp10b, pid 1165, refs: 2: 
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.292798] channel status:  in use idle not busy
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.297803] RAMFC : TOP: 0000000000000000 PUT: 0000000000000000 GET: 0000000000000000 FETCH: 0000000000000000
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.297803] HEADER: 60400000 COUNT: 00000000
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.297803] SYNCPOINT 00000000 00000000 SEMAPHORE 00000000 00000000 00000000 00000000
Feb 11 08:42:34 tegra-ubuntu kernel: [  886.320637] 
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.233374] xhci-tegra 3530000.xhci: Stopped the command ring failed, maybe the host is dead
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.281520] xhci-tegra 3530000.xhci: Host not halted after 16000 microseconds.
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.288766] xhci-tegra 3530000.xhci: Abort command ring failed
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.294652] xhci-tegra 3530000.xhci: HC died; cleaning up
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.301005] usb 1-1: USB disconnect, device number 2
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.306074] usb 1-1.2: USB disconnect, device number 4
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.315000] xsens_mt ttyUSB0: xsens_mt converter now disconnected from ttyUSB0
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.324817] xsens_mt 1-1.2:1.1: device disconnected
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.333203] usb 1-1.4: USB disconnect, device number 5
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.360944] usb 1-3: USB disconnect, device number 3
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.367351] usb 1-3.1: USB disconnect, device number 12
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.376416] usb 1-3.2: USB disconnect, device number 13
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.386633] usb 1-3.3: USB disconnect, device number 6
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.394041] usb 1-3.4: USB disconnect, device number 7
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.401614] usb 1-3.4.4: USB disconnect, device number 9
Feb 11 08:42:42 tegra-ubuntu kernel: [  894.408043] usb 1-3.4.4.4: USB disconnect, device number 11

I’m running a TX2 with 3 USB3 cameras on a hub. I have some heavy usage on the CPUs but haven’t maxed out the cores.

Although one thing that I have observed is that it usually doesn’t crash if I’m interacting with the system . I’m not sure if its relevant. Initially I suspected a thermal issue, thought it was happening due to over heating or something, but then I ventilated it a couple of fans (TX2 sits in an enclosure), But this still occurs from time to time…

I have another TX2 that I run the same setup on, but i haven’t encountered this problem on that … May be I have a faulty unit?

Any insight would be helpful…

Thanks

1 Like