NVIDIA Jetson NX Auto Shutdown Issue When Not Logged In

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
,
1

Hello NVIDIA and Jetson Community!

I’ve been experiencing an issue with my NVIDIA Jetson NX where it automatically shuts down after a certain period of inactivity when not logged in or without any physical login. Initially, it would turn off after perhaps around 1 hour of inactivity. However, these days, it shuts down without any discernible time pattern; it could be in 10 or 15 minutes or more. It’s important to highlight that this issue only occurs when we haven’t logged in or without any physical login. When I log in, the system functions normally without any unexpected shutdowns.

To troubleshoot this issue, I’ve taken several steps:

  1. Checked system logs for error messages or warnings related to the shutdowns.
  2. Ensured that all software configurations, including power management settings, are properly configured.
  3. Monitored hardware components for any signs of failure or instability.
  4. Reviewed recent changes to the system, including any software installations or updates.
  5. Attempted to stop VNC server services, as I suspected they might be related to the issue.
  6. Verified power supply and consumption to rule out any power-related issues.

Despite these efforts, the auto shutdown issue persists. I’m seeking guidance on how to further diagnose and resolve this problem. Are there any additional troubleshooting steps I can take or specific settings I should check to prevent the system from automatically shutting down when not logged in or without any physical login?

I have used a total of 3 Jetson devices - 2 Jetson Xavier NX and 1 Jetson AGX Orin. All Jetsons Xavier NX were purchased from Jetson Xavier NX コンプリートキット J202版（SSD250GB） - Physical Computing Lab. I’ve been using the Jetson Xavier NX for 1.5 years, and they all worked well before. Suddenly, one of my Xavier NX devices began experiencing this issue. This is the first time I’ve encountered this problem.

Furthermore, there’s a related PCIe problem. The error line I encountered is:
[ 5.217923] tegra194-pcie 14160000.pcie: Phy link never came up

When the shutdown occurs, including the LED being shut off, I noticed that unlike other users’ experiences where the LED remains on, all LEDs on my devices are totally off, as if there’s no power. However, this only happens when I don’t log in. If I log in, everything works well.

Any insights or suggestions on resolving this issue would be greatly appreciated. Thank you.

3

Hi share.itbdelabo,

Are they all the devkit or custom board?

What’s your Jetpack version in use?

Is the issue happening after updating the L4T release?

Could you share the full serial console log when you hit the shutdown issue?

4

  1. Only one of them has this problem. It’s a kit from Jetson Xavier NX コンプリートキット J202版（SSD250GB） - Physical Computing Lab.

  2. My Jetpack version in use # R35 (release), REVISION: 2.1, GCID: 32413640, BOARD: t186ref, EABI: aarch64, DATE: Tue Jan 24 23:38:33 UTC 2023. Other Jetsons also use the same Jetpack but they have no problem.

  3. The issue didn’t start occurring after updating the L4T release. It was working fine previously, and the problem emerged suddenly without any known changes to the system.

  4. This is the full serial console log.
    serial_console_log.txt (65.1 KB)

5

Okay, it seems you are using the custom carrier board for Xavier NX.

Do you mean that you have 2 Xavier NX board? One has the shutdown issue but another not?

I don’t see the shutdown related messages in your log, could you point out where it gets shutdown?

6

Yes, I have 2 Xavier NX boards. Only one has the shutdown issue. But it just happened this month (after using it for around 1.5 years)

It only gets shutdown when I don’t physically login. Can you tell me how to get the log when I haven’t login? Because I can’t get the log before login.

7

What we need is the full serial console log.
For the devkit, it can be captured through USB to TTL cable like Jetson Nano & NX Style - Serial Debug Console - JetsonHacks.
For the custom carrier board, please ask the guidance from your vendor.

8

Alright. Thank you for your guidance. I’ll do as you instructed and let you know the result by next week.

9

Hi, sorry for the late reply. Here I attach the log file.
minicom-jetson_1.txt (64.3 KB)

When the Jetson turns itself off, starting from the line below, this is the data that appears after.

[ 1229.833619] Trying to unregister non-registered hwtime source

10

From the log you shared, it seems entering into suspend(SC7) rather than shutdown.

����spe entering sc7

You can also try to run sudo systemctl suspend to enter this state.

11

What should I do to prevent this suspend mode? It keeps happening and I need to restart the Jetson every time it happens.

It has never happened before. What is the trigger?

12

Maybe you can just wake it up through pressing the button or other wakeup source.

You can find if there’s any settings in your system causing it to enter this state.

You can try if the following command help for your case.

$ sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target
13

Thank you very much. My Jetson doesn’t enter the suspend mode anymore.

14

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.