USB2 problem on J106, WARN Event TRB

Hi everyone,

Recently, we started working with the Auvidea J106 and encountered an issue with one of the USBs that we don’t know how to debug. That’s why we figured it would make sense to see if maybe anyone on the NVIDIA Kernel team has an idea of what’s going on on the software side…

The problem occurs when we connect our cameras - one usb port doesn’t work at all while the other one fails at a rate of ~1/25. We’re connecting Matrixvision Bluefox mlc200wC cameras via USB2 cables. The cameras do light up and also turn “on” (i.e. green status LED) when opening the port in software, but dmesg gets flooded with these messages after opening the camera.

[ 156.301215] tegra-xhci tegra-xhci: WARN Event TRB for slot 1 ep 4 with no TDs queued?
[ 156.349649] tegra-xhci tegra-xhci: WARN Event TRB for slot 1 ep 4 with no TDs queued?
[ 156.398687] tegra-xhci tegra-xhci: WARN Event TRB for slot 1 ep 4 with no TDs queued?
[ 156.448586] tegra-xhci tegra-xhci: WARN Event TRB for slot 1 ep 4 with no TDs queued?
[ 156.500557] tegra-xhci tegra-xhci: WARN Event TRB for slot 1 ep 4 with no TDs queued?
[ 156.549755] tegra-xhci tegra-xhci: WARN Event TRB for slot 1 ep 4 with no TDs queued?
[ 156.603192] tegra-xhci tegra-xhci: WARN Event TRB for slot 1 ep 4 with no TDs queued?
[ 156.654370] tegra-xhci tegra-xhci: WARN Event TRB for slot 1 ep 4 with no TDs queued?
[ 156.706384] tegra-xhci tegra-xhci: WARN Event TRB for slot 1 ep 4 with no TDs queued?
[ 156.756986] tegra-xhci tegra-xhci: WARN Event TRB for slot 1 ep 4 with no TDs queued?
[ 156.807573] tegra-xhci tegra-xhci: WARN Event TRB for slot 1 ep 4 with no TDs queued?
[ 156.857193] tegra-xhci tegra-xhci: WARN Event TRB for slot 1 ep 4 with no TDs queued?
[ 156.908195] tegra-xhci tegra-xhci: WARN Event TRB for slot 1 ep 4 with no TDs queued?

lsusb:
ubuntu@tegra-ubuntu:~$ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0955:09ff NVidia Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 164c:0103 Matrix Vision GmbH mvBlueFOX camera
Bus 001 Device 002: ID 164c:0103 Matrix Vision GmbH mvBlueFOX camera
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hu

After replugging any of the cameras, we have to completely power cycle the system before anything works again. Both the Matrixvision default GUI as well as our ROS node using their driver cause this problem.

Any idea what this might be related to? Do you know where that USB warning is coming from in dmesg?

We have also swapped cameras/cables/etc. to no avail.

System Info:

R24 (release), REVISION: 2.1, GCID: 8028265, BOARD: t210ref, EABI: aarch64, DATE: Thu Nov 10 03:51:59 UTC 2016

We primarily see this problem on the second USB port - the one which is USB 2 only. The dev kit does not have this port. The first USB port (USB 3) does not have this problem - at least it is very rare. So it is hard to compare it to the dev kit.

Is there any chance to find out, what this error message means?

Thanks!

Hi MarGy,
Please refer to USB Lane Mapping in
Tegra_Linux_Driver_Package_Documents_R24.2.1  --> Start_L4T_Docs.html --> Downloads --> Platform Adaptation and Bring-Up Guide (PDF)

What is the case of the custom board? Have you revised the device tree per the section?

Hi MarcGy,

Have you revised the device tree per the section?
Or you have found the cause and resolved this problem?

Thanks