Skip to contentSkip to conversation

mm: BadRAM support for broken memory

PATCH [email protected] 9 participants 24 messages Mar 4, 2008 – Mar 11, 2008 Documentation

lore
Share & tools
lore
#1 lore raw
Quoted 7 lines · * [email protected] <[email protected]> wrote:
Quoted 1 line

What is wrong with mem=exactmap?

probably no ordinary user knows how to use it instead of badram?
http://lists.opensuse.org/opensuse/2007-04/msg00501.html

someone please show us how to use that instead of badram or how this can replace what badram does.

as i said it in another reply to this thread, it would be perfectly acceptable for upstream to merge an easier to use boot option - be that badmem=addr$size or excludemem=addr$size. Please send a patch :-)

Ingo

#2 lore raw

Ingo,

Quoted 3 lines

as i said it in another reply to this thread, it would be perfectly acceptable for upstream to merge an easier to use boot option - be that badmem=addr$size or excludemem=addr$size.

I'm not sure if that is an optimal replacement of BadRAM at all.

Broken memories usually manifest themselves as a column or row in a DIMM that stopped working. So there is a pattern in the memory that is to be excluded, and I'm not wholly sure that combines well with the excludemem mechanism. (I will look into it to be sure.) I hope to know after the weekend if the patterns that I am talking about can be turned into to a cosmetic boot option.

I've also read that people on this list say that it is a waste to throw out a full page if only 5 bytes (say) are actually faulty. Although it is certainly interesting from an academic viewpoint to avoid this, it has never, ever led to complaints. I've been advertising the possibility of using the pages for allocation slabs, and allow all slabs except for those with an error contained, but nobody has ever taken that seriously.

Quoted 1 line

Please send a patch :-)

I've been reluctant to quickly mend things because it could lead to unstable code. The patch that I am presenting is mature code, with the possible exception of the somewhat newer 64-bit code. If this list has a preference for less mature code that is hardly field-tested, I could of course tailor to that.

Cheers,

Rick van Rein

#3 lore raw
Quoted 4 lines · Rick van Rein
Quoted 3 lines

as i said it in another reply to this thread, it would be perfectly acceptable for upstream to merge an easier to use boot option - be that badmem=addr$size or excludemem=addr$size.

Quoted 8 lines

I'm not sure if that is an optimal replacement of BadRAM at all.

Broken memories usually manifest themselves as a column or row in a DIMM that stopped working. So there is a pattern in the memory that is to be excluded, and I'm not wholly sure that combines well with the excludemem mechanism. (I will look into it to be sure.) I hope to know after the weekend if the patterns that I am talking about can be turned into to a cosmetic boot option.

feel free to extend the "excludemem=" mechanism to support the full range of "badram=" configuration methods. As long as you are able to feed it into an e820 table (which is not trivial at all), it's the right thing to do and it would be mainstream acceptable.

and i wouldnt mind the "badmem=" option either - because you already have users of that facility and it's intuitively named as well - as long as it's cleanly fed into the e820 space. I.e. it would all look and behave the same way towards users as the BadMem patch does - with a different internal approach.

Ingo

#4 lore raw
In reply to Rick van Rein
Quoted 8 lines
Quoted 2 lines

Please send a patch :-)

I've been reluctant to quickly mend things because it could lead to unstable code. The patch that I am presenting is mature code, with the possible exception of the somewhat newer 64-bit code. If this list has a preference for less mature code that is hardly field-tested, I could of course tailor to that.

Clean/small/simple is preferable to 'has been stable for 7 years', yes.

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#5 lore raw
In reply to Ingo Molnar
Quoted 10 lines · Ingo Molnar
Quoted 5 lines · * [email protected] <[email protected]> wrote:
Quoted 1 line

What is wrong with mem=exactmap?

probably no ordinary user knows how to use it instead of badram?
http://lists.opensuse.org/opensuse/2007-04/msg00501.html

someone please show us how to use that instead of badram or how this can replace what badram does.

as i said it in another reply to this thread, it would be perfectly acceptable for upstream to merge an easier to use boot option - be that badmem=addr$size or excludemem=addr$size. Please send a patch :-)

It already called:

memmap=addr$size

... and has been implemented for years. Does the badram patch do anything different? (And yes, I agree the $/@/# is ugly.)

-hpa

#6 lore raw
Quoted 7 lines · H. Peter Anvin
Quoted 3 lines

as i said it in another reply to this thread, it would be perfectly acceptable for upstream to merge an easier to use boot option - be that badmem=addr$size or excludemem=addr$size. Please send a patch :-)

