Bad memory

cornel panceac cpanceac at
Fri Jan 18 18:49:14 UTC 2013

2013/1/18 Justin M. Forbes <jmforbes at>

> On Thu, Jan 17, 2013 at 09:18:40AM -0800, Chuck Forsberg WA7KGX N2469R
> wrote:
> > Recently I discovered the motherboard that had been running
> > had an undetected bad memory chip.   This is a real confidence builder.
> >
> > Currently, running a definitive memory test requires hours of down time.
> > The user mode memory tester has serious limitations.
> >
> > I propose kernel support for a user mode program similar to memtest86
> > to allow such a program to request a hardware block of memory and
> > relocate whatever was in that block to another memory area.  This way
> > all of the memory can be checked in the background of a running system.
> >
> There are a lof of reasons that this isn't feasible on a running system.
> You just don't have access to all of the memory for a full check.
> Justin
> why not? is there something that can not be relocated in RAM?

on the other hand, wasn't there supposed to be a way to exclude a damaged
RAM area by passing some arguments to the kernel?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the test mailing list