As an apology for making a bit of "noise" today, here is the bugfix
for the "Memory size detected wrong on Compaq Proliant/1600" bug :)
It was to do with setup_arch() incorrectly initializing max_pfn if there
is a range with zero size.
http://www.ocston.org/~tigran/patches/proliant-2.3.33.patch
Btw, running on a machine with detected 900M (real 64M) had a side effect
of having very large page cache hashtable configured and I liked the
performance thereof - I will tune it up manually for some of my nodes.
Regards,
------
Tigran A. Aivazian | http://www.sco.com
Escalations Research Group | tel: +44-(0)1923-813796
Santa Cruz Operation Ltd | http://www.ocston.org/~tigran
--- linux/arch/i386/kernel/setup.c Wed Dec 8 07:01:40 1999
+++ ta/arch/i386/kernel/setup.c Wed Dec 15 15:41:06 1999
@@ -594,7 +594,7 @@
for (i = 0; i < e820.nr_map; i++) {
unsigned long curr_pfn;
/* RAM? */
- if (e820.map[i].type != E820_RAM)
+ if (e820.map[i].type != E820_RAM || (int)e820.map[i].size == 0)
continue;
curr_pfn = PFN_DOWN(e820.map[i].addr + e820.map[i].size);
if (curr_pfn > max_pfn)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/