From: swathi.suresh07@gmail.com (swathi suresh)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Debug Kernel Crash
Date: Thu, 31 Mar 2011 09:35:44 +0530 [thread overview]
Message-ID: <AANLkTimLU+W9P1jFL-wTC8=P-fp9XHFANqyWOY9uAU+C@mail.gmail.com> (raw)
Hello All,
I wanted to know what is the best way to generate the kernel crash
dump on kernel panic,
after doing some searching, i came to know we can use kexec to load a new
kernel on the kernel,
i followed the instruction from the following links
http://www.dedoimedo.com/computers/kdump.html
http://www.developertutorials.com/tutorials/linux/reboot-linux-faster-072204-1358/
I do found that the kernel load properly with the, kexec -l option followed
by kexec -e option,
but when i set the kernel to be loaded on kernel panic using the option
kexec -p, i see that after
kernel crash, the system just hangs, it wont even try to load the new
kernel. following are the
commands am using. Can some one point, if there is any thing wrong with
this.
chkconfig kdump on
/etc/init.d/kdump start
kexec -l --append="`cat /proc/cmdline`"
--initrd=/boot/initrd.img-2.6.35.10-kdump /boot/vmlinuz-2.6.35.10-kdump
kexec -e
works fine and loads the kernel successfully, i will be able to see *starting
new kernel* in the shell
*
*
*
chkconfig kdump on
/etc/init.d/kdump start
*
kexec -p --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-2.6.35.10*
-kdump
**
/boot/vmlinuz-2.6.35.10
-kdump
*
*
*
i simulate the panic by using
echo 1 > /proc/sys/kernel/sysrq
echo c > /proc/sysrq-trigger
which just crash the kernel and system hangs, and it does not show any
message *starting new kernel.*
*
*
Thanks,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110331/dc7bcc18/attachment.html
next reply other threads:[~2011-03-31 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 4:05 swathi suresh [this message]
2011-03-31 7:34 ` Debug Kernel Crash swathi suresh
2011-03-31 15:28 ` Thayumanavar S
2011-04-01 3:37 ` swathi suresh
2011-04-01 7:17 ` Thayumanavar S
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTimLU+W9P1jFL-wTC8=P-fp9XHFANqyWOY9uAU+C@mail.gmail.com' \
--to=swathi.suresh07@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).