From: Bouchard Louis <louis.bouchard@canonical.com>
To: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Cc: prasad@linux.vnet.ibm.com, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [Bug] Kdump does not work when panic triggered due to MCE
Date: Mon, 09 May 2011 17:21:06 +0200 [thread overview]
Message-ID: <4DC80662.9000703@canonical.com> (raw)
In-Reply-To: <20110509123902.GA5975@redhat.com>
Hello,
Le 09/05/2011 14:39, Vivek Goyal a écrit :
>
> Prasad,
>
> I have never tried taking dump in MCE situation. Does kdump work on this
> machine with normal panic()?
>
> Use --debug and --serial option in kexec-tools to print some debug message
> and look for "I am in purgatory". This will tell you whether you hanged
> in first kernel or second kernel.
>
> Then put "outb()" messages in the kernel to trace what happened.
>
> Thanks
> Vivek
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
I have seen numerous occurrences of MCE triggered kernel panics on both
RHEL & SLES environment used on IA32 architecture. Both in contexts
where kexec/kdump was being used.
Matter of fact, MCE triggered panic are part of the reason that pushed
me to work on crashdc : only one crash command is required to get the
MCE trace out of the kernel ring buffer. This avoids transfering massive
amount of vmcore file over the net.
crashdc does well on those, mcelog can be applied on the data gathered.
HTH,
...Louis
--
Louis Bouchard
Server Support Analyst
Canonical Ltd
Ubuntu support: http://landscape.canonical.com
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2011-05-09 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 16:54 [Bug] Kdump does not work when panic triggered due to MCE K.Prasad
2011-05-06 17:38 ` Andi Kleen
2011-05-09 16:35 ` K.Prasad
2011-05-10 1:28 ` Huang Ying
2011-05-09 12:39 ` Vivek Goyal
2011-05-09 15:21 ` Bouchard Louis [this message]
2011-05-09 15:46 ` Vivek Goyal
2011-05-10 7:31 ` Bouchard Louis
2011-05-09 17:03 ` K.Prasad
2011-05-10 7:19 ` Bouchard Louis
2011-05-10 10:21 ` WANG Cong
2011-05-09 16:53 ` K.Prasad
2011-05-09 17:05 ` Vivek Goyal
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=4DC80662.9000703@canonical.com \
--to=louis.bouchard@canonical.com \
--cc=kexec@lists.infradead.org \
--cc=prasad@linux.vnet.ibm.com \
--cc=vgoyal@redhat.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