[ale] Bad memory, need to work around it

Michael B. Trausch mike at trausch.us
Tue May 10 10:48:47 EDT 2011


On 05/09/2011 12:22 PM, David A. Merritt wrote:
> How about this boot option:
>
>           memmap=nn[KMG]$ss[KMG]
>                           [KNL,ACPI] Mark specific memory as reserved.
>                           Region of memory to be used, from ss to ss+nn.
>                           Example: Exclude memory from 0x18690000-0x1869ffff
>                                    memmap=64K$0x18690000
>                                    or
>                                    memmap=0x10000$0x18690000

As I noted in my original post, if I do that, the problem is that the 
kernel refuses to boot.  I'm not sure why.  It gives an "early 
exception" panic message.

I'm not sure if this is because of some sort of a mismatch between 
memtest's output and what I have to feed into Linux.

I did read something about a fork of memtest that would output 
parameters for the Linux kernel.  I need to look into that.

I'll also look into the whole thing about lifetime replacement.  What I 
might do in the short-term is get another 4 GB of RAM (this system 
originally had 8 GB, but then a stick went bad, and then another one 
did, and now a third) and install it.  THen send off the existing RAM 
for replacement.  That way, when all is said and done I'll be back to 8 
GB.  For some of the things that I do, 4 GB can be tight.

Admittedly, that can be fixed by making some of the things I do more 
efficient than they are.

	--- Mike


More information about the Ale mailing list