From 849369d6c66d3054688672f97d31fceb8e8230fb Mon Sep 17 00:00:00 2001 From: root Date: Fri, 25 Dec 2015 04:40:36 +0000 Subject: initial_commit --- Documentation/memory.txt | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 Documentation/memory.txt (limited to 'Documentation/memory.txt') diff --git a/Documentation/memory.txt b/Documentation/memory.txt new file mode 100644 index 00000000..802efe58 --- /dev/null +++ b/Documentation/memory.txt @@ -0,0 +1,33 @@ +There are several classic problems related to memory on Linux +systems. + + 1) There are some motherboards that will not cache above + a certain quantity of memory. If you have one of these + motherboards, your system will be SLOWER, not faster + as you add more memory. Consider exchanging your + motherboard. + +All of these problems can be addressed with the "mem=XXXM" boot option +(where XXX is the size of RAM to use in megabytes). +It can also tell Linux to use less memory than is actually installed. +If you use "mem=" on a machine with PCI, consider using "memmap=" to avoid +physical address space collisions. + +See the documentation of your boot loader (LILO, grub, loadlin, etc.) about +how to pass options to the kernel. + +There are other memory problems which Linux cannot deal with. Random +corruption of memory is usually a sign of serious hardware trouble. +Try: + + * Reducing memory settings in the BIOS to the most conservative + timings. + + * Adding a cooling fan. + + * Not overclocking your CPU. + + * Having the memory tested in a memory tester or exchanged + with the vendor. Consider testing it with memtest86 yourself. + + * Exchanging your CPU, cache, or motherboard for one that works. -- cgit v1.2.3