All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: David Madore <david.madore@ens.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: patch/option to wipe memory at boot?
Date: Mon, 17 Sep 2007 11:11:52 -0700	[thread overview]
Message-ID: <46EEC368.1040308@goop.org> (raw)
In-Reply-To: <20070917155149.GA5453@clipper.ens.fr>

David Madore wrote:
> Is there a patch or a boot option or something which wipes all
> available (physical) RAM at boot (or better, fills it with a fixed
> signature like 0xdeadbeef)?  I'm getting phony ECC errors and I'd like
> to test whether they go away when the RAM is properly initialized.
> Also, I'd like to know exactly which parts of RAM are being used and
> which are untouched since boot (hence the 0xdeadbeef signature).
>
> If this patch/option doesn't exist, can anyone give me a hint as to
> where and how it would be best to add this?  (I'm afraid I'm very
> ignorant as to how Linux sets up its RAM mapping.)  I'm concerned
> about x86 and x86_64.
>
> PS: I'm not finicky: it's all right if a couple of megabytes at the
> bottom of RAM are not scrubbed (I'm more interested about the top
> gigabyte-or-so), especially if they're guaranteed to be used by the
> kernel.
>   

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.

    J

  reply	other threads:[~2007-09-17 18:12 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 [this message]
2007-09-17 20:43   ` David Madore
2007-09-19 18:30     ` Chris Snook
     [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=46EEC368.1040308@goop.org \
    --to=jeremy@goop.org \
    --cc=david.madore@ens.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.