Nvidia Jetson Xavier is hanging on "Started Update UTMP about System Runlevel Changes."

has anyone figured this one out? I’m facing the same issue with screen going on and off every second and hanging on [OK] Started Update UTMP about System Runlevel Changes.
The console on host says lost connection.
My setup is exactly the same as oabdulhafez’s

Hey tom,

Try to change the PC that you are using for flashing Xavier board.

There’s few instructions that I find missing from the official docs which I found in different parts of the devtalk forum and elsewhere on the internet that led me to a solution. So for anyone with similar problems, and for those writing the docs, here’s few points that helped me succeed with properly setting up Xavier.
I hope someone will find the below helpful.

  1. Run the jetpack .run file from a Linux partition (not external HDD, nor a partition that’s shared with Windows OS) as only that partition holds relevant permission information which is required after files are copied to Xavier. Otherwise you copy files without permissions and you won’t be able to do anything as root later on.
  2. Make sure that you’ve got more than enough space for Jetpack on the host machine to extract/build all it needs. In my case I wasn’t getting no error messages but things just froze during setup after device was (succesffully?) flashed
  3. Try different USB port if there’s any problems during/after flashing the device

From my understanding, you may need to flash new kernel, rootfs and bootloader if it has been changed. I have also faced the same problem that Jetson Xavier get hang “Started Update UTMP about System Runlevel Changes.”, even I used JETPACK 4.2 from Nvidia without modification. I finally found that I flashed to target only the kernel, not the rootfs.

I would recommend to use the below command for flashing, if you need to flash rootfs as well.

sudo ./flash.sh jetson-xavier mmcblk0p1

Hope this is helpful!

1 Like

I am facing the same issue after upgrading to JETPACK 4.2 and L4T 32.1. Has anyone managed to identify the root cause of this issue?

Thanks,
Peter

In my case,

I connect the Xavier to the Internet in order to make it available to log in with ssh.
However, as soon as the device was flashed and rebooted, it was hacked immediately.

The problem never happened again after I change the password of the both default accounts “ubuntu” and “nvidia” before connecting to the Internet.

Allen

Thanks allenchen0958,

By changing the password the boot sequence advanced a few more steps and now it hangs on

“Reached target Graphical Interface”

Peter

1 Like

I am not surprised at all. Many people connect through a router which blocks uninitiated traffic, but if for example you share a router in a dormitory, then everyone sees everyone else. Port scans are continuous, and you might see multiple brute force attempts using default logins every second when not protected through a router or firewall.

I have the same problem with the screen on and off. It’s already flashed and works when having internet connection. I got this error when I start the Xavier without an internet connection, is there any solution?

Is it correct that only the GUI login does this? For example, something like CTRL-ALT-F3 might give you a text based console. Also, the serial console should always work.

For serial console you would use the provided micro-B USB cable on the running system and the host would see some serial devices as you plug in the cable (monitor “dmesg --follow” on the host PC as you plug in the cable…if the first device found is “/dev/ttyUSB0”, then this is the serial console device). Serial console settings would be 115200 8N1 with whatever serial console program you use. I like gtkterm (“sudo apt-get install gtkterm” on the PC), and if the serial device is “/dev/ttyUSB0”, then:

gtkterm -b 8 -t 1 -s 115200 -p /dev/ttyUSB0

(which conveniently can log the boot process and you can post the log here…hover your mouse over the quote icon in the upper right of one of your existing posts, and then a paper clip icon will show up…use that to attach a log file)

Incidentally, if you can log in, then check that everything in this command shows “ok”:

sha1sum -c /etc/nv_tegra_release

If one of the graphics libraries shows incorrectly, then this can be why graphics failed with the “flashing” effect (as the GUI starts up it would crash if drivers are incorrect, and then the system would attempt to restart the crashed GUI in an infinite loop). If there is another problem, then the serial console log will probably offer some good hints.

1 Like

Thank you @linuxdev for the reply, after login through serial console we found the better error message which saysNo space left on Device. After cleaning the disk we can log in again, the cmds you have is very handy, thanks!!

I ran into the same symptom on TX2. I’m using ubuntu18.04 laptop, not virtual machine as the host.

After flashing the os image and installed the packages with SDKmanager 1.1, I rebooted the TX2, and it got stuck at “[OK] Started update UTMP about System Runlevel Changes.” This one has [OK] in front, it itself might be successful, something after this may get stuck.

I used “dmesg --follow” to check what was going on when unplug/plug micro-b on TX2, got below messages.
$ dmesg --follow

unplug micro-b on tx2:

[36469.381516] usb 1-4: USB disconnect, device number 29
[36469.381843] rndis_host 1-4:1.0 enp0s20f0u4: unregister ‘rndis_host’ usb-0000:00:14.0-4, RNDIS device
[36469.467427] cdc_ncm 1-4:1.5 enp0s20f0u4i5: unregister ‘cdc_ncm’ usb-0000:00:14.0-4, CDC NCM

plug micro-b on tx2:

