USB Port Error on AGX Orin SOM with Jetson Linux 35.5.0 - Mouse/Keyboard Delayed on Boot

Hello Team,

We are using the NVIDIA Jetson AGX Orin SOM with custom hardware, running Jetson Linux version 35.5.0 GA.

I have been encountering continuous error messages in the dmesg logs related to USB port issues. When the system boots, the keyboard and mouse are unresponsive for around 10 seconds, after which they start working, but the error messages persist.

Here are the error logs:

[14536.073227] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
[14540.157398] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
[14544.233328] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
[14548.309055] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
[14552.385198] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
[14556.461135] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
[14560.540845] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
[14564.617021] usb usb2-port3: Cannot enable. Maybe the USB cable is bad?

We have validated our hardware correctly, and it works without issue when tested with older JetPack versions.
Could this issue be related to a software or driver change in Jetson Linux 35.5.0 GA? Any guidance or suggestions to resolve this would be greatly appreciated.

Regards,
Parashuram

One possible and mostly happened case is your USB device tree does not correctly configured and it is kind of relying on some timing to make it work.

Another case is the signal integrity issue.
There is a bug related to the SSC and got fixed on rel-35.5.

Hello Wayne,

Thank you for the prompt response.

  1. USB Device Tree Configuration: We have reviewed our USB device tree configuration and ensured it is set up correctly. However, we still observe the issue despite these efforts.

  2. Signal Integrity Issue: Could you please provide more details on the SSC bug that was fixed in rel-35.5? We are currently using Jetson Linux 35.5.0 GA, so I want to ensure that we have the latest updates and fixes.

If there are any additional steps we can take or specific checks you recommend, please let us know. We are keen to resolve this issue as it affects our development process.

Thank you for your assistance.

Regards,
Parashuram

SSC was disabled in rel-35.4.1 and previous release. This is a bug because SSC should be enabled.

Experimental patch could be found here if you want to disable it again.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.