diff mbox

[04/11] docs: Get rid of the badRAM guide

Message ID 1477523979-5837-5-git-send-email-corbet@lwn.net
State New
Headers show

Commit Message

Jonathan Corbet Oct. 26, 2016, 11:19 p.m. UTC
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>

---
 Documentation/admin-guide/bad-memory.rst | 50 --------------------------------
 Documentation/admin-guide/index.rst      |  1 -
 2 files changed, 51 deletions(-)
 delete mode 100644 Documentation/admin-guide/bad-memory.rst

-- 
2.7.4

Comments

Mauro Carvalho Chehab Oct. 27, 2016, 12:19 a.m. UTC | #1
Em Wed, 26 Oct 2016 17:19:32 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:

> The last release of this tool was for 2.6.28; it's hard to see how it has

> any relevance to current kernels.


I suspect that only the BadRAM data there is obsolete.

Anyway, I'm fine if you want to remove this one.

> 

> Signed-off-by: Jonathan Corbet <corbet@lwn.net>

> ---

>  Documentation/admin-guide/bad-memory.rst | 50 --------------------------------

>  Documentation/admin-guide/index.rst      |  1 -

>  2 files changed, 51 deletions(-)

>  delete mode 100644 Documentation/admin-guide/bad-memory.rst

> 

> 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




Thanks,
Mauro
diff mbox

Patch

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