Brad Shelton wrote:
On Wed, Feb 09, 2000 at 05:43:05PM -0500, Paul W. Abrahams wrote:
"Paul W. Abrahams" wrote earlier:
Here is the text of a message I sent to the maintainter of the ext2fs filesystem. I think it would be of interest to this group, especially if anyone here has had a similar experience.
1. Summary: Ext2fx implosion when RAM added
I won't repeat the previous message again, but I've run a memory tester (memtest86) and think it's unlikely the memory is at fault. And all the surface testing I've done makes it unlikely the disk is at fault.>
Hmmm. Did I miss it, or did you tell us you weren't using the append="MEM=128M" lilo boot statement?
Just curious to see if that's involved in your predicament.
Very interesting. I never would have thought to look in the Boot-Prompt Howto for something relevant to the problem, and the MEM parameter isn't even mentioned in Werner Almsberger's Lilo writeup. But according to the description in the Boot-Prompt Howto, the BIOS isn't able to report memory sizes greater than 64MB, so Linux needs to be told if more memory is present. I suspect there was some nonuniform treatment of memory access going on. As it happens, I rebuilt the kernel, and after doing that (though with the same version) the problem went away. Of course I would have liked to compare the current kernel configuration with the configuration when I was getting the error, but /usr/src/linux was in the partition that got clobbered. I'm going to start another thread on this subject to see what experiences others have had. Paul Abrahams -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/