[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <10327.1317830438@turing-police.cc.vt.edu>
Date: Wed, 05 Oct 2011 12:00:38 -0400
From: Valdis.Kletnieks@...edu
To: Vivek Goyal <vgoyal@...hat.com>
Cc: "K.Prasad" <prasad@...ux.vnet.ibm.com>,
Borislav Petkov <bp@...en8.de>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
linux-kernel@...r.kernel.org, crash-utility@...hat.com,
kexec@...ts.infradead.org, Andi Kleen <andi@...stfloor.org>,
"Luck, Tony" <tony.luck@...el.com>, anderson@...hat.com,
tachibana@....nes.nec.co.jp, oomichi@....nes.nec.co.jp
Subject: Re: [Patch 1/4][kernel][slimdump] Add new elf-note of type NT_NOCOREDUMP to capture slimdump
On Wed, 05 Oct 2011 11:52:17 EDT, Vivek Goyal said:
> I am assuming that basic MCE error messages are available in kernel log.
They're not in the kernel log if it's an MCE that causes the kernel to declare
a panic. There's some MCE's that you can retry the operation and continue, and
some that you can get away with poisoning a page, killing the process, and rest
of the system is OK. But some you really need to roll over and die because you
can't guarantee kernel integrity anymore.
And at that point, those messages are never gonna make it to syslogd and onto
disk.
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists