We are experiencing random reboots on the NVIDIA Jetson Orin Nano Super Development Kit.
We collected samples of voltage regulators, current, temperature, and CPU usage, but we didn’t observe anything unusual. The samples were recorded at a frequency of 5 Hz.
The kernel version we are using is:
I believe we cannot update it since newer versions are not compatible with our CPU model. We are running Ubuntu 22.04 with ROS 2 Humble.
We have tried debugging the cause of the reboots but haven’t been able to obtain any useful information.
From the journalctl -b logs, we can see that when the system restarts, it shows the following error:
Nov 04 12:39:32 Beetle004 systemd-fsck[421]: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
The CPU is properly powered with 15 V/5A through a DC-DC buck converter, and in fact, the system reboots rather than shutting down.
We have observed the same issue on two different CPUs of the same model, operating in different environments.
*** Please note that this reply is generated by LLM automatically ***
Based on the provided information, it appears that the NVIDIA Jetson Orin Nano Super Development Kit is experiencing random reboots. The team has collected samples of voltage regulators, current, temperature, and CPU usage, but nothing unusual was observed. The kernel version is not specified, but it is believed to be an older version that cannot be updated due to compatibility issues with the CPU model.
The system is running Ubuntu 22.04 with ROS 2 Humble, and the team has tried debugging the cause of the reboots but hasn’t been able to obtain any useful information. The logs show an error message indicating that the file system was not properly unmounted and some data may be corrupt.
Given the information, here are a few potential causes and suggestions for further investigation:
Power supply issues: Although the CPU is properly powered with 15V/5A through a DC-DC buck converter, it’s possible that the power supply is not stable or is experiencing voltage drops. It’s recommended to monitor the power supply voltage and current to ensure it’s within the specified range.
Thermal issues: The Jetson Orin Nano series is known to have thermal management features. It’s possible that the system is experiencing thermal throttling or shutdowns due to high temperatures. The team should investigate the thermal management settings and ensure that the system is properly cooled.
File system corruption: The error message indicates that the file system was not properly unmounted and some data may be corrupt. The team should investigate the file system and ensure that it’s properly configured and mounted.
Kernel version: Although the team believes that the kernel version cannot be updated, it’s worth investigating if there are any known issues with the current kernel version that could be causing the reboots.
Hardware issues: Given that the issue is observed on two different CPUs of the same model operating in different environments, it’s possible that there’s a hardware issue with the CPUs or the development kit. The team should investigate the hardware and ensure that it’s properly configured and functioning.
In comparison to other Jetson modules, the Jetson Orin Nano series has similar power management features to the Jetson Orin NX series and Jetson AGX Orin series. However, the Jetson Orin Nano series has a more limited power budget and thermal management capabilities compared to the other two series.
To further debug the issue, the team could try:
Collecting more detailed logs and system information during the reboot process
Running stress tests and monitoring system performance to identify potential bottlenecks
Investigating the file system and ensuring that it’s properly configured and mounted
Monitoring the power supply voltage and current to ensure it’s within the specified range
Investigating the thermal management settings and ensuring that the system is properly cooled
By following these steps, the team should be able to gather more information and potentially identify the root cause of the random reboots.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***