[ale] Bad memory, need to work around it

[Greg Clifton]

Mike,

Why play around with bad RAM. If you expect more of it to fail, why take the
chance that it might hose something important during a write to the HDD.
Pretty much all RAM has lifetime warranty these days. If it is name brand
such as Kingston, Crucial, etc. just type in the part number in the
manufacturer's web site and see if it is covered. Get your new RAM for the
cost of mailing in the bad stuff.

Meanwhile, buy at least a decent power strip if not a UPS that has the $
coverage for any attached device and your whole system is covered should
something else get fried.



On Mon, May 9, 2011 at 12:22 PM, David A. Merritt <dmerritt at comcast.net>wrote:

> On Mon, 9 May 2011, Michael Trausch wrote:
>
> > On Mon, May 9, 2011 at 11:13, Jim Kinney <jim.kinney at gmail.com> wrote:
> >> http://rick.vanrein.org/linux/badram/
> >
> > You assume I can compile a kernel.  :-)
> >
> > Sorry, can't do that.
> >
> > At least, not until I can find a way to disable this area of RAM.
> > Building anything sizeable will result in an ICE from GCC ATM.
>
> 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
>
> -dam
>
> --
>
> David A. Merritt
> dmerritt at comcast.net
> boulder.dam at gmail.com
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ale.org/pipermail/ale/attachments/20110509/efc4d12e/attachment.html