Hi, I’m trying to use a Unitree Go1. One of the Jetsons on it (Jetson Xavier NX) shows the following output from dmesg when booting up:
[ 1.785433] tegradc 15200000.nvdisplay: hdmi: edid read failed
[ 2.150635] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[ 2.150981] imx219 9-0010: board setup failed
[ 2.174977] imx219 10-0010: imx219_board_setup: error during i2c read probe (-121)
[ 2.175304] imx219 10-0010: board setup failed
/mnt: is a mountpoint cp: not writing through dangling symlink “etc/resolv.conf”
/sbin/init: /lib/aarch64-linux-gnu/libc.so.6: version ‘GLIBC_2.34’ not found (required by /usr/lib/aarch64-linux-gnu/libudev.so.1)
/sbin/init: /lib/aarch64-linux-gnu/libc.so.6: version ‘GLIBC_2.28’ not found (required by /usr/lib/aarch64-linux-gnu/libudev.so.1)
/sbin/init: /lib/aarch64-linux-gnu/libc.so.6: version ‘GLIBC_2.32’ not found (required by /usr/lib/aarch64-linux-gnu/libudev.so.1)
/sbin/init: /lib/aarch64-linux-gnu/libc.so.6: version ‘GLIBC_2.33’ not found (required by /usr/lib/aarch64-linux-gnu/libudev.so.1)
/sbin/init: /lib/aarch64-linux-gnu/libc.so.6: version ‘GLIBC_2.30’ not found (required by /usr/lib/aarch64-linux-gnu/libudev.so.1)
[ 3.962839] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 3.963096] CPU: 3 PID: 1 Comm: init Not tainted 4.9.201-tegra #1
[ 3.963243] Hardware name: NVIDIA Jetson Xavier NX Developer Kit (DT)
[ 3.963390] Call trace:
[ 3.963465] [] dump_backtrace+0x0/0x198
[ 3.963594] [] show_stack+0x24/0x30
[ 3.963718] [] dump_stack+0xa0/0xc8
[ 3.963847] [] panic+0x12c/0x2a8
[ 3.964083] [] do_exit+0xac/0xa50
[ 3.964211] [] do_group_exit+0x40/0xa8
[ 3.964339] [] __wake_up_parent+0x0/0x40
[ 3.964477] [] el0_svc_naked+0x34/0x38
[ 3.964582] SMP: stopping secondary CPUs
[ 3.964689] Memory Limit: none
[ 3.964770] trusty-log panic notifier - trusty version Built: 14:49:44 Jan 15 2021
[ 3.973051] Rebooting in 5 seconds…
a solution without having to re-flash is preferred .
I also do need to mention this is a university machine and I am not sure what caused the issue.