[ linux-doc@xxxxxxxxxxxxxxx added, these should be the proper guys to merge this ] On Wed, 26 Nov 2008, Pavel Machek wrote: > > Document how to deal with bad memory reported with memtest. > > Signed-off-by: Pavel Machek <pavel@xxxxxxx> > > diff --git a/Documentation/bad_memory.txt b/Documentation/bad_memory.txt > new file mode 100644 > index 0000000..df84162 > --- /dev/null > +++ b/Documentation/bad_memory.txt > @@ -0,0 +1,45 @@ > +March 2008 > +Jan-Simon Moeller, dl9pf@xxxxxx > + > + > +How to deal with bad memory e.g. reported by memtest86+ ? > +######################################################### > + > +There are three possibilities I know of: > + > +1) Reinsert/swap the memory modules > + > +2) Buy new modules (best!) or try to exchange the memory > + if you have spare-parts > + > +3) Use BadRAM or memmap > + > +This Howto is about number 3) . > + > + > +BadRAM > +###### > +BadRAM is the actively developed and available as kernel-patch > +here: http://rick.vanrein.org/linux/badram/ > + > +For more details see the BadRAM documentation. > + > +memmap > +###### > + > +memmap is already in the kernel and usable as kernel-parameter at > +boot-time. Its syntax is slightly strange and you may need to > +calculate the values by yourself! > + > +Syntax to exclude a memory area (see kernel-parameters.txt for details): > +memmap=<size>$<address> > + > +Example: memtest86+ reported here errors at address 0x18691458, 0x18698424 and > + some others. All had 0x1869xxxx in common, so I chose a pattern of > + 0x18690000,0xffff0000. > + > +With the numbers of the example above: > +memmap=64K$0x18690000 > + or > +memmap=0x10000$0x18690000 > + > > -- > (english) http://www.livejournal.com/~pavelmachek > (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html > -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
