Kernel panic

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

Hello, after connecting a servo motor via usb to the Jetson Nano and sending a command to make it move, it makes the Jetson crash. According to logs in console-ram oops-0 there is a kernel panic, and this is the output:

[    1.197037] tegradc tegradc.1: dpd enable lookup fail:-19
[    1.343289] imx219 7-0010: imx219_board_setup: error during i2c read probe (-121)
[    1.343358] imx219 7-0010: board setup failed
[    1.367202] imx219 8-0010: imx219_board_setup: error during i2c read probe (-121)
[    1.367264] imx219 8-0010: board setup failed
[    2.226824] usb 1-2.1: device not accepting address 3, error -71
[    2.726822] usb 1-2.1: device not accepting address 4, error -71
[    3.415008] usb 1-2.1: device descriptor read/64, error -32
[    3.594594] cgroup: cgroup2: unknown option "nsdelegate"
[    3.606973] usb 1-2.1: device descriptor read/64, error -32
[    3.878928] usb 1-2.1: device descriptor read/64, error -32
[    4.071022] usb 1-2.1: device descriptor read/64, error -32
[    4.182921] usb 1-2-port1: unable to enumerate USB device
[    4.248868] systemd-journald[1955]: File /var/log/journal/a3d9197b765643568af09eb2bd3e5ce7/system.journal corrupted or uncleanly shut down, renaming and replacing.
[    4.952996] random: systemd: uninitialized urandom read (16 bytes read)
[    4.963626] random: systemd: uninitialized urandom read (16 bytes read)
[    4.966483] random: systemd-journal: uninitialized urandom read (16 bytes read)
[    5.534800] random: crng init done
[    5.538233] random: 170 urandom warning(s) missed due to ratelimiting
[    6.704417] using random self ethernet address
[    6.722178] using random host ethernet address
[    7.327876] using random self ethernet address
[    7.332434] using random host ethernet address
[   13.365384] Bridge firewalling registered
[  780.594334] systemd-journald[1955]: File /var/log/journal/a3d9197b765643568af09eb2bd3e5ce7/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[  782.663418] tegra-i2c 7000c000.i2c: no acknowledge from address 0x50
[  782.670287] tegra-i2c 7000c400.i2c: no acknowledge from address 0x50
[ 3185.922024] INFO: rcu_preempt self-detected stall on CPU[ 3185.923158] INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 3185.923256] 0-...: (1 GPs behind) idle=89d/140000000000001/0 softirq=125397/125397 fqs=146 
[ 3185.923272] 
[ 3185.943101] 0-...: (1 GPs behind) idle=89d/140000000000001/0 softirq=125397/125397 fqs=147 
[ 3185.951584]  (t=5338 jiffies g=59172 c=59171 q=282)
[ 3212.888768] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ksoftirqd/0:6]
[ 3212.898343] Kernel panic - not syncing: softlockup: hung tasks
[ 3212.904259] CPU: 0 PID: 6 Comm: ksoftirqd/0 Tainted: G             L  4.9.337-tegra #1
[ 3212.912227] Hardware name: NVIDIA Jetson Nano Developer Kit (DT)
[ 3212.918277] Call trace:
[ 3212.920815] [<000000007faee8b5>] dump_backtrace+0x0/0x198
[ 3212.926294] [<00000000717ca80e>] show_stack+0x24/0x30
[ 3212.931425] [<00000000ff7ca7a6>] dump_stack+0xa0/0xc4
[ 3212.936546] [<000000000027ab17>] panic+0x128/0x2a4
[ 3212.941414] [<000000005f5f860a>] watchdog_unpark_threads+0x0/0x98
[ 3212.947574] [<0000000062ea4ab0>] __hrtimer_run_queues+0xd8/0x360
[ 3212.953643] [<00000000d929cbe7>] hrtimer_interrupt+0xa8/0x1e0
[ 3212.959453] [<00000000dd5ce593>] tegra210_timer_isr+0x38/0x48
[ 3212.965268] [<000000007b31ceeb>] __handle_irq_event_percpu+0x68/0x288
[ 3212.971770] [<00000000ab4eafdf>] handle_irq_event_percpu+0x28/0x60
[ 3212.978010] [<0000000064dc5c7c>] handle_irq_event+0x50/0x80
[ 3212.983647] [<0000000011672373>] handle_fasteoi_irq+0xd4/0x1c0
[ 3212.989535] [<000000000094d54b>] generic_handle_irq+0x34/0x50
[ 3212.995340] [<000000001e571c72>] __handle_domain_irq+0x68/0xc0
[ 3213.001231] [<00000000117e81f0>] gic_handle_irq+0x5c/0xb0
[ 3213.006687] [<000000004bd516c9>] el1_irq+0xe8/0x194
[ 3213.011628] [<00000000b35d5222>] __free_pages_ok+0xfc/0x4a0
[ 3213.017259] [<0000000031d50b38>] __free_page_frag+0x90/0xa0
[ 3213.022900] [<00000000b21f243d>] skb_free_head+0x38/0x48
[ 3213.028274] [<000000009ab5b0af>] skb_release_data+0x100/0x130
[ 3213.034079] [<00000000f9637238>] skb_release_all+0x30/0x40
[ 3213.039624] [<00000000b3e4c212>] consume_skb+0x38/0x118
[ 3213.044917] [<00000000f1213df9>] arp_process+0x160/0x708
[ 3213.050291] [<00000000f1cfd5f4>] arp_rcv+0x118/0x1a8
[ 3213.055323] [<000000001fa8c86f>] __netif_receive_skb_core+0x3b8/0xad8
[ 3213.061829] [<000000009dce01f6>] __netif_receive_skb+0x28/0x78
[ 3213.067728] [<0000000068229637>] netif_receive_skb_internal+0x2c/0xb0
[ 3213.074234] [<000000000641be21>] napi_gro_receive+0x15c/0x188
[ 3213.080046] [<0000000061ddfb0c>] rtl8168_rx_interrupt.isra.21+0x1f0/0x4d8
[ 3213.086891] [<000000000a539840>] rtl8168_poll+0x50/0x258
[ 3213.092272] [<000000005cf0dae1>] net_rx_action+0xf4/0x358
[ 3213.097731] [<000000006ae15e03>] __do_softirq+0x13c/0x3b0
[ 3213.103202] [<00000000c68d181f>] run_ksoftirqd+0x48/0x58
[ 3213.108586] [<00000000d4a06f06>] smpboot_thread_fn+0x160/0x248
[ 3213.114477] [<0000000033064513>] kthread+0xec/0xf0
[ 3213.119330] [<000000003ba1b452>] ret_from_fork+0x10/0x30
[ 3213.124703] SMP: stopping secondary CPUs
[ 3213.129001] Kernel Offset: disabled
[ 3213.132558] Memory Limit: none
[ 3213.250451] Rebooting in 5 seconds..

