Jetson nx ,the system Abnormal operation

jetpack 4.6.1
nx

硬件底板是我们自己做的,然后运行了我们自己的程序,但是系统莫名其妙的崩溃了(系统没有重启,就是程序进程异常了),我们通过supervisor守护的程序,但是supervisor也不能查看进程状态了,我查查看了系统日志,但是我没有最终确定是哪条记录导致的异常,能帮我看一下么?

We made the hardware backplane ourselves, and then ran our own program, but the system crashed inexplicably (if the system didn’t restart, the program process was abnormal). We passed the supervisor daemon, but the supervisor couldn’t check the process status. I checked the system log, but I didn’t finally determine which record caused the exception. Can you help me?
kern.log (777.2 KB)
syslog (1001.3 KB)

If without your program, will the system crash?
What kind of the program you developed?

目标检测和目标跟踪,同时上面运行了java以及mysql,使用了串口
Target detection and target tracking. At the same time, Java and MySQL are running on it, and the serial port is used

我觉得和我的程序关系不大,应该是系统层面的问题,如果我们新作的硬件,是否需要重新编译内核呢,内核这块我不太懂,没有做额外的扩展,板子只是引出了一个HDMI,2个USB,两个串口,一个调试串口等
I don’t think it has much to do with my program. It should be a system level problem. If we make new hardware, do we need to recompile the kernel? I don’t know much about the kernel. I didn’t make additional enrollment expansion. The board just leads to one HDMI, two USB, two serial ports, one debugging serial port, etc

同样,我还测试了把固态放到套件的板子上就没有崩溃
Similarly, I also tested that putting the solid state on the board of the kit did not crash

情况大致就是这样,您能给我点建议如何排查这个问题么,系统日志有点看不明白和哪条记录有关系
The situation is basically like this. Can you give me some suggestions on how to troubleshoot this problem? The system log is a little unclear about which record it has to do with

syslog may not able to dump the log in time.

Need to dump the log from uart.

好的,我知道这样操作,今天测试就是这么观察的,没有遇到崩溃的现象,同时想请教一下,MODE 20W cpu有时候使用率100%,这样会不会导致系统不稳定呢

OK, I know how to operate like this. Today’s test is based on this observation. There is no crash. At the same time, I would like to ask if the mode 20W CPU utilization rate is 100% sometimes. Will this lead to system instability

It should not, if there is no thermal problem.

好的,这个问题我后来就没有遇到了,等我下次遇到的我做好调试口的记录再咨询

OK, I haven’t encountered this problem since then. I’ll make a record of the debugging port and consult again when I encounter it next time