Jetson NX hangs - followup with serial log

Hi,

We had a previous discussion here:

Jetson NX hangs - no interaction except for ping

It took us a while to extract valuable logs from the serial interface, and here it is attached.
jetson_log_b12.txt (593.2 KB)

I’d appreciate any help with that.

Kind regards,
Moti.

Hi moti4,

Are you using the devkit or custom board for Xavier NX?


[2025-02-10 03:36:47]-[314302.861706] tegra-xusb 3610000.xhci: WARN Event TRB for slot 9 ep 6 with no TDs queued?

[2025-02-10 03:36:48]-[314303.450714] bpmp: mrq 27 took 1244000 us

[2025-02-10 03:37:07]-[314322.934487] INFO: rcu_preempt detected stalls on CPUs/tasks:
[314322.934641] 	(detected by 5, t=5252 jiffies, g=16610465, c=16610464, q=632)
[314322.934796] All QSes seen, last rcu_preempt kthread activity 5252 (4373473487-4373468235), jiffies_till_next_fqs=1, root ->qsmask 0x0
[314322.935168] rcu_preempt kthread starved for 5252 jiffies! g16610465 c16610464 f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0

[2025-02-10 03:37:41]-[314356.922265] BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=0 stuck for 54s!

From the log you shared, it seems caused from USB device.
Do you connect multiple USB devices on your setup?

[2025-02-09 18:38:53]-[282029.403972] usb 2-3.2: usbfs: process 12471 (.NET ThreadPool) did not claim interface 0 before use
[282029.422093] usb 2-3.2: usbfs: process 20132 (0-1) did not claim interface 1 before use

It indicates that the .NET ThreadPool process does not claim USB interface before use. Or it may be caused from multiple process request for the same USB port.

Could you share the steps how do you reproduce the issue?

Hi,

I am Moti4’s teammate.

Regarding your questions:

We are using DevKit and connecting multiple USB devices.
We have not been able to reproduce the issue because we do not know what leads to the system hanging. This occurs every few days without a clear pattern.

Kind regards,
Tehila

Would you hit the issue if you remove all USB devices?
If not, please help to clarify which USB device causes this error and let us know what you are running.