bad_memory.txt 1.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546
  1. March 2008
  2. Jan-Simon Moeller, dl9pf@gmx.de
  3. How to deal with bad memory e.g. reported by memtest86+ ?
  4. #########################################################
  5. There are three possibilities I know of:
  6. 1) Reinsert/swap the memory modules
  7. 2) Buy new modules (best!) or try to exchange the memory
  8. if you have spare-parts
  9. 3) Use BadRAM or memmap
  10. This Howto is about number 3) .
  11. BadRAM
  12. ######
  13. BadRAM is the actively developed and available as kernel-patch
  14. here: http://rick.vanrein.org/linux/badram/
  15. For more details see the BadRAM documentation.
  16. memmap
  17. ######
  18. memmap is already in the kernel and usable as kernel-parameter at
  19. boot-time. Its syntax is slightly strange and you may need to
  20. calculate the values by yourself!
  21. Syntax to exclude a memory area (see kernel-parameters.txt for details):
  22. memmap=<size>$<address>
  23. Example: memtest86+ reported here errors at address 0x18691458, 0x18698424 and
  24. some others. All had 0x1869xxxx in common, so I chose a pattern of
  25. 0x18690000,0xffff0000.
  26. With the numbers of the example above:
  27. memmap=64K$0x18690000
  28. or
  29. memmap=0x10000$0x18690000