This is not SuSE-specific, although one affected machine is (now) running SuSE 6.2. The other two machines are running Debian. We have 3 Dell computers -- each with a Celeron 433 proc and 128MB of RAM -- that are supposed to be used as development boxes. The two Debian boxes are running kernel 2.2.13 and the SuSE box runs 2.2.14. Being they each have 128MB of RAM there is an "append" line in lilo.conf: append="mem=128M" Each of the three machines choke when booted and the kernel panics. It looks almost like a GPF, with stack and register crap spewed all over the screen. Oddly enough, if the append line is changed to, say, append="mem=126M" all three machines boot fine. The Dells are the same model, purchased at the same time from the same place (from Dell directly). It is possible, although I feel very unlikely, that the machines are victims of a bad batch of RAM. Any ideas what could be causing the machines to choke, other than the possibility of bad RAM? Regards, kw /* ** Keith Warno ** Developer & Sys Admin ** http://www.HaggleWare.com/ */ -- 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/