diff options
author | Jonathan Herman <hermanjl@cs.unc.edu> | 2013-01-22 10:38:37 -0500 |
---|---|---|
committer | Jonathan Herman <hermanjl@cs.unc.edu> | 2013-01-22 10:38:37 -0500 |
commit | fcc9d2e5a6c89d22b8b773a64fb4ad21ac318446 (patch) | |
tree | a57612d1888735a2ec7972891b68c1ac5ec8faea /Documentation/memory.txt | |
parent | 8dea78da5cee153b8af9c07a2745f6c55057fe12 (diff) |
Diffstat (limited to 'Documentation/memory.txt')
-rw-r--r-- | Documentation/memory.txt | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/Documentation/memory.txt b/Documentation/memory.txt new file mode 100644 index 00000000000..802efe58647 --- /dev/null +++ b/Documentation/memory.txt | |||
@@ -0,0 +1,33 @@ | |||
1 | There are several classic problems related to memory on Linux | ||
2 | systems. | ||
3 | |||
4 | 1) There are some motherboards that will not cache above | ||
5 | a certain quantity of memory. If you have one of these | ||
6 | motherboards, your system will be SLOWER, not faster | ||
7 | as you add more memory. Consider exchanging your | ||
8 | motherboard. | ||
9 | |||
10 | All of these problems can be addressed with the "mem=XXXM" boot option | ||
11 | (where XXX is the size of RAM to use in megabytes). | ||
12 | It can also tell Linux to use less memory than is actually installed. | ||
13 | If you use "mem=" on a machine with PCI, consider using "memmap=" to avoid | ||
14 | physical address space collisions. | ||
15 | |||
16 | See the documentation of your boot loader (LILO, grub, loadlin, etc.) about | ||
17 | how to pass options to the kernel. | ||
18 | |||
19 | There are other memory problems which Linux cannot deal with. Random | ||
20 | corruption of memory is usually a sign of serious hardware trouble. | ||
21 | Try: | ||
22 | |||
23 | * Reducing memory settings in the BIOS to the most conservative | ||
24 | timings. | ||
25 | |||
26 | * Adding a cooling fan. | ||
27 | |||
28 | * Not overclocking your CPU. | ||
29 | |||
30 | * Having the memory tested in a memory tester or exchanged | ||
31 | with the vendor. Consider testing it with memtest86 yourself. | ||
32 | |||
33 | * Exchanging your CPU, cache, or motherboard for one that works. | ||