Jetson Xavier NX 5.1.2: Failed to Start nv-l4t-usb-device-mode.service and Stuck in Booting

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

Hello,

I am experiencing a boot issue with my Jetson Xavier NX running version 5.1.2. After a certain number of reboots or power-offs, the device gets stuck during the boot process.

Here is an image showing the error and the point at which the boot process gets stuck:

test
test1230×2184 213 KB

Below is the detailed error message I receive:
sudo systemctl status nv-l4t-usb-device-mode.service
● nv-l4t-usb-device-mode.service - Configure USB flashing port for device mode
Loaded: loaded (/etc/systemd/system/nv-l4t-usb-device-mode.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2024-06-11 15:39:14 IST; 46min ago
Process: 413 ExecStart=/opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode-start.sh (code=exited, status=1/FAILURE)
Process: 2376 ExecStopPost=/opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode-stop.sh (code=exited, status=0/SUCCESS)
Main PID: 413 (code=exited, status=1/FAILURE)

Jun 11 15:39:09 phoenix-desktop nv-l4t-usb-device-mode-stop.sh[2401]: rmdir: failed to remove ‘l4t/functions/mass_storage.0/’: No such file or directory
Jun 11 15:39:09 phoenix-desktop nv-l4t-usb-device-mode-stop.sh[2404]: rmdir: failed to remove ‘l4t/functions/acm.GS0/’: No such file or directory
Jun 11 15:39:09 phoenix-desktop nv-l4t-usb-device-mode-stop.sh[2406]: rmdir: failed to remove ‘l4t/functions/rndis.usb0/’: No such file or directory
Jun 11 15:39:09 phoenix-desktop nv-l4t-usb-device-mode-stop.sh[2413]: rmdir: failed to remove ‘l4t/configs/c.1/’: No such file or directory
Jun 11 15:39:09 phoenix-desktop nv-l4t-usb-device-mode-stop.sh[2417]: rmdir: failed to remove ‘l4t/strings/0x409’: No such file or directory
Jun 11 15:39:09 phoenix-desktop nv-l4t-usb-device-mode-stop.sh[2418]: rmdir: failed to remove ‘l4t’: No such file or directory
Jun 11 15:39:09 phoenix-desktop nv-l4t-usb-device-mode-stop.sh[2422]: l4tbr0: ERROR while getting interface flags: No such device
Jun 11 15:39:09 phoenix-desktop nv-l4t-usb-device-mode-stop.sh[2431]: bridge l4tbr0 doesn’t exist; can’t delete it
Jun 11 15:39:14 phoenix-desktop systemd[1]: nv-l4t-usb-device-mode.service: Failed with result ‘exit-code’.
Jun 11 15:39:14 phoenix-desktop systemd[1]: Failed to start Configure USB flashing port for device mode

3

Hi,

So what’s the situation now?
The GUI stucks but you are still able to log in via serial console?
Is it a DevKit or a custom board?
Put both the booting log and the systemctl status as text files here.

4

yes GUI is stuck while i am able to log in via ethernet.

log_file.txt (1.9 KB)

5

Share the

  1. df -h
  2. /var/log/Xorg.0.log
  3. dmesg.
6

i have share the file below.
dmesg.txt (73.3 KB)
log_file1.txt (8.3 KB)

7

[ 17.852] (II) NVIDIA: The X server supports PRIME Render Offload.
[ 17.852] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics device!
[ 17.852] (EE) NVIDIA(0): Failing initialization of X screen

This is the error why your monitor GUI cannot show up.

Are you sure you are booting from nvme? Your kernel log showed something weird.

[ 6.577067] Found dev node: /dev/mmcblk0p1
[ 6.612286] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
[ 6.621633] Rootfs mounted over mmcblk0p1

Rootfs is mounted over mmcblk0p1. Probably your internal emmc.

8

Yes, rootfs is mounted over mmcblk0p1.

Could you provide further guidance on the possible causes and debugging steps for these issues? Specifically:

  1. Why might the NVIDIA graphics device fail to initialize?
9

Are you sure this issue was happened with few boot attempt?

Also, your df -h result indicates your system is mounted on nvme… mmcblkp0p1 does not show up…

10

yes, this issues was happen with few boot attempt.

sorry, rootfs is mounted in nvme0n1p1 which is my external ssd.

nvme0n1      259:0    0   1.8T  0 disk 
├─nvme0n1p1  259:1    0   1.8T  0 part /
└─nvme0n1p2  259:2    0     4G  0 part [SWAP]
11

Then why did your dmesg said rootfs is on emmc? This behavior may lead to problem.

12

is there is any suggestion to resolve this issues.

13

Can you first stop this service?

setssdroot.service

You can directly flash rootfs into NVMe, and there is really no need of using such tools.

14

yes, i can stop this service. but i need the external storage for the application.

15

SDK Manager supports flashing to NVMe.
Please do it this way.

Maybe some file permissions were corrupted when you copied the rootfs to NVMe, hence the error.

16

okay thank you for the suggestion.