From: Dharmosoth Seetharam <dseetharam@inbox.com>
To: "Eric W. Biederman" <ebiederm@xmission.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: Sat, 13 Jun 2009 07:08:58 -0800 [thread overview]
Message-ID: <A0CF50B4BBE.0000004Fdseetharam@inbox.com> (raw)
In-Reply-To: <m1bpostedp.fsf@fess.ebiederm.org>
> -----Original Message-----
> From: ebiederm@xmission.com
> Sent: Sat, 13 Jun 2009 07:08:50 -0700
> To: dseetharam@inbox.com
> Subject: Re: /var/log/messages doesn't have crash info when kernel gets
> panic/oops/crash
>
> Dharmosoth Seetharam <dseetharam@inbox.com> writes:
>
>>>>> Basic questions.
>>>>> 1) Do you have panic on oops set?
>>>>> I think that setting more than anything else will be the
>>>>> difference in what shows up in /var/log/messages.
>>>>
>>>> Yes, in my case panic_on_oops was set with 1
>>>
>>> That is the reason thing don't show up in /var/log/messages
>>> because you panic before syslog has a chance to write the messages.
>>
>> Thanks.
>> So, if panic_on_oops set with 0(default), we will get all the
>> needed info like stack traces, bug info etc. in /var/log/messages then
>> reboots.
>>
>> Or do we need to apply any specific patches to get info in
>> /var/log/messages?
>>
>>>
>>>>> 2) Have you tried a dry run and confirmed you can get a crash dump?
>>>>
>>>> No, I haven't tried this.
>>>
>>> It sounds like you have not been getting the coredumps when problems
>>> happen. Running a simple test run to Alt-sysrq-c to confirm
>>> that things are basically setup ok is a good idea.
>>>
>> Sorry, I misunderstood your question.
>> I have gave dry run and confirmed that the dumps are getting saved in
>> particular dir and able to analyze.
>>
>> I did in both the ways like
>> 1 - echo c > /proc/sysrq-trigger
>> 2 -Alt -sysrq -c
>
> Then unless you are having problems capturing core dumps in real
> failure situations it sounds like all is well with the world.
>
> A kernel oops is normally not fatal and the kernel tries to limp along
> allowing for better diagnostics etc. This allows klogd to read the
> kernels message buffer and pass the kernel messages to syslog which
> writes the messages to /var/log/messages.
>
> After a kernel panic nothing is allowed to happen which prevents
> user space from writing to /var/log/messages in the usual way.
>
> If you want data in /var/log/messages it appears you have two choices.
> 1) Post process a core dump as Neil suggested and feed the kernel log
> buffer to syslog.
> 2) disable panic on oops. The system will continue to limp along
> allowing
> user space to write to /var/log/messages.
>
> Eric
Thanks Eric.
I will try all the ways as you suggested and let you know the outcome.
regards,
Seetharam
____________________________________________________________
FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family!
Visit http://www.inbox.com/photosharing to find out more!
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2009-06-13 15:07 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 [this message]
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=A0CF50B4BBE.0000004Fdseetharam@inbox.com \
--to=dseetharam@inbox.com \
--cc=ebiederm@xmission.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