From: ebiederm@xmission.com (Eric W. Biederman)
To: Andi Kleen <ak@suse.de>
Cc: James Courtier-Dutton <James@superbug.co.uk>,
Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Black box flight recorder for Linux
Date: Sun, 09 Apr 2006 13:25:42 -0600 [thread overview]
Message-ID: <m1odzaima1.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <200604091704.47566.ak@suse.de> (Andi Kleen's message of "Sun, 9 Apr 2006 17:04:47 +0200")
Andi Kleen <ak@suse.de> writes:
> On Saturday 08 April 2006 18:28, James Courtier-Dutton wrote:
>> Andi Kleen wrote:
>> > On Saturday 08 April 2006 16:05, Robert Hancock wrote:
>> >> Andi Kleen wrote:
>> >>> James Courtier-Dutton <James@superbug.co.uk> writes:
>> >>>> Now, the question I have is, if I write values to RAM, do any of those
>> >>>> values survive a reset?
>> >>> They don't generally.
>> >>>
>> >>> Some people used to write the oopses into video memory, but that
>> >>> is not portable.
>> >> I wouldn't think most BIOSes these days would bother to clear system RAM
>> >> on a reboot. Certainly Microsoft was encouraging vendors not to do this
>> >> because it slowed down system boot time.to
>> >
>> > Reset button is like a cold boot and it generally ends up with cleared
>> > RAM.
>> >
>> > -Andi
>>
>> Thank you. That saved me 30mins hacking. :-)
Actually clearing the memory can be done at full memory bandwidth
which can happen in seconds. On systems with ECC you need initialize
all of the check bits so some kind of write to memory needs to happen.
In practice a reset does not clear the memory and only a few bits
tend to get flipped. Unless you can get support from the
BIOS/firmware developers it isn't a practical approach though.
> First if you're not aware of this - the "official" way right now
> to solve this problem is kexec + kdump + a preloaded crash kernel. But in
> practice it still has many problems because a lot of drivers cannot
> reinitialize the hardware properly. And of course it will users need
> to load the crash kernel in advance and lose about 64MB of RAM.
Does a kernel really need 64M? That number seems insanely large
to me. 8M should be more than sufficient if someone actually
tried to be small. If you are aiming for a dedicated hardware
solution you don't need even need a kernel in there and the
amount reserved could be reduced to less than a meg.
The size etc becomes a trade off between what is expedient
and maintainable.
Eric
next prev parent reply other threads:[~2006-04-09 19:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5ZjEd-4ym-37@gated-at.bofh.it>
[not found] ` <5ZlZk-7VF-13@gated-at.bofh.it>
2006-04-08 14:05 ` Robert Hancock
2006-04-08 7:17 ` Andi Kleen
2006-04-08 16:28 ` James Courtier-Dutton
2006-04-08 22:28 ` JustFillBug
2006-04-09 17:09 ` James Courtier-Dutton
2006-04-10 18:53 ` Ville Herva
2006-04-09 15:04 ` Andi Kleen
2006-04-09 19:25 ` Eric W. Biederman [this message]
2006-04-10 12:18 ` linux-os (Dick Johnson)
2006-04-10 19:44 ` Krzysztof Halasa
2006-04-10 20:07 ` linux-os (Dick Johnson)
2006-04-08 22:45 linux
-- strict thread matches above, loose matches on Subject: below --
2006-04-08 11:12 James Courtier-Dutton
2006-04-08 13:41 ` Andi Kleen
2006-04-08 19:42 ` Guennadi Liakhovetski
2006-04-08 16:40 ` Lee Revell
2006-04-08 17:30 ` Matti Aarnio
2006-04-09 19:23 ` Krzysztof Halasa
2006-04-10 12:01 ` Andy Green
2006-04-10 19:24 ` Krzysztof Halasa
2006-04-19 10:47 ` Krzysztof Halasa
2006-06-06 17:42 ` Krzysztof Halasa
2006-06-07 8:03 ` Jean Delvare
2006-06-07 10:18 ` Andy Green
2006-06-07 23:52 ` Krzysztof Halasa
2006-04-11 11:21 ` Jan Engelhardt
2006-04-10 3:06 ` Russell Senior
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=m1odzaima1.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=James@superbug.co.uk \
--cc=ak@suse.de \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.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
Powered by JetHome