Commit d078a815 authored by Mauro Carvalho Chehab's avatar Mauro Carvalho Chehab
Browse files

Documentation/bad_memory.txt: convert it to ReST markup 



- promote the section level of the document name;
- add/remove spaces/new lines where needed to format the output;
- use quote blocks.
- add it to the user book.

Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@s-opensource.com>
parent 684adc0a

Documentation/bad_memory.txt

+16 −10
Original line number Diff line number Diff line 
How to deal with bad memory e.g. reported by memtest86+ ?

=========================================================



March 2008

Jan-Simon Moeller, dl9pf@gmx.de





How to deal with bad memory e.g. reported by memtest86+ ?

#########################################################



There are three possibilities I know of:
@@ -19,6 +20,7 @@ This Howto is about number 3) . 


BadRAM

######



BadRAM is the actively developed and available as kernel-patch

here:  http://rick.vanrein.org/linux/badram/
@@ -31,15 +33,19 @@ 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):

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:

With the numbers of the example above::



	memmap=64K$0x18690000

 or



or::



	memmap=0x10000$0x18690000

CRA Git | Maintained and supported by SUSTech CRA and CCSE