lkml.org 
[lkml]   [2001]   [Aug]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: broken memory chip -> software fix?
Date
From
> I have a broken bit in my memory - at address 0x04d5ae38 if you want
> to know the details (bit 29 of the double word there sometimes reads
> as 1 when it was written as 0, in particular if bit 15 is at 1). I
> discovered this by observing a one-bit corruption of some files, and
> diagnosed it by running memtest86.
>
> Now that I know the address, is there a way I can prevent Linux from
> using that region of memory in any way? The simplest and cleanest

Yep. The mem= option can exclude stuff. Alternatively you can
patch arch/i386/kernel/mm/init.c:mem_init() to skip that page.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:57    [W:0.063 / U:0.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site