The system is Ubuntu20.04
System version: JetPack5.1.3_L4T35.5.0
Description of the problem: After several power failures and restarts, there will be a phenomenon that can not enter, view the print information seems to be stuck in the UEFI stage, but after the power failure and restart again, it will enter the system normally, verifying that multiple modules have this phenomenon
Hi,
If the device cannot be flashed/booted, please refer to the page to get uart log from the device:
Jetson/General debug - eLinux.org
And get logs of host PC and Jetson device for reference. If you are using custom board, you can compare uart log of developer kit and custom board to get more information.
Also please check FAQs:
Jetson AGX Orin FAQ
If possible, we would suggest follow quick start in developer guide to re-flash the system:
Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation
And see if the issue still persists on a clean-flashed system.
Thanks!
Supplement: After the module brushes the system, external repeated power off and restart verification will appear. It is suspected that this operation will cause system file damage
Requirements: Can you provide an operation description for the normal power on and off of the module? Or is there a better solution for the above operations and some internal configuration of the system can be avoided
What is the reason for power loss? Is this a random power failure? Is this intentional for testing? Is it due to a lack of a method for proper shutdown? Jetsons are a full computer system with a journaling filesystem. You would need to run a normal shutdown command, and if this is perhaps not possible, then use an UPS to give time for proper shutdown. Some information on journals:
https://forums.developer.nvidia.com/t/tuning-linux-on-jetson-nano-for-better-data-reliability-in-power-failure-scenario/252664/5
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
