Nvidia Jetson Xavier NX is hanging on “Started Update UTMP about System Runlevel Changes.” jetpack4.6,SD card

I encoutered this problem in Xavier NX,Jetpack4.6.Nvidia Jetson Xavier NX is hanging on “Started Update UTMP about System Runlevel Changes.” 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

dmesg info as follows:
[四 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]

Remove your wifi module on device and see if it can boot into kernel now.

I just test this,remove wifi module,and display still hang there,also test reboot the device, hange the UTMP warn… But I can use a serial cable to log into the device,and see this:

[ 19.321991] extcon-disp-state external-connection:disp-state: cable 47 state 0
[ 19.322024] Extcon AUX1(HDMI) disable
[ 19.344445] tegra_nvdisp_handle_pd_disable: Powergated Head1 pd
[ 19.344994] tegra_nvdisp_handle_pd_disable: Powergated Head0 pd
[ 19.346259] tegradc 15210000.nvdisplay: blank - powerdown
[ 19.354595] tegradc 15200000.nvdisplay: blank - powerdown
[ 19.354625] tegradc 15200000.nvdisplay: unblank
[ 19.355466] tegra_nvdisp_handle_pd_enable: Unpowergated Head0 pd
[ 19.355583] tegra_nvdisp_handle_pd_enable: Unpowergated Head1 pd
[ 19.360723] Parent Clock set for DC plld2
[ 19.366206] tegradc 15200000.nvdisplay: hdmi: tmds rate:148500K prod-setting:prod_c_hdmi_111m_223m
[ 19.367612] tegradc 15200000.nvdisplay: hdmi: get YCC quant from EDID.
[ 19.406300] extcon-disp-state external-connection:disp-state: cable 47 state 1
[ 19.406304] Extcon AUX1(HDMI) enable
[ 19.417812] tegradc 15200000.nvdisplay: sync windows ret = 248
[ 19.888622] tegradc 15200000.nvdisplay: unblank
[ 19.888659] tegradc 15210000.nvdisplay: blank - powerdown
[ 20.909310] tegradc 15200000.nvdisplay: blank - powerdown
[ 20.967945] extcon-disp-state external-connection:disp-state: cable 47 state 0
[ 20.967950] Extcon AUX1(HDMI) disable
[ 20.992728] tegra_nvdisp_handle_pd_disable: Powergated Head1 pd
[ 20.993964] tegra_nvdisp_handle_pd_disable: Powergated Head0 pd
[ 20.994178] tegradc 15210000.nvdisplay: blank - powerdown
[ 21.003538] tegradc 15200000.nvdisplay: blank - powerdown
[ 21.003570] tegradc 15200000.nvdisplay: unblank
[ 21.004372] tegra_nvdisp_handle_pd_enable: Unpowergated Head0 pd
[ 21.004486] tegra_nvdisp_handle_pd_enable: Unpowergated Head1 pd
[ 21.009389] Parent Clock set for DC plld2
[ 21.015385] tegradc 15200000.nvdisplay: hdmi: tmds rate:148500K prod-setting:prod_c_hdmi_111m_223m
[ 21.016775] tegradc 15200000.nvdisplay: hdmi: get YCC quant from EDID.
[ 21.052144] extcon-disp-state external-connection:disp-state: cable 47 state 1
[ 21.052148] Extcon AUX1(HDMI) enable
[ 21.066979] tegradc 15200000.nvdisplay: sync windows ret = 246
[ 21.539915] tegradc 15200000.nvdisplay: unblank
[ 21.539930] tegradc 15210000.nvdisplay: blank - powerdown
[ 22.545384] tegradc 15200000.nvdisplay: blank - powerdown
[ 22.600418] extcon-disp-state external-connection:disp-state: cable 47 state 0
[ 22.600423] Extcon AUX1(HDMI) disable
[ 22.625672] tegra_nvdisp_handle_pd_disable: Powergated Head1 pd
[ 22.626750] tegra_nvdisp_handle_pd_disable: Powergated Head0 pd
[ 22.626937] tegradc 15210000.nvdisplay: blank - powerdown
[ 22.635911] tegradc 15200000.nvdisplay: blank - powerdown
[ 22.635942] tegradc 15200000.nvdisplay: unblank
[ 22.636859] tegra_nvdisp_handle_pd_enable: Unpowergated Head0 pd
[ 22.637037] tegra_nvdisp_handle_pd_enable: Unpowergated Head1 pd
[ 22.641539] Parent Clock set for DC plld2
[ 22.646266] tegradc 15200000.nvdisplay: hdmi: tmds rate:148500K prod-setting:prod_c_hdmi_111m_223m
[ 22.647710] tegradc 15200000.nvdisplay: hdmi: get YCC quant from EDID.
[ 22.684374] extcon-disp-state external-connection:disp-state: cable 47 state 1
[ 22.684378] Extcon AUX1(HDMI) enable
[ 22.697902] tegradc 15200000.nvdisplay: sync windows ret = 247
[ 23.164037] tegradc 15200000.nvdisplay: unblank
[ 23.164051] tegradc 15210000.nvdisplay: blank - powerdown
[ 24.177389] tegradc 15200000.nvdisplay: blank - powerdown
[ 24.231329] extcon-disp-state external-connection:disp-state: cable 47 state 0
[ 24.231334] Extcon AUX1(HDMI) disable
[ 24.255600] tegra_nvdisp_handle_pd_disable: Powergated Head1 pd
[ 24.256173] tegra_nvdisp_handle_pd_disable: Powergated Head0 pd
[ 24.257475] tegradc 15210000.nvdisplay: blank - powerdown
[ 24.266585] tegradc 15200000.nvdisplay: blank - powerdown
[ 24.266642] tegradc 15200000.nvdisplay: unblank
[ 24.267418] tegra_nvdisp_handle_pd_enable: Unpowergated Head0 pd
[ 24.267525] tegra_nvdisp_handle_pd_enable: Unpowergated Head1 pd
[ 24.273024] Parent Clock set for DC plld2
[ 24.278033] tegradc 15200000.nvdisplay: hdmi: tmds rate:148500K prod-setting:prod_c_hdmi_111m_223m
[ 24.279503] tegradc 15200000.nvdisplay: hdmi: get YCC quant from EDID.
[ 24.317218] extcon-disp-state external-connection:disp-state: cable 47 state 1
[ 24.317222] Extcon AUX1(HDMI) enable
[ 24.329727] tegradc 15200000.nvdisplay: sync windows ret = 247
[ 34.142295] vdd-1v8-sd: disabling
[ 34.142303] vdd-1v8-cvb: disabling
[ 34.142308] vdd-epb-1v0: disabling
[ 34.142313] avdd-cam-2v8: disabling
[ 34.142317] vdd-fan: disabling
[ 34.142322] vdd_sys_en: disabling
[ 60.501498] nvgpu: 17000000.gv11b railgate_enable_store:297 [INFO] railgate is disabled.
kctiir@kctiir-desktop:~$ uname -a
Linux kctiir-desktop 4.9.253-tegra #1 SMP PREEMPT Mon Jul 26 12:19:28 PDT 2021 aarch64 aarch64 aarch64 GNU/Linux
kctiir@kctiir-desktop:~$

