Dear nvidia team:
There is an hung abnormality in our device. Please help me to analyze it. This robot customer is very important.It’s very urgent.
Thanks
syslog.txt (7.0 MB)
I can’t be of much help, but some more information will help whoever answers (plus I’ll add some context):
- What L4T release is this? See “
head -n 1 /etc/nv_tegra_release”. - Is this a developer’s kit, or is it using a third party carrier board?
- It seems you have installed an RT kernel patch. Did you install the main kernel and all modules? Did you update the initrd?
- Is this booting to eMMC (which would mean it is a commercial module)? Or is this booting to a dev kit SD card (dev kit NX modules do not have eMMC)?
- I see some relation to the Intel iwlwi wifi. I’ve heard of some known issues with the iwlwifi driver (I don’t know the details).
It is something of a wild guess, and someone else will need to look since it also showed an issue with an NVIDIA module (but it wasn’t necessarily the module at fault, it could have been an inability to load the module due to replacement kernel configuration), but it seems likely this is related to either the Intel iwlwifi driver or the kernel not being fully/correctly installed. If it is the former, then it might also be related to having both a bug in the Intel driver and maybe firmware which is intended to upload into the iwlwifi hardware.
Just out of curiosity, if you run the command “lsmod”, do any modules show up? What do you see from “cat /proc/cmdline”?
The register 0x3100008 is from UARTA.
What kind of device did you add on it?
It’s connected to a RS485 driver IC.But no peripherals were connected to it during the operation of the device.
$cat /sys/class/tty/ttyTHS1/iomem_base
$0x3100000
How to trigger the error there? Is it kind of random one or you have a step that can 100% reproduce it?
Could you share the full dmesg and device tree for further check?
Please also share the reproduce step with us to verify as we don’t see similar error on the devkit with default JP6.2 BSP package.
This problem cannot 100% reproduce it.If we reproduced it we will provide a full dmeg log.On the other hand,we also have modified the uart function on the customized board, please help see if it will affect it?I have attacted it.
uart_modify.txt (3.3 KB)
I have reprodced the issue again and captured full system logs and uart log.Please help us to analyze.
log.zip (786.7 KB)
testrt-uart.log (227.0 KB)
It seems you customize uartb: serial@3110000 in device tree but the error reporting for Address : 0x31000xx which is used by UART-A.
Do you have any customization for UART-A?(i.e. uarta: serial@3100000)?
Please also share the full device tree captured from your board.
I have no customization for UART-A.
tegra234-p3768-0000+p3767-0000-nv-super.txt (315.6 KB)
There is no update from you for a period, assuming this is not an issue anymore.
Hence, we are closing this topic. If need further support, please open a new one.
Thanks ~1105
How about from the HW?
Or could you reproduce the issue on the devkit?
If so, please share the detailed steps with us to verify and debug further.