Home > OS >  ARM development version of Linux system, the board collapse, was already unable to through the dmesg
ARM development version of Linux system, the board collapse, was already unable to through the dmesg

Time:09-16

Run (user mode application invokes the kernel driver), the board crash quit, already can't through the dmesg view the log,

After restart the development version before trying to find collapse records, the current system seems to be no record, how to view the previous record collapse and why?

Sh# ls var
Backups db local log run TMP
Cache lib lock preferences spool volatile

Sh# ls var/log
BTMP lastlog LXC messages private WTMP

Lastlog is empty, and there was other corresponding saved the collapse information records,


CodePudding user response:

1. Internal syslog server configuration system, log write disk (to prepare storage space and partition)
2. Or configure the syslog server, the internal syslog outward through the network to send directly to the
3. Same as above, using a serial port to send and receive log
4. If the compiler support parameters, which generate kdump kernel configuration (dump to storage or network) - this is the ultimate method, but may be added a lot of things,

CodePudding user response:

Can you open a serial console, run to see?

CodePudding user response:

Open the UART grasp, like the sudden restart, can only use a serial port to catch as much as possible the kernel log, keep the log in the system or other memory card, can not save the log,
  • Related