public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
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: Sat, 13 Jun 2009 00:11:25 -0700	[thread overview]
Message-ID: <m1ljnwwqua.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <9C8DECFB07C.00000038dseetharam@inbox.com> (Dharmosoth Seetharam's message of "Fri\, 12 Jun 2009 23\:01\:35 -0800")

Dharmosoth Seetharam <dseetharam@inbox.com> writes:

> Hi Neil,
>
> Thanks for your quick reply.
>
> What you have suggested is nice when we got/save crash dump (i.e vmcore)
> What if we failed to save/capture vmcore info or vmcore is corrupted etc. then we dont get any information
> regarding the panic/crash/oops at anywhere?

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.
2) Have you tried a dry run and confirmed you can get a crash dump?
3) Are you using kvm


Eric


> Thanks and Regards
>
>  Seetharam
>
>
>> -----Original Message-----
>> From: nhorman@redhat.com
>> Sent: Fri, 12 Jun 2009 16:05:13 -0400
>> To: dseetharam@inbox.com
>> Subject: Re: /var/log/messages doesn't have crash info when kernel gets
>> panic/oops/crash
>> 
>> On Fri, Jun 12, 2009 at 01:25:49AM -0800, Dharmosoth Seetharam wrote:
>>> 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.
>>> 
>> run crash on the resultant vmcore file that kexec can produce/save and
>> get the
>> dmesg log out of it.
>> alternatively you can use makedumpfile with the --dump-dmesg log
>> 
>> Neil
>> 
>>> 
>>> 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
>
> ____________________________________________________________
> GET FREE SMILEYS FOR YOUR IM & EMAIL - Learn more at http://www.inbox.com/smileys
> Works with AIM®, MSN® Messenger, Yahoo!® Messenger, ICQ®, Google Talk™ and most webmails

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2009-06-13  7:11 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 [this message]
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=m1ljnwwqua.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