[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D427763.7080301@computer.org>
Date: Fri, 28 Jan 2011 08:59:31 +0100
From: Jan Ceuleers <jan.ceuleers@...puter.org>
To: Tejun Heo <tj@...nel.org>
CC: "Ahmed S. Darwish" <darwish.07@...il.com>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, X86-ML <x86@...nel.org>,
Tony Luck <tony.luck@...el.com>, Dave Jones <davej@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Randy Dunlap <rdunlap@...otime.net>,
Willy Tarreau <wtarreau@...a.kernel.org>,
Willy Tarreau <w@....eu>, Dirk Hohndel <hohndel@...radead.org>,
Dirk.Hohndel@...el.com, IDE-ML <linux-ide@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2][concept RFC] x86: BIOS-save kernel log to disk upon
panic
On 25/01/11 15:49, Tejun Heo wrote:
> I'm afraid this is gonna be something which works sometimes (or even
> more times than not) but can't ever be made reliable. I think it
> would be better to head toward usb or other kind of early console.
Apologies in advance if this is a stupid idea, but would it be possible
and safer to dedicate a whole device (such as a USB thumb drive or a
memory card) to this? You could initialise the media in a certain way to
let the kernel know that it is OK to trample on the device.
You'd have a mkpoops command (make persistent oops :-). Perhaps this
could be a new partition table type. The kernel could either auto-detect
such a device or be told which-one to use. It could then, upon crash and
prior to writing to it, re-verify that the device bears the hallmarks of
being a poops device.
Thanks, Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists