summaryrefslogtreecommitdiffstats
path: root/Documentation/bad_memory.txt
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@s-opensource.com>2016-09-21 13:24:12 -0300
committerMauro Carvalho Chehab <mchehab@s-opensource.com>2016-10-24 08:12:35 -0200
commitd078a815196bc4b3d8fe728a0dbd83c07b928a47 (patch)
treeb94e7f14afd2f4584d0eae3593c6a8e362efd608 /Documentation/bad_memory.txt
parent684adc0aa3d482228d0727ee9a9a7b8deec62ca5 (diff)
downloadop-kernel-dev-d078a815196bc4b3d8fe728a0dbd83c07b928a47.zip
op-kernel-dev-d078a815196bc4b3d8fe728a0dbd83c07b928a47.tar.gz
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: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Diffstat (limited to 'Documentation/bad_memory.txt')
-rw-r--r--Documentation/bad_memory.txt26
1 files changed, 16 insertions, 10 deletions
diff --git a/Documentation/bad_memory.txt b/Documentation/bad_memory.txt
index df84162..5cac93e 100644
--- a/Documentation/bad_memory.txt
+++ b/Documentation/bad_memory.txt
@@ -1,9 +1,10 @@
+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):
-memmap=<size>$<address>
+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.
+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::
-With the numbers of the example above:
-memmap=64K$0x18690000
- or
-memmap=0x10000$0x18690000
+ memmap=0x10000$0x18690000
OpenPOWER on IntegriCloud