From: Bouchard Louis <louis.bouchard@canonical.com>
To: prasad@linux.vnet.ibm.com
Cc: Bouchard Louis <louis.bouchard@canonical.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: [Bug] Kdump does not work when panic triggered due to MCE
Date: Tue, 10 May 2011 09:19:49 +0200 [thread overview]
Message-ID: <4DC8E715.2050102@canonical.com> (raw)
In-Reply-To: <20110509170336.GC1963@in.ibm.com>
Hello,
Le 09/05/2011 19:03, K.Prasad a écrit :
> On Mon, May 09, 2011 at 05:21:06PM +0200, Bouchard Louis wrote:
>> 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.
>>
> That's interesting! Assuming that these are not software induced MCEs
> but panic() calls invoked due to unrecoverable memory errors in a
> physical machine, did you experience any situation where the kdump
> kernel hung/rebooted due to a second MCE (triggered while reading the
> faulty memory location belonging to the first kernel)?
What I'm relating is issues I have seen in the past, while I was
employed somewhere else. Unfortunately, I no longer have access to any
of those dumps.
Kind regards,
...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-10 7:19 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
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 [this message]
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=4DC8E715.2050102@canonical.com \
--to=louis.bouchard@canonical.com \
--cc=kexec@lists.infradead.org \
--cc=prasad@linux.vnet.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