document memmap option better and help people with bad memory
Provide example for memmap exclude option (it is slightly strange an non-trivial) and provide nice small HOWTO for people with bad memory.
---
commit ec630f2291d7a3a154e22fa54cd74e5f6aa47f9a
tree 9cf33f9fcda3ea363061acebc971c37815f6c907
parent 456fc99ea933d38466ee25681908868cde3425c5
author Pavel <[email protected]> Thu, 13 Mar 2008 09:06:15 +0100 committer Pavel <[email protected]> Thu, 13 Mar 2008 09:06:15 +0100
Documentation/bad_memory.txt | 45 +++++++++++++++++++++++++++++++++++ Documentation/kernel-parameters.txt | 4 +++ 2 files changed, 49 insertions(+), 0 deletions(-)
Documentation/bad_memory.txt new file +45 -0
@@ -0,0 +1,45 @@ +March 2008 +Jan-Simon Moeller, [email protected] + + +How to deal with bad memory e.g. reported by memtest86+ ? +######################################################### + +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 kernel-parameters.txt 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 +
Documentation/kernel-parameters.txt +4 -0
@@ -1131,6 +1131,10 @@ and is between 256 and 4096 characters. 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=64K$0x18690000 + or + memmap=0x10000$0x18690000 meye.*= [HW] Set MotionEye Camera parameters See Documentation/video4linux/meye.txt.
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Nack ... See comments ..
Am Donnerstag, 13. März 2008 09:08:04 schrieb Pavel Machek:
Quoted 36 lines
Provide example for memmap exclude option (it is slightly strange an non-trivial) and provide nice small HOWTO for people with bad memory.
Signed-off-by Jan-Simon Moeller <[email protected]>Signed-off-by Pavel Machek <[email protected]>---
commitec630f2291d7a3a154e22fa54cd74e5f6aa47f9a
tree9cf33f9fcda3ea363061acebc971c37815f6c907
parent456fc99ea933d38466ee25681908868cde3425c5
author Pavel <[email protected]> Thu, 13 Mar 2008 09:06:15 +0100 committer Pavel <[email protected]> Thu, 13 Mar 2008 09:06:15 +0100Documentation/bad_memory.txt | 45 +++++++++++++++++++++++++++++++++++ Documentation/kernel-parameters.txt | 4 +++ 2 files changed, 49 insertions(+), 0 deletions(-)Documentation/bad_memory.txt new file +12
-0@@ -0,0 +1,45 @@ +March 2008 +Jan-Simon Moeller, [email protected] + + +How to deal with bad memory e.g. reported by memtest86+ ? +######################################################### + +There are three possibilities I know of: + +1) Reinsert/swap the memory modules + +2) Buy new modules (best!) or try to exchange the memory
Documentation/bad_memory.txt line 22
Quoted 10 lines
Documentation/bad_memory.txt new file +10
-0+ 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
Typo from me: ^^^ remove "the"
Documentation/bad_memory.txt line 25
Quoted 3 lines
Documentation/bad_memory.txt new file +3
-0+here: http://rick.vanrein.org/linux/badram/ + +For more details see the BadRAM documentation.
Example: memtest86+ <- was here ... and has its context here (BadRAM-Pattern and so on) ...
Just switch the place.
Documentation/bad_memory.txt line 36
Quoted 11 lines
Documentation/bad_memory.txt new file +11
-0+ +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 kernel-parameters.txt for details): +memmap=<size>$<address> +
<move to BadRAM section>
Quoted 3 lines
Documentation/bad_memory.txt new file +1
-0+Example: memtest86+ reported here errors at address 0x18691458, 0x18698424and + some others. All had 0x1869xxxx in common, so I chose a
pattern of + 0x18690000,0xffff0000.
</move>
Quoted 11 lines
Documentation/bad_memory.txt new file +6
-0+ +With the numbers of the example above: +memmap=64K$0x18690000 + or +memmap=0x10000$0x18690000 +(quoted diff) +0
-0
b/Documentation/kernel-parameters.txtindex 533e67f..f25da88 100644
Documentation/kernel-parameters.txt and is between 256 and 4096 characters. · line 1140
Quoted 10 lines
Documentation/kernel-parameters.txt +4
-0@@ -1131,6 +1131,10 @@ and is between 256 and 4096 characters. 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=64K$0x18690000 + or + memmap=0x10000$0x18690000 meye.*= [HW] Set MotionEye Camera parameters See Documentation/video4linux/meye.txt.
Tnx, Pavel for inclusion.
Best regards,
Jan-Simon