Re: Masking out one page of RAM because of bit-errors.

• Next message: Alan Cox: "Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee"
• Previous message: Sandy Harris: "Re: Using Yarrow in /dev/random"
• In reply to: Patrick Mau: "Masking out one page of RAM because of bit-errors."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, Sep 12, 2000 at 06:18:36PM +0200, Patrick Mau wrote:
> I have a bad SDRAM chip with exactly one bit error. Memtest86 shows
> that the bit error always occurs at the address 0x4eff508. I tried
> to calculate the page number and it should be 20223.

There is a patch on http://home.zonnet.nl/vanrein/badram/ to avoid using
bad ram pages. I didn't test it - my ram is good ;-) (at least the ram in
my computer - I'd like to see a port of this program to my own brain...)

Jan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Alan Cox: "Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee"
• Previous message: Sandy Harris: "Re: Using Yarrow in /dev/random"
• In reply to: Patrick Mau: "Masking out one page of RAM because of bit-errors."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Sep 15 2000 - 21:00:19 EST