Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753941AbYCJTA3 (ORCPT ); Mon, 10 Mar 2008 15:00:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751851AbYCJTAS (ORCPT ); Mon, 10 Mar 2008 15:00:18 -0400 Received: from mail.gmx.net ([213.165.64.20]:53813 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751825AbYCJTAQ (ORCPT ); Mon, 10 Mar 2008 15:00:16 -0400 X-Authenticated: #7313500 X-Provags-ID: V01U2FsdGVkX18aTmcHteQaTrYcFbxYQ+AC9eJq34WU5iXf8+qbHH rGEhNMBs0+Obh7 From: Jan-Simon =?iso-8859-1?q?M=F6ller?= To: "H. Peter Anvin" Subject: Re: [PATCH 2.6.24] mm: BadRAM support for broken memory Date: Mon, 10 Mar 2008 19:59:46 +0100 User-Agent: KMail/1.9.9 Cc: Pavel Machek , Jiri Kosina , Ingo Molnar , devzero@web.de, linux-kernel@vger.kernel.org, rick@vanrein.org References: <182234194@web.de> <200803101523.03620.dl9pf@gmx.de> <47D56DD3.8060108@zytor.com> In-Reply-To: <47D56DD3.8060108@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200803101959.47202.dl9pf@gmx.de> X-Y-GMX-Trusted: 0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2994 Lines: 101 What about ... diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 533e67f..19343e1 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -1131,6 +1131,10 @@ and is between 256 and 4096 characters. It is defined in the file memmap=nn[KMG]$ss[KMG] [KNL,ACPI] Mark specific memory as reserved. Region of memory to be used, from ss to ss+nn. + Example: Exclude memory from 0x18690000-0x1869ffff + memmap=0x18690000$64K + or + memmap=0x18690000$10000 meye.*= [HW] Set MotionEye Camera parameters See Documentation/video4linux/meye.txt. Signed-off-by: Jan-Simon Moeller ... and/or ... diff --git a/Documentation/bad-memory.txt b/Documentation/bad-memory.txt new file mode 100644 index 0000000..53e817d --- /dev/null +++ b/Documentation/bad-memory.txt @@ -0,0 +1,55 @@ +March 2007 +Jan-Simon Moeller, dl9pf@gmx.de + + +How to deal with bad memory e.g. reported by memtest86+ ? +######################################################### + +There are three possibilities I know of: + +1) Buy new memory (best!) + +2) Try to exchange the memory if you have spare-parts + +3) Use BadRAM or memmap + +This Howto is about number 3) . + + +BadRAM +###### +BadRAM is actively developed and available as kernel-patch +here: http://rick.vanrein.org/linux/badram/ + +It takes the patterns of memtest86+ as arguments to exclude the defective +areas of the memory. + +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. + This means exclusion of the area from 0x18690000 to 0x1869ffff + (which is a block of 64k). + My kernel-cmdline was: badram=0x18690000,0xffff0000 + +There are efforts to bring BadRAM into mainline in some way, possibly using +memmap internally (maybe for 2.6.26 ?). +Thread on lkml: http://lkml.org/lkml/2008/3/2/42 + +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 different and you may need to calculate the values by yourself! + +Syntax to exclude a memory area (see kernel-parameters for details): +memmap=
$ + +With the numbers of the example above: +memmap=0x18690000$64K + or +memmap=0x18690000$0x10000 + +TODO: Multiple areas to exclude using memmap ? + Signed-off-by: Jan-Simon Moeller Best regards, Jan-Simon -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/