[36486.745497] usb 1-4: new high-speed USB device number 30 using xhci_hcd
[36486.894630] usb 1-4: New USB device found, idVendor=0955, idProduct=7020, bcdDevice= 0.02
[36486.894637] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[36486.894642] usb 1-4: Product: Linux for Tegra
[36486.894645] usb 1-4: Manufacturer: NVIDIA
[36486.894649] usb 1-4: SerialNumber: 0421219007430
[36486.901465] rndis_host 1-4:1.0 usb0: register ‘rndis_host’ at usb-0000:00:14.0-4, RNDIS device, b2:51:1d:47:94:3c
[36486.902052] cdc_acm 1-4:1.2: ttyACM0: USB ACM device
[36486.902453] usb-storage 1-4:1.4: USB Mass Storage device detected
[36486.902575] scsi host2: usb-storage 1-4:1.4
[36486.926716] cdc_ncm 1-4:1.5: MAC-Address: f2:00:6a:c4:c8:22
[36486.926917] cdc_ncm 1-4:1.5 usb1: register ‘cdc_ncm’ at usb-0000:00:14.0-4, CDC NCM, f2:00:6a:c4:c8:22
[36486.961811] rndis_host 1-4:1.0 enp0s20f0u4: renamed from usb0
[36486.979671] cdc_ncm 1-4:1.5 enp0s20f0u4i5: renamed from usb1
[36487.068548] cdc_ncm 1-4:1.5 enp0s20f0u4i5: 425 mbit/s downlink 425 mbit/s uplink
[36487.100391] cdc_ncm 1-4:1.5 enp0s20f0u4i5: 425 mbit/s downlink 425 mbit/s uplink
[36487.132506] cdc_ncm 1-4:1.5 enp0s20f0u4i5: network connection: connected
[36487.132534] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s20f0u4i5: link becomes ready
[36487.930287] scsi 2:0:0:0: Direct-Access Linux File-Stor Gadget 0409 PQ: 0 ANSI: 2
[36487.931120] sd 2:0:0:0: Attached scsi generic sg1 type 0
[36487.931384] sd 2:0:0:0: Power-on or device reset occurred
[36487.931780] sd 2:0:0:0: [sdb] 32768 512-byte logical blocks: (16.8 MB/16.0 MiB)
[36487.931985] sd 2:0:0:0: [sdb] Write Protect is on
[36487.931991] sd 2:0:0:0: [sdb] Mode Sense: 0f 00 80 00
[36487.932191] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
[36487.934567] sdb:
[36487.936106] sd 2:0:0:0: [sdb] Attached SCSI removable disk

I didn’t see any /dev/ttyUSB* devices, don’t know which represents the serial console.

Though I cannot start up TX2 with a shell or GUI, I could ssh into it from the host, by using the default ip 192.168.55.1 via the USB cable. I checked the space on TX2, seems not due to out-of-space.

tx2@tx2-desktop:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p1 28G 11G 16G 42% /
none 3.8G 0 3.8G 0% /dev
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 3.9G 68M 3.8G 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs 786M 0 786M 0% /run/user/1000
tmpfs 786M 4.0K 786M 1% /run/user/120

Also tried this command sha1sum, got below result.

tx2@tx2-desktop:~$ sha1sum -c /etc/nv_tegra_release
sha1sum: /etc/nv_tegra_release: no properly formatted SHA1 checksum lines found
tx2@tx2-desktop:~$ cat /etc/nv_tegra_release

R32 (release), REVISION: 4.2, GCID: 20074772, BOARD: t186ref, EABI: aarch64, DATE: Thu Apr 9 01:26:40 UTC 2020

What else could cause this issue?

I attached the log, it’s zip file, due to site restriction, I appended “.log” to the file, remove “.log” and use unzip to decompress, you will get a bunch of log files.
SDKM_logs_JetPack_4.4_DP_Linux_for_Jetson_TX2_2020-06-08_22-29-38.zip.log (288.4 KB)

FYI, this is in the Xavier forum, and there are significant differences between Xavier and TX2. I would advise reposting this in TX2 forum.

Notes for when you post in the TX2 forum:

  • sha1sum -c /etc/nv_tegra_release works for older releases, but not newer releases.
  • In newer releases /etc/nv_tegra_release does not exist, and you would find the release version via:
    dpkg -l | grep 'nvidia-l4t-core'
  • A full serial console boot log from the TX2 would help.
  • Knowing if your monitor is purely HDMI, versus having an adapter, would help.
  • Knowing the output of this would help:
sudo -s
egrep -H '.*' `find /sys -name edid`
exit

FYI, you have enough disk space, so that can be ruled out as an issue.

You can also include the flash logs, but it is likely the flash itself went well and the actual GUI configuration on the Jetson is at issue.

The serial console boot logs will be more likely to help, but serial console setup is different on a TX2 versus Xavier. To know more about this issue, run “dmesg --follow” on the host PC, and post what you see in the host PC’s logs upon insert of the micro-B USB cable.

Also note if this is the dev kit or a third party carrier board.

