Test environment: jetpack 5.2.1
Test module: jetpack-Orin-AGX 64G
Test command: reboot
When OrinAGX executes reboot, it prints a call trace, becomes unresponsive and fails to proceed, displays an RCU error, and is then restarted by the watchdog after two minutes.
Hi,KevinFFF
we are using custom board for AGX Orin 64G,JetPack 5.1.2. And we have applied the RT real-time kernel patch.
This issue is not 100% reproducible, but it occurs with a fairly high probability.
When I run the reboot command, under normal conditions,the following LOG is always printed; however, I’m not sure whether the two are necessarily related.
root@ubuntu:~# reboot
[10689.875030] tegra-xudc 3550000.xudc: setup request failed: -22
[10692.737613] watchdog: watchdog0: watchdog did not stop!
[10693.070063] WARNING: CPU: 7 PID: 1 at kernel/workqueue.c:3047 __flush_work.isra.0+0x20c/0x220
[10693.070371] —[ end trace 20b6eb2cf4c400d6 ]—
[10694.533277] arm-smmu 8000000.iommu: disabling translation
[10694.533347] arm-smmu 10000000.iommu: disabling translation
[10694.533377] arm-smmu 12000000.iommu: disabling translation
[10694.533589] reboot: Restarting system
?釹hutdown state requested 1
Rebooting system …
?
I have conducted tests on the devkit and found that the aforementioned error log does not appear on the devkit. It can reboot normally.
We have tested on the custom board and found that both the real-time kernel and the non-real-time kernel will report errors upon reboot, and the aforementioned issue still occurs.
Can you provide a direction for troubleshooting? Which module might be causing this?
From the results you shared, it seems the issue is specific to your custom carrier board rather than rt kernel.
To clarify the issue, could you also verify the latest Jetpack 5.1.5(r35.6.2) on your custom carrier board?
Is there more logs before you got rcu related messages?
Or do you run any custom application on your board?