Auto-restart in JetsonAGXOrin 32G Module Brush 35.3.1 We tried to re-flush the system several times, and it automatically restarted during the installation process through the sdk
This problem does not appear in other modules of the same style. I look forward to your reply. Thank you!
Only this module got the problem?
With custom carrier board?
The several restarts during flash is expected.
Please share the full flash log from your host.
and also, the serial console log from your board when you are flashing for further check.
[quote=“kayccc, post:2, topic:271908, full:true”]
Only this module got the problem?
With custom carrier board?
[/quote]After many tests and comparisons, only this module has the problem of restart. We tried to grab the log and painstakingly show it. Thank you
After many tests and comparisons, only this module has the problem of restart. We tried to grab the log and painstakingly show it. Thank you
orin.log (291.3 KB)
[ 238.677357] nvgpu: 17000000.ga10b nvgpu_set_err_notifier_locked:149 [ERR] error notifier set to 25 for ch 505
..
[ 290.497470] ---[ end Kernel panic - not syncing: Oops: Fatal exception ]---
From the log you provided, there’re errors from nvgpu and the kernel panic causing reboot.
Are you using the devkit or custom board?
What’s your Jetpack version in use?
Do you connect any HDMI/DP monitor on your board?
burning version 35.3.1, the HDMI interface on the board was connected when this problem occurred. There was no such problem when using the same model module of the carrier board independently developed by us.
Would you hit the issue when the HDMI is disconnected?
Could you help to verify with the latest R35.4.1?
Do you mean the issue happen only with the devkit?
It seems no HDMI for AGX Orin devkit board…
We replaced the module of the same model and flushed the system of the same version. . We tried 35.4.1 system also appeared，This problem did not occur in other modules
We decided that it was a module problem and whether RMA could be carried out
Looking forward to your reply
If there’s only one module hit the issue and using SDKM to flash the devkit could not help, we would suggest RMA it.