Any update of PCIe driver and/or USB3.0 driver for TX2's L4T ?

Autonomous Machines Jetson & Embedded Systems Jetson TX2
21

Log files attached in #17 have following log

[  240.657268] xhci_hcd 0000:04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk?
[  240.677016] xhci_hcd 0000:04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk?
[  240.689603] xhci_hcd 0000:04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk?
[  240.712873] xhci_hcd 0000:04:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk?

and this should be fixed with https://devtalk.nvidia.com/default/topic/1027100/jetson-tx2/stream-4-cameras-with-gstreamer/post/5225245/#5225245 patch. Can you please confirm that this patch is applied correctly?

22

hi vidyas,

Sorry for my late response.
When I applied the patch, the XHCI_TRUST_TX_LENGTH error disappeared in the log but the problem with basler USB3.0 camera occurred as ever.
Also, when I applied R28.2, it is same above result. Please see log file atttached #20.

Thanks,

23

This looks more like device specific issue.
Can you please try the patch mentioned in Re: xhci_hcd WARN Event TRB for slot ep with no TDs queued? — Linux USB ?
Also, do you see this issue when the USB camera is connected directly to native USB3.0 slot?

24

hi vidyas,

What is the “device” of device specific issue you are taking about?
Is it the USB camera ? or the TX2?
This issue does not occur on TX1 w/ L4T R28.1. So, I don’t think the problem of camera side.
However, this issue occurs on TX2 w/ both L4T R28.1 and R28.2.
So, I think the problem cause is not camera side but TX2 side.

Also, this issue occurs when using native USB3.0 port of TX2.

Is the implementation of xhci-ring.c different between TX1 and TX2 of L4T?
(Is it really worth applying the patch?)

Best Regards,

25

Thanks for confirming that the issue happens on native USB3.0 port also. That makes it clear that there is no issue with PCIe as such. I’m still surprised that the issue doesn’t occur on TX1 with same R28.1
And yes, the patch is worth a try.

26

Hi nanoto,

Have you clarified cause and resolved the problem? Any positive result?

Thanks