<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2013/1/18 Justin M. Forbes <span dir="ltr"><<a href="mailto:jmforbes@linuxtx.org" target="_blank">jmforbes@linuxtx.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Thu, Jan 17, 2013 at 09:18:40AM -0800, Chuck Forsberg WA7KGX N2469R wrote:<br>
> Recently I discovered the motherboard that had been running <a href="http://omen.com" target="_blank">omen.com</a><br>
> had an undetected bad memory chip. This is a real confidence builder.<br>
><br>
> Currently, running a definitive memory test requires hours of down time.<br>
> The user mode memory tester has serious limitations.<br>
><br>
> I propose kernel support for a user mode program similar to memtest86<br>
> to allow such a program to request a hardware block of memory and<br>
> relocate whatever was in that block to another memory area. This way<br>
> all of the memory can be checked in the background of a running system.<br>
><br>
<br>
</div>There are a lof of reasons that this isn't feasible on a running system.<br>
You just don't have access to all of the memory for a full check.<br>
<span class="HOEnZb"><font color="#888888"><br>
Justin<br><br></font></span></blockquote><div>why not? is there something that can not be relocated in RAM?<br><br></div><div>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?<br>
</div></div><br></div></div>