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

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
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:

  1. It’s a dev kit, carrier board version C02.
  2. Using a direct HDMI instead of adapter.
  3. It’s a new installation with 128GB sd card, it has enough disk space.
  4. Package version.
    $ dpkg -l | grep ‘nvidia-l4t-core’
    ii nvidia-l4t-core 32.4.2-20200408182620 arm64 NVIDIA Core Package
  5. Output of below command
sudo -s
egrep -H '.*' `find /sys -name edid`
exit

$ egrep -H ‘.*’ find /sys -name edid
/sys/kernel/debug/tegradc.0/edid: 00 ff ff ff ff ff ff 00 22 f0 3a 29 01 01 01 01
/sys/kernel/debug/tegradc.0/edid: 26 15 01 03 80 33 1d 78 2a 1e 55 a0 59 56 9f 27
/sys/kernel/debug/tegradc.0/edid: 0d 50 54 a1 08 00 81 c0 81 80 95 00 b3 00 d1 c0
/sys/kernel/debug/tegradc.0/edid: 01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c
/sys/kernel/debug/tegradc.0/edid: 45 00 fd 1e 11 00 00 1e 00 00 00 fd 00 32 4c 18
/sys/kernel/debug/tegradc.0/edid: 5e 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 48
/sys/kernel/debug/tegradc.0/edid: 50 20 32 33 31 31 0a 20 20 20 20 20 00 00 00 ff
/sys/kernel/debug/tegradc.0/edid: 00 43 4e 54 31 33 38 39 33 37 48 0a 20 20 01 35
/sys/kernel/debug/tegradc.0/edid: 02 03 14 b1 49 90 04 03 02 01 9f 13 12 11 65 03
/sys/kernel/debug/tegradc.0/edid: 0c 00 10 00 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00
/sys/kernel/debug/tegradc.0/edid: fd 1e 11 00 00 18 01 1d 00 72 51 d0 1e 20 6e 28
/sys/kernel/debug/tegradc.0/edid: 55 00 fd 1e 11 00 00 1e 02 3a 80 18 71 38 2d 40
/sys/kernel/debug/tegradc.0/edid: 58 2c 45 00 fd 1e 11 00 00 1e 01 1d 00 bc 52 d0
/sys/kernel/debug/tegradc.0/edid: 1e 20 b8 28 55 40 fd 1e 11 00 00 1e 02 3a 80 d0
/sys/kernel/debug/tegradc.0/edid: 72 38 2d 40 10 2c 45 80 fd 1e 11 00 00 1e 00 00
/sys/kernel/debug/tegradc.0/edid: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9d

  1. ‘dmesg --follow’ log on host PC when unpluging/pluging micro-b on TX2.
    $ 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

  1. Serial console log.
    Do not have it yet. Will search how to get that.

Thanks for any comments and suggestions.

6

Hi,

Waiting for your serial console log.

7

Serial console information can be found here:
http://www.jetsonhacks.com/2017/03/24/serial-console-nvidia-jetson-tx2/

Serial console programs usually have logging options, so you can simply have it record the boot. I use gtkterm, many other people use minicom for this.

8

Thanks @linuxdev for pointing out this useful link. As I said in another post, it turns out that the GPU card on this TX2 device got broken. I’m doing other stuff, may come back to this later or may not.