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

[linuxdev]

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.

[bridge]

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

Nvidia Jetson TX2 is hanging on “Started Update UTMP about System Runlevel Changes.” after flashing new packages with SDKManager 1.1

I ran into this issue on TX2. I’m using ubuntu18.04 laptop, not virtual machine as the host. After flashing the os image and installed the packages in JetPack 4.4 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. Basic information and troubleshooting: It’s a dev kit, carrier board version C02. Using a direct HDMI instead of adapte…

[yyjqr789]

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]

[linuxdev]

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

[yyjqr789]

OK，maybe not the wifi issue.

[jk009d]

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.

[linuxdev]

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).

[zrn-dev]

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