From: Dharmosoth Seetharam <dseetharam@inbox.com>
To: kexec@lists.infradead.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
fastboot@lists.linux-foundation.org, vgoyal@in.ibm.com
Subject: /var/log/messages doesn't have crash info when kernel gets panic/oops/crash
Date: Fri, 12 Jun 2009 01:25:49 -0800 [thread overview]
Message-ID: <913DA90C6C8.0000039Bdseetharam@inbox.com> (raw)
Hi,
I have encounter a problem called /var/log/messages does not contain any information
on kernel crash dump.
Prior to enabling KEXEC we saw stack traces and bug info etc in /var/log/messages.
After enabling KEXEC feature those info was missed.
How can we get those missed info in /var/log/messages even when KEXEC feature is enabled.
Any help will appreciate.
Thanks and Regards
Seetharam
____________________________________________________________
Receive Notifications of Incoming Messages
Easily monitor multiple email accounts & access them with a click.
Visit http://www.inbox.com/notifier and check it out!
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2009-06-12 19:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 9:25 Dharmosoth Seetharam [this message]
2009-06-12 20:05 ` /var/log/messages doesn't have crash info when kernel gets panic/oops/crash Neil Horman
2009-06-13 7:01 ` Dharmosoth Seetharam
2009-06-13 7:11 ` Eric W. Biederman
2009-06-13 10:22 ` Dharmosoth Seetharam
2009-06-13 12:51 ` Eric W. Biederman
2009-06-13 13:24 ` Dharmosoth Seetharam
2009-06-13 14:08 ` Eric W. Biederman
2009-06-13 15:08 ` Dharmosoth Seetharam
2009-06-13 18:07 ` Neil Horman
2009-06-16 4:43 ` Dharmosoth Seetharam
2009-06-16 5:43 ` [Fastboot] " Haren Myneni
2009-06-16 6:19 ` Eric W. Biederman
2009-06-16 6:19 ` Eric W. Biederman
2009-06-16 11:24 ` Neil Horman
2009-06-16 11:47 ` Dharmosoth Seetharam
[not found] <9e4e2f1ef78.00000173dseetharam@inbox.com>
[not found] ` <9c8decfb07c.00000038dseetharam@inbox.com>
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=913DA90C6C8.0000039Bdseetharam@inbox.com \
--to=dseetharam@inbox.com \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.linux-foundation.org \
--cc=kexec@lists.infradead.org \
--cc=vgoyal@in.ibm.com \
/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