It already called:
memmap=addr$size
... and has been implemented for years. Does the badram patch do anything different? (And yes, I agree the $/@/# is ugly.)

I admit that I haven't examined badram too closely, but I think that what it has in addition to what you can get by simple 'memmap=..' is that it allows you to use bitmasks to mask particular address patterns.

Signature · 2 lines
Jiri Kosina
SUSE Labs
#7 lore raw

Am Samstag 08 März 2008 12:13:01 schrieb Jiri Kosina:

Quoted 5 lines · H. Peter Anvin
Quoted 4 lines
Quoted 3 lines

as i said it in another reply to this thread, it would be perfectly acceptable for upstream to merge an easier to use boot option - be that badmem=addr$size or excludemem=addr$size. Please send a patch :-)

Quoted 8 lines
Quoted 4 lines

It already called:
memmap=addr$size
... and has been implemented for years. Does the badram patch do anything different? (And yes, I agree the $/@/# is ugly.)

I admit that I haven't examined badram too closely, but I think that what it has in addition to what you can get by simple 'memmap=..' is that it allows you to use bitmasks to mask particular address patterns.

I had once a bad ram-module and even after heavy search didn't came across memmap or its usage. Together with memtest86 badram= is pretty usable. So for usability's sake i strongly vote for badram= - good name, quite good to use. If you wanna tune on the internal implementation - thats fine ;) .

Best regards
Jan-Simon

#8 lore raw

Am Montag 10 März 2008 11:14:48 schrieben Sie:

Quoted 3 lines

Feel free to improve memmap documentation.
Pavel

BUT ...
to do that, I would need to know already a bit of memmap ?!

This is a Chicken-egg-problem !

And I won't "waste" my time if i've a solution at hand already ?!

Lets do it like this: Show me what i need to know about the usage of memmap and i'll write some doc.

Just shouting "write your own doc" is pointless, as I don't know this part of the kernel myself (yet).

Best regards
Jan-Simon

#9 lore raw
Quoted 11 lines · Jan-Simon Möller

Am Montag 10 März 2008 11:14:48 schrieben Sie:

Quoted 2 lines

Feel free to improve memmap documentation.

BUT ...
to do that, I would need to know already a bit of memmap ?!

This is a Chicken-egg-problem !

And I won't "waste" my time if i've a solution at hand already ?!

...so you waste everyone elses...?

Quoted 5 lines

Lets do it like this: Show me what i need to know about the usage of memmap and i'll write some doc.

Just shouting "write your own doc" is pointless, as I don't know this part of the kernel myself (yet).

Read the thread you are replying to. It was already there.
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#10 lore raw

Am Montag 10 März 2008 12:52:37 schrieb Pavel Machek:

Quoted 12 lines · Jan-Simon Möller
Quoted 9 lines

Am Montag 10 März 2008 11:14:48 schrieben Sie:

Quoted 1 line

Feel free to improve memmap documentation.

BUT ...
to do that, I would need to know already a bit of memmap ?!

This is a Chicken-egg-problem !

And I won't "waste" my time if i've a solution at hand already ?!

...so you waste everyone elses...?

This is no fair answer, Pavel - I already invested my time to find a solution and only found BadRAM at that time. So my impression is that for memmap there's so little doc that no average user is able to use it. This will also prevent users from making "derived" documentation for other use-cases. And again we're back to the chicken-egg ??
You can have the "nicest" solution out there - as long as its either "nasty-to-use" or zero-documented, no one will really use it.

Quoted 7 lines
Quoted 5 lines

Lets do it like this: Show me what i need to know about the usage of memmap and i'll write some doc.

Just shouting "write your own doc" is pointless, as I don't know this part of the kernel myself (yet).

Read the thread you are replying to. It was already there.

I did that and also read kernel-parameters.txt / memory.txt :
But there is _NO_ example line, just the synopsis.
Do you expect all users to know what's e820 table is ? - this is not realistic. Not everybody is an expert in computer science.

Thats why BadRAM is used out there - memtest prints the values and BadRam can use them.

Lets try to get an example and document it:
My starting point would be: i wanna exclude this memory-area

badram=0x18690000,0xffff0000
(which means a whole from 0x18690000 to 0x1869ffff )

what would that be in memmap= -Syntax if i've got 2GB RAM in total ?

Best regards
Jan-Simon

#11 lore raw
Quoted 4 lines · Jan-Simon Möller

badram=0x18690000,0xffff0000
(which means a whole from 0x18690000 to 0x1869ffff )

memmap=0x18690000$64K

or

memmap=0x18690000$0x10000

-hpa

#12 lore raw

Am Montag 10 März 2008 18:20:19 schrieb H. Peter Anvin:

Quoted 11 lines
Quoted 2 lines · Jan-Simon Möller

badram=0x18690000,0xffff0000
(which means a whole from 0x18690000 to 0x1869ffff )

memmap=0x18690000$64K

or

memmap=0x18690000$0x10000

-hpa

Thanks a lot !

I'll reply with a patch for the Documentation and add an example.

Best regards,
Jan-Simon

#13 lore raw
In reply to H. Peter Anvin

What about ...

(quoted diff) +0 -0

b/Documentation/kernel-parameters.txt
index 533e67f..19343e1 100644

Documentation/kernel-parameters.txt +0 -0
@@ -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.

... and/or ...

Documentation/bad-memory.txt new file +27 -0
new file mode 100644
index 0000000..53e817d
@@ -0,0 +1,55 @@
+March 2007
+Jan-Simon Moeller, [email protected]
+
+
+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=<address>$<size>
+
+With the numbers of the example above:
+memmap=0x18690000$64K
+ or
+memmap=0x18690000$0x10000
+
+TODO: Multiple areas to exclude using memmap ?
+

Best regards,
Jan-Simon

#14 lore raw

Am Montag 10 März 2008 19:59:46 schrieb Jan-Simon Möller:

Quoted 1 line

+March 2007

hmmm, change that to 2k8 !

#21 lore raw
In reply to H. Peter Anvin

Hello,

Quoted 8 lines
Quoted 2 lines

badram=0x18690000,0xffff0000
(which means a whole from 0x18690000 to 0x1869ffff )

memmap=0x18690000$64K

or

memmap=0x18690000$0x10000

The true challenge, of course, is to map things like these:

badram=0x18fedcba36,0xfffecff6a

This is a repetitive pattern, and this is why people enjoy the syntactic sugar of BadRAM (which is penciled down from the output of memtest86). It appears to be the prevailing wind in this discussion that the patch must be rewritting to make series of amandments as a long series of memmap would do, and I'll take on that task.

Cheers,
-Rick

#15 lore raw
In reply to Jan-Simon Möller

Hi!

Quoted 1 line

What about ...

Thanks for doing this.

Quoted 10 lines
Documentation/kernel-parameters.txt +0 -0
index 533e67f..19343e1 100644
@@ -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.

Documentation/kernel-parameters.txt

Quoted 4 lines
Documentation/kernel-parameters.txt +4 -0
+                       Example: Exclude memory from 0x18690000-0x1869ffff
+                                memmap=0x18690000$64K
+                                or
+                                memmap=0x18690000$10000

missing 0x after $.

Quoted 63 lines
Documentation/bad-memory.txt new file +27 -0
new file mode 100644
index 0000000..53e817d
@@ -0,0 +1,55 @@
+March 2007
+Jan-Simon Moeller, [email protected]
+
+
+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

Documentation/bad-memory.txt new file +28 -0
+         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=<address>$<size>
+
+With the numbers of the example above:
+memmap=0x18690000$64K
+ or
+memmap=0x18690000$0x10000
+
+TODO: Multiple areas to exclude using memmap ?
+
Quoted 1 line

Actually, I'd include both.. I guess you should fix the 0x, the year, and submit it to akpm (or trivial?).
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#16 lore raw

Patches V2

(quoted diff) +0 -0

b/Documentation/kernel-parameters.txt
index 533e67f..e81f9da 100644

Documentation/kernel-parameters.txt +0 -0
@@ -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$0x10000

meye.*= [HW] Set MotionEye Camera parameters
See Documentation/video4linux/meye.txt.

bad-memory.txt 2008-03-11 01:33:13.885991216 +0100 renamed from dev/null 2007-09-21 21:12:45.000000000 +0200 +27 -0
diff -Naur /dev/null bad-memory.txt
@@ -0,0 +1,55 @@
+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) 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 the 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 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=<address>$<size>
+
+With the numbers of the example above:
+memmap=0x18690000$64K
+ or
+memmap=0x18690000$0x10000
+
+TODO: Multiple areas to exclude using memmap ?
+

#22 lore raw
In reply to H. Peter Anvin

Am Montag 10 März 2008 18:20:19 schrieb H. Peter Anvin:

Quoted 11 lines
Quoted 2 lines · Jan-Simon Möller

badram=0x18690000,0xffff0000
(which means a whole from 0x18690000 to 0x1869ffff )

memmap=0x18690000$64K

or

memmap=0x18690000$0x10000

-hpa

Hmmm reading the kernel-parameters again and again ...

<QUOTE>
memmap=nn[KMG]$ss[KMG]
[KNL,ACPI] Mark specific memory as reserved. Region of memory to be used, from ss to ss+nn.
</QUOTE>