Thank you very much, I re-posted it to TX2 forum.

I also encoutered this problem in Xavier NX,Jetpack4.6. How to solve it?
Thanks in advance!!
head -n 1 /etc/nv_tegra_release

R32 (release), REVISION: 6.1, GCID: 27863751, BOARD: t186ref, EABI: aarch64, DATE: Mon Jul 26 19:36:31 UTC 2021

[四 7月 22 02:52:06 2021] WARNING: CPU: 0 PID: 6130 at /dvs/git/dirty/git-master_linux/kernel/kernel-4.9/net/wireless/nl80211.c:14153 cfg80211_ch_switch_notify+0x150/0x170 [cfg80211]
[四 7月 22 02:52:06 2021] Modules linked in: fuse xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xt_addrtype iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack br_netfilter zram overlay bnep rtk_btusb btusb btrtl btbcm btintel rtl8822ce userspace_alert cfg80211 binfmt_misc nvgpu ip_tables x_tables

[四 7月 22 02:52:06 2021] CPU: 0 PID: 6130 Comm: RTW_CMD_THREAD Not tainted 4.9.253-tegra #1
[四 7月 22 02:52:06 2021] Hardware name: NVIDIA Jetson Xavier NX Developer Kit (DT)
[四 7月 22 02:52:06 2021] task: ffffffc1e2433800 task.stack: ffffffc1c7590000
[四 7月 22 02:52:06 2021] PC is at cfg80211_ch_switch_notify+0x150/0x170 [cfg80211]
[四 7月 22 02:52:06 2021] LR is at rtw_cfg80211_ch_switch_notify+0x94/0x98 [rtl8822ce]
[四 7月 22 02:52:06 2021] pc : [] lr : [] pstate: 60c00045
[四 7月 22 02:52:06 2021] sp : ffffffc1c7593c20
[四 7月 22 02:52:06 2021] x29: ffffffc1c7593c20 x28: ffffff8001281760
[四 7月 22 02:52:06 2021] x27: ffffff800d2c21bc x26: ffffff8001446578
[四 7月 22 02:52:06 2021] x25: ffffff80014ca13c x24: ffffffc1dac09000
[四 7月 22 02:52:06 2021] x23: ffffffc1d6c91000 x22: ffffffc1d6ca4000
[四 7月 22 02:52:06 2021] x21: 0000000000000002 x20: ffffffc1c7593ca8
[四 7月 22 02:52:06 2021] x19: ffffffc1dc8df400 x18: 0000000000000030
[四 7月 22 02:52:06 2021] x17: 0000007f7ad11258 x16: 000000000046cbfb
[四 7月 22 02:52:06 2021] x15: ffffffffffffffff x14: 0000000000000008
[四 7月 22 02:52:06 2021] x13: 7f1201c7fffa009b x12: 0105c00363fffa03
[四 7月 22 02:52:06 2021] x11: 0000000000000004 x10: 0000000000000002
[四 7月 22 02:52:06 2021] x9 : 0000000000000004 x8 : ffffffc1c7593d3a
[四 7月 22 02:52:06 2021] x7 : 0000000000000000 x6 : 0000000000000001
[四 7月 22 02:52:06 2021] x5 : 0000000000000040 x4 : 00000000000016ad
[四 7月 22 02:52:06 2021] x3 : 0000168f00000003 x2 : ffffffc1d6ca5e08
[四 7月 22 02:52:06 2021] x1 : 0000168f00000003 x0 : 0000000000000000

[四 7月 22 02:52:06 2021] —[ end trace 3e70be274b58110b ]—
[四 7月 22 02:52:06 2021] Call trace:
[四 7月 22 02:52:06 2021] [] cfg80211_ch_switch_notify+0x150/0x170 [cfg80211]
[四 7月 22 02:52:06 2021] [] rtw_cfg80211_ch_switch_notify+0x94/0x98 [rtl8822ce]
[四 7月 22 02:52:06 2021] [] rtw_chk_start_clnt_join+0x43c/0x4d8 [rtl8822ce]
[四 7月 22 02:52:06 2021] [] join_cmd_hdl+0x238/0x330 [rtl8822ce]

You will need to start a new thread on this. Looks like the WiFi is completely different as an issue versus the original thread.

OK,maybe not the wifi issue.

I got this:

" no properly formatted SHA1 checksum lines found".

I also tried flashing again AGX with new jetpack and OS it says bad state with manual recovery and it will just get stuck on connecting button on automatic update.

Automatic update sounds like what happens when it is fully booted, and a successful flash will automatically reboot in order to get to first boot account setup. Everyone should probably start a new thread since so much is different compared to the original thread (which was from about 2 years ago, and the previous replies were about a year old). When posting do include a full serial log (if flashing, then the log of flash, and if booting, the serial console log; in both cases, even flashing, one can also save a serial console log of the flash process).

In my case, It stopped at " [OK] Finished Update UTMP about system Runlevel Changed"

I just pressed Power Off button once again, agx xavier got turned off.
Again turned on and everything worked well