NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0]
our dev board + xavier module
jetpack4.2.2
what’s problems?
For reference, JetPack is just the front end to the flash software, and what actually gets flashed is L4T (Ubuntu is called L4T when the NVIDIA drivers are added). It sounds like your release is quite old. Check your L4T release with “head -n 1 /etc/nv_tegra_release”.
Your JetPack version implies an L4T R32.x which is old even within the R32.x. You will probably need to migrate to L4T R32.7.5 to start with:
https://developer.nvidia.com/linux-tegra
(this leads to the JetPack/SDK Manager as well)
A lot of bugs will be fixed just going to the most recent R32.x.
Next, you will most likely be asked to try this on a dev kit carrier board. My guess is that the error won’t show up again if using the more recent L4T on a dev kit. If the issue does not occur on the dev kit carrier board, then it is likely your device tree is incorrect (assuming the carrier board layout is valid).
If it turns out to be an issue on the newer L4T release, especially on the dev kit carrier board, then it comes back to either (A) device tree or (B) carrier board. Device trees can make hardware “appear” to fail even when it isn’t failed. Issues like incorrect impedance and trace lengths can break (or make marginal) PCIe and other high speed lines. In that case someone else will need to answer.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.