Hi, I have had problems when my device runs for a long time, it may not operate as normal. My system is likely to crash the kernel. But when I reboot my device and check syslog then my device isn’t rebooted. I think it goes into an idle state. So, what must I do anything to check the reason leading to an idle state? Thanks.
Basically your previous topic already has the answer for what to do…
No, it is another problem. Thanks
The method to analyze the problem is same… Dump log from serial console and check it.
the new problem it doesn’t have anything logged from the kernel. And when I enter the reset button, it runs normally.
What kind of method are you using to check “logged from the kernel”?
If this is kernel panic, then your syslog of course won’t have any log there…
I am checking the log from file /var/log/syslog. I see my device isn’t rebooted and kernel panic it is still stuck and doesn’t create anything log. So, I think my device ran into an idle state.
As I already told, use the UART serial console to check the status…
Syslog won’t record things when system goes hang…
I am really not sure what is going on here that it seems you don’t really understand much of what we are trying to say here.
I understand what you say but my device is located in another city. I can’t go to this place to check the log from uart port.
With my knowledge log from uart port i just get in runtime. But my device is not running How i can get log from this.
You need to enable the UART log before the system hang. Check the last log got recorded on UART console to see why it goes into crash/hang…
That is also what I asked you to do on your Xavier NX post…
UART log would even print logs when system not boot into kernel… That is why it is more reliable than syslog which can only record kernel log when system is not dead…
it is hard for me to reach my device to get the syslog from uart port. I wanna have another way. Thanks.
You can only try ramoops.
https://www.kernel.org/doc/html/v4.15/admin-guide/ramoops.html
Otherwise, no other useful method.
Also, just to clarify again. We are not asking you to dump “syslog”. UART port itself will record the log but they are not syslog…
I don’t really know what is your purpose to keep using this term “syslog”. Syslog does not provide much help in this case.
or you can talk to me for some reason leading a device run into idle state. I think my system is not crash the kernel. If crashed my log can have some log related to kernel. But i checked my log don’t have anything.
but i just have syslog in this case. i don’t have other information from other log to check my problem
Yes, you only have syslog. That is why you cannot analyze anything here.
Syslog won’t record logs when kernel panic happened. I already mentioned this for about 3 times…
You can only try ramoops or UART log which would record the logs. Other method won’t record the log when system goes crash.
thanks, let me try with ramoops
I remember ramoops was already enabled by default. So you only need to try
mount -t pstore pstore /mnt/
cat /mnt/ftrace-ramoops
Of course you need to reproduce the issue too.
Thanks, my errors appear randomly. Let me try to reproduce this issue.
One question. How did you reset the board in this remote situation?