From: WANG Cong <xiyou.wangcong@gmail.com>
To: kexec@lists.infradead.org
Subject: Re: [Bug] Kdump does not work when panic triggered due to MCE
Date: Tue, 10 May 2011 10:21:08 +0000 (UTC) [thread overview]
Message-ID: <iqb3ij$e10$2@dough.gmane.org> (raw)
In-Reply-To: 20110509170336.GC1963@in.ibm.com
On Mon, 09 May 2011 22:33:36 +0530, K.Prasad wrote:
> 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)?
Someone discussed this with me inside RH, is disabling MCE
checking in the second kernel an acceptable solution?
> We're contemplating a solution on the similar lines (refer the
> description of 'slim' kdump at https://lkml.org/lkml/2011/5/4/396) to
> create a 'crash tool readable coredump containing a message that
> indicates the cause of the crash as MCE (and not any data from the old
> memory).
>
You might want to try use other way instead of memory to store
the log of the first kernel, for example, mtdoops.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2011-05-10 10:21 UTC|newest]
Thread overview: 20+ 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 16:54 ` K.Prasad
2011-05-06 17:38 ` Andi Kleen
2011-05-06 17:38 ` Andi Kleen
2011-05-09 16:35 ` K.Prasad
2011-05-09 16:35 ` K.Prasad
2011-05-10 1:28 ` Huang Ying
2011-05-10 1:28 ` Huang Ying
2011-05-09 12:39 ` Vivek Goyal
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
2011-05-10 10:21 ` WANG Cong [this message]
2011-05-09 16:53 ` K.Prasad
2011-05-09 16:53 ` K.Prasad
2011-05-09 17:05 ` Vivek Goyal
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='iqb3ij$e10$2@dough.gmane.org' \
--to=xiyou.wangcong@gmail.com \
--cc=kexec@lists.infradead.org \
/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.