From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jani Nikula <jani.nikula@intel.com>
Subject: Re: [PATCH 04/11] docs: Get rid of the badRAM guide
Date: Wed, 26 Oct 2016 22:19:37 -0200 [thread overview]
Message-ID: <20161026221937.5c06b48e@vento.lan> (raw)
In-Reply-To: <1477523979-5837-5-git-send-email-corbet@lwn.net>
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
next prev parent reply other threads:[~2016-10-27 0:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 23:19 [PATCH 00/11] Organize and clean up the admin and process guides Jonathan Corbet
2016-10-26 23:19 ` [PATCH 01/11] docs: Tweak the top-level Sphinx page Jonathan Corbet
2016-10-27 0:12 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 02/11] docs: retitle the kernel-documentation.rst Jonathan Corbet
2016-10-27 0:13 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 03/11] docs: Clean up and organize the admin guide a bit Jonathan Corbet
2016-10-27 0:18 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 04/11] docs: Get rid of the badRAM guide Jonathan Corbet
2016-10-27 0:19 ` Mauro Carvalho Chehab [this message]
2016-10-26 23:19 ` [PATCH 05/11] docs: Get rid of the "basic profiling" guide Jonathan Corbet
2016-10-27 0:20 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 06/11] docs: Get rid of the "bug-hunting" guide Jonathan Corbet
2016-10-27 0:23 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 07/11] docs: Apply some basic organization to the process guide Jonathan Corbet
2016-10-27 0:24 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 08/11] docs: Tweak submitting-patches.rst formatting Jonathan Corbet
2016-10-27 0:25 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 09/11] docs: Collapse the process guide TOC Jonathan Corbet
2016-10-27 0:26 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 10/11] docs: add a warning to submitting-drivers.rst Jonathan Corbet
2016-10-27 0:38 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 11/11] docs: Add a warning to applying-patches.rst Jonathan Corbet
2016-10-27 0:32 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161026221937.5c06b48e@vento.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome