From: ebiederm@xmission.com (Eric W. Biederman)
To: Dharmosoth Seetharam <dseetharam@inbox.com>
Cc: Neil Horman <nhorman@redhat.com>,
vgoyal@in.ibm.com, kexec@lists.infradead.org,
fastboot@lists.linux-foundation.org
Subject: Re: /var/log/messages doesn't have crash info when kernel gets panic/oops/crash
Date: Mon, 15 Jun 2009 23:19:37 -0700 [thread overview]
Message-ID: <m1fxe0zona.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <C11029D0F00.00000039dseetharam@inbox.com> (Dharmosoth Seetharam's message of "Mon\, 15 Jun 2009 20\:43\:02 -0800")
Dharmosoth Seetharam <dseetharam@inbox.com> writes:
> Hi,
>
> I have experimented few things and results are below.
>
> Case 1) echo 0 > /proc/sys/kernel/panic_on_oops
> When BUG/oops occurred it is able to log the diagnostics to /var/log/messages
> and then continue(not switching to dump-saving kernel).
>
> What I am looking is - I want both the things to be happen.
> that is - it should log the appropriate messages in /var/log/messsages and
> should be able to take kernel dump.
You can't have it. Sorry.
Keeping user space alive is something that simply can not be done reliably.
> Please advice me, What we can do to achieve those things.
The only scenario I see possible is to take the dump. Use
makedumpfile or the crash log command to extract the kernel messages
and put them in the /var/log/messages.
Eric
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2009-06-16 6:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 9:25 /var/log/messages doesn't have crash info when kernel gets panic/oops/crash Dharmosoth Seetharam
2009-06-12 20:05 ` 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 [this message]
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=m1fxe0zona.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=dseetharam@inbox.com \
--cc=fastboot@lists.linux-foundation.org \
--cc=kexec@lists.infradead.org \
--cc=nhorman@redhat.com \
--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