From: Chris Snook <csnook@redhat.com>
To: David Madore <david.madore@ens.fr>
Cc: linux-kernel@vger.kernel.org, Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: patch/option to wipe memory at boot?
Date: Wed, 19 Sep 2007 14:30:52 -0400 [thread overview]
Message-ID: <46F16ADC.3030307@redhat.com> (raw)
In-Reply-To: <20070917204325.GA23658@clipper.ens.fr>
David Madore wrote:
> On Mon, Sep 17, 2007 at 11:11:52AM -0700, Jeremy Fitzhardinge wrote:
>> Boot memtest86 for a little while before booting the kernel? And if you
>> haven't already run it for a while, then that would be your first step
>> anyway.
>
> Indeed, that does the trick, thanks for the suggestion. So I can be
> quite confident, now, that my RAM is sane and it's just that the BIOS
> doesn't initialize it properly.
>
> But I'd still like some way of filling the RAM when Linux starts (or
> perhaps in the bootloader), because letting memtest86 run after every
> cold reboot isn't a very satisfactory solution.
Bootloaders like to do things like run in 16-bit or 32-bit mode on boxes where
higher bitness is necessary to access all the memory. It may be possible to do
this in the bootloader, but the BIOS is clearly the correct place to fix this
problem.
-- Chris
next prev parent reply other threads:[~2007-09-19 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 15:51 patch/option to wipe memory at boot? David Madore
2007-09-17 18:11 ` Jeremy Fitzhardinge
2007-09-17 20:43 ` David Madore
2007-09-19 18:30 ` Chris Snook [this message]
[not found] <94rE7-89j-3@gated-at.bofh.it>
[not found] ` <94tmJ-2EJ-77@gated-at.bofh.it>
[not found] ` <94vHE-6xa-11@gated-at.bofh.it>
[not found] ` <95cD1-7gI-31@gated-at.bofh.it>
2007-09-20 11:17 ` Bodo Eggert
-- strict thread matches above, loose matches on Subject: below --
2007-09-20 11:38 Tomasz Chmielewski
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=46F16ADC.3030307@redhat.com \
--to=csnook@redhat.com \
--cc=david.madore@ens.fr \
--cc=jeremy@goop.org \
--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