[olug] Intriguing random hangs! Followup

[Blaine Kahle]

IMHO, memory is too bloody cheap right now to worry about this. Buy
new RAM, replace old stuff that's under warranty (most is lifetime nowadays),
or plan ahead for situations like this and go the ECC route, if you're
paranoid like my boss (duck and cover) :P

-brk

>You'll need a detailed description of what EXACT areas are bad on the 
>chip, memtest86 can supposedly do this.  Then, areas of memory to avoid 
>are passed to the kernel via an "append=" in your lilo.conf.
>
>Im interested to see this feature put in the main kernel tree.
>
>Jason
>
>kaygee wrote:
>
>>Thanks to everyone who made suggestions regarding my last post.  I went to
>>BestBuy today and picked up some memory.  I'm testing it now but my
>>preliminary findings are that the other stick of memory was indeed to
>>blame.
>>Anyway, I'm looking to still use that stick by adding the BadRAM patch to
>>a new kernel.  Does anyone have any experience with this patch and if so
>>do you have any suggestions for me?  Thanks again.
>>Keith
>>----------
>>There's ease of use and then there's ease of usefulness.
>>Choose usefulness. Choose Linux.
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: olug-unsubscribe at bstc.net
>>For additional commands, e-mail: olug-help at bstc.net
>>
>
>
>
>--
>"That as we enjoy great advantages from others, we should be glad of an 
>opportunity to serve others by any invention of ours; and this we should 
>do freely and generously." - Benjamin Franklin, 1742,
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: olug-unsubscribe at bstc.net
>For additional commands, e-mail: olug-help at bstc.net


---------------------------------------------------------------------
To unsubscribe, e-mail: olug-unsubscribe at bstc.net
For additional commands, e-mail: olug-help at bstc.net