nn would be 0x18690000 or ~409MB
ss would be 0x10000 or 64k

quite big hole ???

I'm not in front of the faulty box, but something is wrong there ...

Best regards,
Jan-Simon

#23 lore raw
Quoted 22 lines · Jan-Simon Möller

Am Montag 10 März 2008 18:20:19 schrieb H. Peter Anvin:

Quoted 10 lines
Quoted 2 lines · Jan-Simon Möller

badram=0x18690000,0xffff0000
(which means a whole from 0x18690000 to 0x1869ffff )

memmap=0x18690000$64K

or

memmap=0x18690000$0x10000

-hpa

Hmmm reading the kernel-parameters again and again ...

<QUOTE>
memmap=nn[KMG]$ss[KMG]
[KNL,ACPI] Mark specific memory as reserved. Region of memory to be used, from ss to ss+nn.
</QUOTE>

Quoted 7 lines

nn would be 0x18690000 or ~409MB
ss would be 0x10000 or 64k

quite big hole ???

I'm not in front of the faulty box, but something is wrong there ...

Sorry, got it backwards.

-hpa

#17 lore raw
In reply to Jan-Simon Möller

Documentation/bad-memory.txt line 8

Quoted 5 lines
Documentation/bad-memory.txt new file +4 -0
+How to deal with bad memory e.g. reported by memtest86+ ?
+#########################################################
+
+There are three possibilities I know of:

I find that sometimes memory problems go away when I simply remove and then re-insert the same DIMMs. Maybe that is the thing to try first.

-Len

Quoted 7 lines

+1) Buy new memory (best!)

Documentation/bad-memory.txt new file +6 -0
+
+2) Try to exchange the memory if you have spare-parts
+
+3) Use BadRAM or memmap
+
+This Howto is about number 3) .
#18 lore raw

Patches V3 with corrected Syntax, tnx hpa !
Changed also text according to idea from Len.

(quoted diff) +0 -0

b/Documentation/kernel-parameters.txt
index 533e67f..f25da88 100644

Documentation/kernel-parameters.txt +0 -0
@@ -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=64K$0x18690000
+                                or
+                                memmap=0x10000$0x18690000

meye.*= [HW] Set MotionEye Camera parameters
See Documentation/video4linux/meye.txt.

bad-memory.txt 2008-03-11 18:44:45.101344820 +0100 renamed from dev/null 2007-09-21 21:12:45.000000000 +0200 +28 -0
@@ -0,0 +1,56 @@
+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 (bad contact?)
+
+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/
+
+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 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=<size>$<address>
+
+With the numbers of the example above:
+memmap=64K$0x18690000
+ or
+memmap=0x10000$0x18690000
+
+TODO: Multiple areas to exclude using memmap ?
+

#19 lore raw

Hi Jan-Simon,

Quoted 22 lines · Jan-Simon Möller

Patches V3 with corrected Syntax, tnx hpa !
Changed also text according to idea from Len.

Documentation/kernel-parameters.txt +0 -0
index 533e67f..f25da88 100644
@@ -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.

Documentation/kernel-parameters.txt +4 -0
+                       Example: Exclude memory from 0x18690000-0x1869ffff
+                                memmap=64K$0x18690000
+                                or
+                                memmap=0x10000$0x18690000
 
        meye.*=         [HW] Set MotionEye Camera parameters
                        See Documentation/video4linux/meye.txt.
Quoted 1 line

Would you mind formatting the patch as described in Documentation/SubmittingPatches? That probably increases the chance of getting it merged.

As far as your patch is concerned, I see broken whitespace, a changelog entry and the signed-off-by is in the wrong place.

Hannes

#20 lore raw

V4 with checkpatch.pl done ...

Start of Documentation for BadRAM/memmap -
Reference: http://lkml.org/lkml/2008/3/2/42

bad-memory.txt 2008-03-11 18:44:45.101344820 +0100 renamed from dev/null 2007-09-21 21:12:45.000000000 +0200 +56 -0
diff -up /dev/null bad-memory.txt
@@ -0,0 +1,56 @@
+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/
+
+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 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.txt for details):
+memmap=<size>$<address>
+
+With the numbers of the example above:
+memmap=64K$0x18690000
+ or
+memmap=0x10000$0x18690000
+
+TODO: Multiple areas to exclude using memmap ?
+

Add example of usage to memmap - evolved from thread about BadRAM inclusion.

Documentation/kernel-parameters.txt +4 -0
index 533e67f..f25da88 100644
@@ -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=64K$0x18690000
+			         or
+			         memmap=0x10000$0x18690000
 
 	meye.*=		[HW] Set MotionEye Camera parameters
 			See Documentation/video4linux/meye.txt.