DGX Spark shuts down within minutes after OS reinstall (kernel panic during first boot update)

Accelerated Computing DGX Spark / GB10 User Forum DGX Spark / GB10
1

Hello everyone,

I have purchased a DGX Spark and tried to start it for the first time. However, during the initial boot, after connecting to Wi-Fi and applying updates, the system encountered a kernel panic error.

Following the instructions on the page System Recovery — DGX Spark User Guide, I reinstalled the operating system. After the reinstallation, I was able to boot into the desktop successfully.

However, a new issue has appeared: the system now shuts down automatically within a few minutes after reboot, even when idle.

I have already checked system logs using the command below, but did not find anything abnormal:

journalctl -1 -b -e

journalctl.txt (5.0 KB)

nvidia-bug-report.sh

bug-report.txt (2.1 KB)

Could anyone help me diagnose this issue?

2

Thanks for the detailed report and for attaching the logs.

From what you shared, the strongest clue is that this may not be a new kernel panic after recovery, but instead an input or power-related shutdown.

In the journal, a Logitech USB receiver is detected, and immediately after that the system logs a power-key event. Could you please try the following first?

  • Power the system off and disconnect all non-essential USB devices, docks, hubs, and adapters, especially the Logitech receiver

  • Boot with only the monitor connected, and if needed, use a simple wired keyboard/mouse

  • Confirm that you are using the original DGX Spark power adapter that shipped with the unit, connected directly to wall power

  • Let the system sit idle for a few minutes and check whether it still shuts down

If it still powers off after that, please collect logs from the failing boot again and share them:

journalctl -b -1 -e
journalctl -b -1 | tail -200

Also, the nvidia-bug-report attachment you posted does not look like the full report contents, so if possible please attach the actual nvidia-bug-report.log.gz file from the system.

If the issue reproduces even with:

  • the supplied power adapter

  • no external USB peripherals except basic wired input devices

  • a clean recovered image

then the next recommended step is to run DGX Spark Field Diagnostics.

The official process is:

  • Disable Secure Boot first:
sudo mokutil --sb-state
sudo systemctl reboot --firmware-setup

Then in UEFI, go to Security → Secure Boot → Disable Secure Boot, save changes, and reboot.

  • Install the diagnostic package:
sudo mkdir -p /usr/share/keyrings
curl -fsSL https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2404/sbsa/cuda-archive-keyring.gpg | sudo tee /usr/share/keyrings/cuda-archive-keyring.gpg > /dev/null
echo "deb [signed-by=/usr/share/keyrings/cuda-archive-keyring.gpg] https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2404/sbsa /" | sudo tee /etc/apt/sources.list.d/cuda-sbsa-ubuntu2404.list
sudo apt-get update
sudo apt-get install dgx-spark-fieldiag
  • Run the diagnostic:
sudo init 3

Log in on the TTY console, then run:

cd /opt/nvidia/dgx-spark-fieldiag
sudo ./partnerdiag --field

The test takes about 30 minutes and should end with a PASS or FAIL banner.

After it completes, please share:

  • whether the result is PASS or FAIL

  • any logs produced by the diagnostic

  • whether the shutdown behavior changes when all USB peripherals are removed

After the test, re-enable Secure Boot by rebooting back into UEFI and setting Security → Secure Boot → Enable Secure Boot.

At that point we can better determine whether this is a peripheral-triggered shutdown, a power issue, or something that needs hardware support escalation.