Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936548AbcJQRBj (ORCPT ); Mon, 17 Oct 2016 13:01:39 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:44274 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934802AbcJQQ4W (ORCPT ); Mon, 17 Oct 2016 12:56:22 -0400 From: Mauro Carvalho Chehab To: Linux Doc Mailing List Cc: Mauro Carvalho Chehab , Mauro Carvalho Chehab , LKML , Jonathan Corbet , Mauro Carvalho Chehab Subject: [PATCH 08/32] Documentation/bad_memory.txt: convert it to ReST markup Date: Mon, 17 Oct 2016 14:55:45 -0200 Message-Id: <6684aed488394f52505bbbef6f8e34cd469e812d.1476717925.git.mchehab@s-opensource.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: References: In-Reply-To: References: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2628 Lines: 86 - 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 --- Documentation/bad_memory.txt | 26 ++++++++++++++++---------- Documentation/user/bad_memory.rst | 1 + Documentation/user/index.rst | 1 + 3 files changed, 18 insertions(+), 10 deletions(-) create mode 120000 Documentation/user/bad_memory.rst diff --git a/Documentation/bad_memory.txt b/Documentation/bad_memory.txt index df8416213202..5cac93e27a97 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=$

+Syntax to exclude a memory area (see kernel-parameters.txt for details):: + + memmap=$

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 -memmap=0x10000$0x18690000 +With the numbers of the example above:: + + memmap=64K$0x18690000 + +or:: + + memmap=0x10000$0x18690000 diff --git a/Documentation/user/bad_memory.rst b/Documentation/user/bad_memory.rst new file mode 120000 index 000000000000..c5ffc33348f2 --- /dev/null +++ b/Documentation/user/bad_memory.rst @@ -0,0 +1 @@ +../bad_memory.txt \ No newline at end of file diff --git a/Documentation/user/index.rst b/Documentation/user/index.rst index 280e62f21efa..d4886e366b5a 100644 --- a/Documentation/user/index.rst +++ b/Documentation/user/index.rst @@ -11,3 +11,4 @@ Contents: REPORTING-BUGS SecurityBugs kernel-parameters + bad_memory -- 2.7.4