All of lore.kernel.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 05:51:25 -0700	[thread overview]
Message-ID: <m1prd8uwj6.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <9E4E2F1EF78.00000173dseetharam@inbox.com> (Dharmosoth Seetharam's message of "Sat\, 13 Jun 2009 02\:22\:08 -0800")

Dharmosoth Seetharam <dseetharam@inbox.com> writes:

>> -----Original Message-----
>> From: ebiederm@xmission.com
>> Sent: Sat, 13 Jun 2009 00:11:25 -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:
>> 
>>> 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?
>> 
> Hi Eric,
>
>> 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.

>> 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.

>> 3) Are you using kvm
> kvm? kernel virtual memory?

Kernel virtual machine.  In particular.
Hardware acceleration for virtual machines.

Eric

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

  reply	other threads:[~2009-06-13 12:51 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 [this message]
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=m1prd8uwj6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.