Bad Memory Blocks Exclusion in Linux Operating System

  • Tomasz Surmacz
  • Bartosz Zawistowski
Conference paper
Part of the Advances in Intelligent and Soft Computing book series (AINSC, volume 97)


Memory failures are quite common in todays technology. When they occur, the whole memory bank has to be replaced, even if only few bytes of memory are faulty. With increasing sizes of memory chips the urge not to waste these ‘not quite properly working’ pieces of equipment becomes bigger and bigger. Operating systems such as Linux already provide mechanisms for memory management which could be utilized to avoid allocating bad memory blocks which have been identified earlier, allowing for a failure-free software operation despite hardware problems. The paper describes problems of detecting memory failures and OS mechanisms that can be used for bad block exclusion. It proposes modifications to Linux kernel allowing a software solution to hardware failures.


Memory Management Soft Error Memory Bank Static Random Access Memory Page Size 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Biswas, S., Metodi, T., Chong, F., Kastner, R.: A pageable, defect-tolerant nanoscale memory system. In: IEEE International Symposium on Nanoscale Architectures, NANOSARCH 2007, pp. 85–92 (2007), doi:10.1109/NANOARCH.2007.4400862Google Scholar
  2. 2.
    De Jonge, J.H., Smeulders, A.J.: Moving Inversions Test Pattern is Thorough, Yet Speedy. International Computer Design (1976)Google Scholar
  3. 3.
    Demeulemeester, S.: Memtest86, an Advanced Memory Diagnostic Tool (2010),
  4. 4.
    Elkind, S., Siewiorek, D.: Reliability and performance of error-correcting memory and register arrays. IEEE Transactions on Computers C-29(10), 920–927 (1980), doi:10.1109/TC.1980.1675475Google Scholar
  5. 5.
    Elm, C., Klein, M., Tavangarian, D.: Automatic On-line Memory Tests in Workstations. In: Records of the IEEE International Workshop on Memory Technology, Design and Testing (1994)Google Scholar
  6. 6.
    Gu, W., Kalbarczyk, Z., Ravishankar, Iyer, K., Yang, Z.: Characterization of Linux kernel behavior under errors. In: Proceedings of 2003 International Conference on Dependable Systems and Networks, pp. 459–468 (2003), doi:10.1109/DSN.2003.1209956Google Scholar
  7. 7.
    Hamdioui, S.: Testing static random access memories: defects, fault models, and test pattern. Kluwer Academic Publishers, Dordrecht (2004)Google Scholar
  8. 8.
    Intel Corporation IA-32 Intel Architecture Software Developer’s Manual. In: System Programming Guide, vol. 3 (2009),
  9. 9.
    Kozierok, C.: The PC Guide – Memory Errors, Detection and Correction (2001)Google Scholar
  10. 10.
    Maestro, J., Reviriego, P.: Selection of the optimal memory configuration in a system affected by soft errors. IEEE Transactions on Device and Materials Reliability 9(3), 403–411 (2009), doi:10.1109/TDMR.2009.2023081CrossRefGoogle Scholar
  11. 11.
    Messer, A., Bernadat, P., Fu, G., Chen, D., Dimitrijevic, Z., Lie, D., Mannaru, D., Riska, A., Milojicic, D.: Susceptibility of commodity systems and software to memory soft errors. IEEE Transactions on Computers 53(12), 1557–1568 (2004), doi:10.1109/TC.2004.119CrossRefGoogle Scholar
  12. 12.
    Silberschats, A., Peterson, J.L., Galvin, P.B.: Operating System Concepts. Addison-Wesley Publishing Company, Inc., Reading (1991)Google Scholar
  13. 13.
    Swift, W.: Memory errors: roll the dice! IEEE Antennas and Propagation Magazine 38(6), 124–125 (1996), doi:10.1109/MAP.1996.556530CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Tomasz Surmacz
    • 1
  • Bartosz Zawistowski
    • 2
  1. 1.Institute of Computers, Control and RoboticsWroclaw University of TechnologyPoland
  2. 2.Wroclaw University of TechnologyPoland

Personalised recommendations