From: Jan Ceuleers <jan.ceuleers@computer.org>
To: Tejun Heo <tj@kernel.org>
Cc: "Ahmed S. Darwish" <darwish.07@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, X86-ML <x86@kernel.org>,
Tony Luck <tony.luck@intel.com>, Dave Jones <davej@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <rdunlap@xenotime.net>,
Willy Tarreau <wtarreau@hera.kernel.org>,
Willy Tarreau <w@1wt.eu>, Dirk Hohndel <hohndel@infradead.org>,
Dirk.Hohndel@intel.com, IDE-ML <linux-ide@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2][concept RFC] x86: BIOS-save kernel log to disk upon panic
Date: Fri, 28 Jan 2011 08:59:31 +0100 [thread overview]
Message-ID: <4D427763.7080301@computer.org> (raw)
In-Reply-To: <20110125144905.GC27510@htj.dyndns.org>
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
next prev parent reply other threads:[~2011-01-28 8:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 13:47 [PATCH 0/2][concept RFC] x86: BIOS-save kernel log to disk upon panic Ahmed S. Darwish
2011-01-25 13:51 ` [PATCH -next 1/2][RFC] x86: Saveoops: Switch to real-mode and call BIOS Ahmed S. Darwish
2011-01-25 17:26 ` H. Peter Anvin
2011-01-25 13:53 ` [PATCH -next 2/2][RFC] x86: Saveoops: Reserve low memory and register code Ahmed S. Darwish
2011-01-25 17:29 ` H. Peter Anvin
2011-01-26 9:04 ` Ahmed S. Darwish
2011-01-25 14:09 ` [PATCH 0/2][concept RFC] x86: BIOS-save kernel log to disk upon panic Ingo Molnar
2011-01-25 15:08 ` Tejun Heo
2011-01-25 17:33 ` H. Peter Anvin
2011-01-26 11:44 ` Ahmed S. Darwish
2011-02-03 14:36 ` Pavel Machek
2011-02-03 15:28 ` H. Peter Anvin
2011-02-03 17:57 ` Ingo Molnar
2011-02-03 21:07 ` H. Peter Anvin
2011-01-25 15:36 ` Ahmed S. Darwish
2011-01-25 16:02 ` James Bottomley
2011-01-25 17:05 ` Ahmed S. Darwish
2011-01-25 17:20 ` James Bottomley
2011-01-25 22:10 ` Mark Lord
2011-01-25 22:16 ` Randy Dunlap
2011-01-25 22:45 ` Jeff Garzik
2011-01-25 22:58 ` H. Peter Anvin
2011-01-26 0:26 ` Jeff Garzik
2011-01-31 2:59 ` Rusty Russell
2011-01-31 10:45 ` Ingo Molnar
2011-01-25 17:32 ` Tony Luck
2011-01-25 17:36 ` H. Peter Anvin
2011-01-25 19:04 ` Jeff Garzik
2011-01-25 14:49 ` Tejun Heo
2011-01-28 7:59 ` Jan Ceuleers [this message]
2011-01-25 20:25 ` Linus Torvalds
[not found] ` <20110126124954.GC24527@laptop>
2011-01-26 23:07 ` Luck, Tony
[not found] ` <20110126231620.GA14807@redhat.com>
[not found] ` <987664A83D2D224EAE907B061CE93D53019438EB02@orsmsx505.amr.corp.intel.com>
[not found] ` <20110126233033.GB14807@redhat.com>
[not found] ` <987664A83D2D224EAE907B061CE93D53019438EBB6@orsmsx505.amr.corp.intel.com>
[not found] ` <4D40F7F1.3020509@zytor.com>
[not found] ` <20110127120039.GD20279@elte.hu>
2011-01-27 18:35 ` Luck, Tony
[not found] ` <4D4197CB.9070201@zytor.com>
[not found] ` <20110127162429.GB26437@elte.hu>
2011-01-27 18:56 ` Luck, Tony
[not found] ` <20110127021338.GA20334@redhat.com>
[not found] ` <4D40F81E.1030009@zytor.com>
[not found] ` <20110127052639.GA16289@laptop>
[not found] ` <m1sjweyeax.fsf@fess.ebiederm.org>
2011-02-02 11:13 ` Ahmed S. Darwish
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=4D427763.7080301@computer.org \
--to=jan.ceuleers@computer.org \
--cc=Dirk.Hohndel@intel.com \
--cc=akpm@linux-foundation.org \
--cc=darwish.07@gmail.com \
--cc=davej@redhat.com \
--cc=hohndel@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=tony.luck@intel.com \
--cc=w@1wt.eu \
--cc=wtarreau@hera.kernel.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).