hello yyjqr789,

so you’re able to boot into kernel and issue the commands, please clarify what’s the following up issue.

the problem is : I cannot enter the desktop , or in other way, the device not show the desktop UI.But through the serial port ,I can log into the device.

1 Like

please reboot and share the /var/log/Xorg.0.log.

I also meet this problom, I just compile kernel and replace the Image.

I have the same problem.

Yeah I know, so where is your log??

This is another new Sd card with JetPack4.6. I can log into the desktop.But the dmesg information still warn wifi issue. The problem sd card log ,post there(At weekend ,the device is not in my hand.And upload the log takes me sometime,can’t upload the log successfully).

Xorg.0.log (18.0 KB)
Xorg.0.log.old (18.0 KB)
log for NX can’t log into the desktop! Thanks!

It looks like both log show the xorg is closed by some reason.

21.948] () Option “config_info” “udev:/sys/devices/3610000.xhci/usb1/1-2/1-2.4/1-2.4:1.1/0003:046D:C534.0003/input/input8/event7”
[ 21.948] (II) XINPUT: Adding extended input device “Logitech USB Receiver” (type: KEYBOARD, id 10)
[ 21.948] (
) Option “xkb_model” “pc105”
[ 21.948] () Option “xkb_layout” “us”
[ 22.584] (
) Option “fd” “34”
[ 22.584] (II) event5 - ILITEK ILITEK-TP: device removed
[ 22.584] () Option “fd” “37”
[ 22.584] (II) event6 - Logitech USB Receiver: device removed
[ 22.584] (
) Option “fd” “38”
[ 22.584] () Option “fd” “39”
[ 22.584] (II) event4 - gpio-keys: device removed
[ 22.584] (
) Option “fd” “38”
[ 22.585] (II) event7 - Logitech USB Receiver: device removed
[ 22.587] (II) UnloadModule: “libinput”
[ 22.587] (II) systemd-logind: not releasing fd for 13:71, still in use
[ 22.587] (II) UnloadModule: “libinput”
[ 22.587] (II) systemd-logind: releasing fd for 13:68
[ 22.616] (II) UnloadModule: “libinput”
[ 22.616] (II) systemd-logind: releasing fd for 13:71
[ 22.640] (II) UnloadModule: “libinput”
[ 22.640] (II) systemd-logind: releasing fd for 13:70
[ 22.672] (II) UnloadModule: “libinput”
[ 22.672] (II) systemd-logind: releasing fd for 13:69
[ 22.823] (II) NVIDIA(GPU-0): Deleting GPU-0
[ 22.960] (II) Server terminated successfully (0). Closing log file.

For such case, please also attach the syslog. And since syslog is quite long , please tell me the timestamp when you see the error…

Please prevent to send me a whole week syslog… it will be hard to check.

In the syslog, I see some gnome error. This problem first happened maybe between Aug10.As before ,the dmesg date is 7.22,that is system time wrong (not updated).
Aug 10 06:14:19 kctiir-desktop gnome-software[10751]: g_strsplit: assertion ‘str
ing != NULL’ failed
Aug 10 06:14:19 kctiir-desktop gnome-software[10751]: g_strv_length: assertion ’
str_array != NULL’ failed
Aug 10 06:14:19 kctiir-desktop gnome-software[10751]: json_object_has_member: as
sertion ‘member_name != NULL’ failed
Aug 10 06:14:19 kctiir-desktop gnome-software[10751]: g_strsplit: assertion ‘str
ing != NULL’ failed
Aug 10 06:14:19 kctiir-desktop gnome-software[10751]: g_strv_length: assertion ’
str_array != NULL’ failed

syslog.1 (7.0 MB)
-rw-r----- 1 kctiir kctiir 0 8月 11 00:09 syslog
-rw-r----- 1 kctiir kctiir 7.0M 8月 11 00:09 syslog.1
-rw-r----- 1 kctiir kctiir 144K 8月 10 00:06 syslog.2.gz
-rw-r----- 1 kctiir kctiir 21K 8月 9 00:10 syslog.3.gz
-rw-r----- 1 kctiir kctiir 19K 8月 8 00:06 syslog.4.gz

I don’t see any log that directly indicates the gdm3 is crashing.

For example, you can search with keyword “gdm-x-session” in your syslog.

And the last few search result indicate the gdm3 is going to run

Aug 10 14:44:03 kctiir-desktop /usr/lib/gdm3/gdm-x-session[8551]: /etc/gdm3/Xsession: Beginning session setup…
ug 10 14:44:05 kctiir-desktop /usr/lib/gdm3/gdm-x-session[8551]: localuser:kctiir being added to access control list
Aug 10 14:44:05 kctiir-desktop /usr/lib/gdm3/gdm-x-session[8551]: dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
Aug 10 14:44:05 kctiir-desktop /usr/lib/gdm3/gdm-x-session[8551]: dbus-update-activation-environment: setting DISPLAY=:1
Aug 10 14:44:05 kctiir-desktop /usr/lib/gdm3/gdm-x-session[8551]: dbus-update-activation-environment: setting XAUTHORITY=/run/user/1000/gdm/Xauthority
Aug 10 14:44:05 kctiir-desktop systemd[1]: Started resolvconf-pull-resolved.service.
Aug 10 14:44:05 kctiir-desktop /usr/lib/gdm3/gdm-x-session[8551]: localuser:kctiir being added to access control list

And then we have a kernel panic from the wifi driver.

Aug 10 14:44:06 kctiir-desktop kernel: [ 52.882650] [] cfg80211_ch_switch_notify+0x150/0x170 [cfg80211]
Aug 10 14:44:06 kctiir-desktop kernel: [ 52.883284] [] rtw_cfg80211_ch_switch_notify+0x94/0x98 [rtl8822ce]
Aug 10 14:44:06 kctiir-desktop kernel: [ 52.883884] [] rtw_chk_start_clnt_join+0x43c/0x4d8 [rtl8822ce]
Aug 10 14:44:06 kctiir-desktop kernel: [ 52.884489] [] join_cmd_hdl+0x238/0x330 [rtl8822ce]
Aug 10 14:44:06 kctiir-desktop kernel: [ 52.885072] [] rtw_cmd_thread+0x308/0x608 [rtl8822ce]
Aug 10 14:44:06 kctiir-desktop kernel: [ 52.885087] [] kthread+0xec/0xf0
Aug 10 14:44:06 kctiir-desktop kernel: [ 52.885096] [] ret_from_fork+0x10/0x30
Aug 10 14:44:06 kctiir-desktop wpa_supplicant[4932]: wlan0: CTRL-EVENT-CHANNEL-SWITCH freq=5805 ht_enabled=1 ch_offset=-1 ch_width=80 MHz cf1=5775 cf2=0
Aug 10 14:44:06 kctiir-desktop NetworkManager[5070]: [1628577846.9566] device (wlan0): supplicant interface state: scanning → associating
Aug 10 14:44:07 kctiir-desktop systemd[1]: Reloading OpenBSD Secure Shell server.
Aug 10 14:44:07 kctiir-desktop systemd[1]: Reloaded OpenBSD Secure Shell server.

I cannot tell if this is the cause of your issue.

You can reboot the device again and check the syslog right after thre boot and see what does the syslog tells you. Such “cannot enter desktop” issue has lots of possible causes. For example, even running out of disk space can cause it too.

Actually, if you don’t mind doing this, I would say even re-flash the sdcard has chance to bring it back.

Now I flash another card to run NX platform, the wifi driver kernel panic still exists.And 64GB SD card system with the problem not logging into the desktop , I check the disk space, it’s OK.

Can you remove your wifi module from the device, flash your board with sdkmanger and check again?

Please note that flashing “sdkmanager” and “sdcard image” are different.

I tried remove my wifi module with SD card,but it still hanged there.When I have time ,I will try to flash my board with SDK manager.Thanks.