summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJonathan Corbet <corbet@lwn.net>2016-10-26 16:20:27 -0600
committerJonathan Corbet <corbet@lwn.net>2016-10-27 16:36:26 -0600
commit2c79dcafd8ecdfd44ee4c509a9c55785b022eba9 (patch)
tree5cae3db99018b00b1b82b05462f417e0ec931423
parent7358bb2f3293461737a61850c56523695f5b2219 (diff)
downloadblackbird-op-linux-2c79dcafd8ecdfd44ee4c509a9c55785b022eba9.tar.gz
blackbird-op-linux-2c79dcafd8ecdfd44ee4c509a9c55785b022eba9.zip
docs: Get rid of the badRAM guide
The last release of this tool was for 2.6.28; it's hard to see how it has any relevance to current kernels. Signed-off-by: Jonathan Corbet <corbet@lwn.net>
-rw-r--r--Documentation/admin-guide/bad-memory.rst50
-rw-r--r--Documentation/admin-guide/index.rst1
2 files changed, 0 insertions, 51 deletions
diff --git a/Documentation/admin-guide/bad-memory.rst b/Documentation/admin-guide/bad-memory.rst
deleted file mode 100644
index a5c0e25e496f..000000000000
--- a/Documentation/admin-guide/bad-memory.rst
+++ /dev/null
@@ -1,50 +0,0 @@
-How to deal with bad memory e.g. reported by memtest86+ ?
-=========================================================
-
-March 2008
-Jan-Simon Moeller, dl9pf@gmx.de
-
-
-
-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 admin-guide/kernel-parameters.rst 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
diff --git a/Documentation/admin-guide/index.rst b/Documentation/admin-guide/index.rst
index 2ce2bf02824b..d737ae71efc6 100644
--- a/Documentation/admin-guide/index.rst
+++ b/Documentation/admin-guide/index.rst
@@ -58,5 +58,4 @@ configure specific aspects of kernel behavior to your liking.
binfmt-misc
mono
java
- bad-memory
basic-profiling
OpenPOWER on IntegriCloud