Skip to contentSkip to conversation

patch/option to wipe memory at boot?

DISCUSSION David Madore 3 participants 4 messages Sep 17, 2007 – Sep 19, 2007

lore
Share & tools
lore
#0 lore raw

Hi,

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.

Happy hacking,

Signature · 3 lines
     David A. Madore
    ([email protected],
     http://www.madore.org/~david/ )
#1 lore raw
Quoted 12 lines · David Madore

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.

Quoted 5 lines

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

#2 lore raw
Quoted 3 lines · Jeremy Fitzhardinge

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.

Happy hacking,

Signature · 3 lines
     David A. Madore
    ([email protected],
     http://www.madore.org/~david/ )
#3 lore raw
Quoted 5 lines · David Madore
Quoted 3 lines · Jeremy Fitzhardinge

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.

Quoted 7 lines

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