串口出错,机器重启

hi nvidia
我们自己做的载板接串口设备后,出现错误并重启,软件版本为jp5.1.1,请帮忙看下,谢谢!
minicom_log20240316.txt (365.4 KB)

Hi yougang.hu,

[2024-03-16 07:27:20] [32840.462156] serial-tegra 3100000.serial: RxData PIO to tty layer failed
[2024-03-16 07:27:21] [32840.999609] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000001
[2024-03-16 07:27:21] [32841.008650] Mem abort info:
[2024-03-16 07:27:21] [32841.011520]   ESR = 0x96000044
[2024-03-16 07:27:21] [32841.014656]   EC = 0x25: DABT (current EL), IL = 32 bits
[2024-03-16 07:27:21] [32841.020104]   SET = 0, FnV = 0
[2024-03-16 07:27:21] [32841.023241]   EA = 0, S1PTW = 0
[2024-03-16 07:27:21] [32841.026463] Data abort info:
[2024-03-16 07:27:21] [32841.029410]   ISV = 0, ISS = 0x00000044
[2024-03-16 07:27:21] [32841.033343]   CM = 0, WnR = 1
[2024-03-16 07:27:21] [32841.036388] user pgtable: 4k pages, 48-bit VAs, pgdp=000000013a1c2000
[2024-03-16 07:27:21] [32841.042994] [0000000000000001] pgd=0000000000000000, p4d=0000000000000000
[2024-03-16 07:27:21] [32841.049979] Internal error: Oops: 96000044 [#1] PREEMPT SMP
[2024-03-16 07:27:21] [32841.055712] Modules linked in: input_leds fuse nvidia_modeset(OE) r8168(OE) xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink iptable_nat nf_nat nf_conntrack nf_defrag_ia
[2024-03-16 07:27:21] [32841.055783]  spi_tegra114 nvidia(OE) binfmt_misc nvmap ip_tables x_tables [last unloaded: mtd]
[2024-03-16 07:27:21] [32841.155723] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W  OE     5.10.104-tegra #1
[2024-03-16 07:27:21] [32841.163915] Hardware name: Unknown NVIDIA Orin NX Developer Kit/NVIDIA 

It seems there’s kernel panic so that the board reboot.

How do you connect the serial device?
Could you reproduce the same issue on the devkit?

hi nvidia
接的串口tx rx, cts/rts没接
这个是在部署现场出现的重启,没法用开发板去验证

Would you hit the kernel panic if you don’t connect serial device?

Which UART interface are you using?
Have you configured pinmux for UART before use and enable related node in device tree?

不接串口的时候不会重启
用的是串口ttyHTS0, 管脚99,101,103,105
pinmux确认是对的
根据log定位可能是在tegra_uart_rx_error_handle_timer中的tegra_uart_write(tup,ier,UART_IER)出错的,帮忙确认下这个是否是导致崩溃的原因

It seems the UART interface from M.2 Key E.
Could you run the following command to check if any driver is using these pins?

# cat /sys/kernel/debug/gpio

Do you mean that the issue is specific to the custom carrier board?
Devkit is used to verify it there’s HW design difference might cause the issue.

Also suggest to try latest bsp.

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