* how to get kernel crashdump
@ 2019-09-13 13:55 Muni Sekhar
0 siblings, 0 replies; only message in thread
From: Muni Sekhar @ 2019-09-13 13:55 UTC (permalink / raw)
I’m having a Linux system, I’m seeing it gets hung during certain
tests. When it hung, it does not even respond for SYSRQ button, only
way to recover is power-button-only. No response for SYSRQ button
means kernel crashed?
After reboot I looked at the kern.log and most of the times it has
“^@^@^@^ ...“ line just before reboot. Can someone clarify me what the
kernel log entry “^@^@^@^ ...“ means? I suspect kernel is crashed, but
it does give any crashdump in kern.log.
Later I enabled the kernel crash dump(sudo apt install
linux-crashdump) and rerun the test but still nothing copied to the
disk(/var/crash/). I don’t have onboard serial port in my machine, so
I tried get the crash dump via netconsole, but this method also does
not able to catch the crash dump.
Can someone help me how to debug in this scenario?
And I'd like to know what other options available to get the crash dump?
Any help will be greatly appreciated.
Kernelnewbies mailing list
^ permalink raw reply [flat|nested] only message in thread
only message in thread, back to index
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-13 13:55 how to get kernel crashdump Muni Sekhar
Kernel Newbies archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/kernelnewbies/0 kernelnewbies/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 kernelnewbies kernelnewbies/ https://lore.kernel.org/kernelnewbies \
Example config snippet for mirrors
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git