I do not have much experience dealing with kernel issues. What would be the problem here, or possible solutions? Thanks in advance.

2

A servo likely has a noisy power consumption, and lots of spikes. Maybe it is also too much power. I suggest you test by using an externally powered USB HUB. This will provide power from the HUB’s power instead of the Jetson.

Incidentally, the particular crash dump includes the rtl8168 wired ethernet driver, which is presumably unrelated to this. Power spikes and instability can cause various hardware to sporadically fail. If the powered HUB does not do the trick, then you’d also include this information:

  • Exact Jetson model, and mention if it is a dev kit or if it is a third party carrier board (if it uses only an SD card, and does not have eMMC, then probably it is a dev kit).
  • Output of “head -n 1 /etc/nv_tegra_release”.
  • List of whatever else is connected.
3

Thanks for the reply! The model is Jetson nano module P3448-0000 with heatsink, should be a dev kit. The output of the head -n 1 /etc/nv_tegra_release command is:
R32 (release), REVISION: 7.4, GCID: 33514132, BOARD: t210ref, EABI: aarch64, DATE: Fri Jun 9 04:25:08 UTC 2023
And this is a list of the connected devices: (Device 006 is the motor)
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0483:5740 STMicroelectronics STM32F407
Bus 001 Device 004: ID 046d:c542 Logitech, Inc.
Bus 001 Device 003: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

4

You apparently have a USB network device (I assume that is what the Realtek device is from the lsusb). This does mean that the USB itself might be at issue even though networking might “appear” to be unrelated. In that case I think the servo is the cause of the USB issue (due to power or noise). Can you use an externally powered USB HUB to test? There isn’t really a fix to software for power delivery issues.

5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.