On Sam, 2002-11-16 at 14:45, Igor Filippov wrote: > Here are my two cents: > > Linux 7.1 on > 1.3 GHz Athlon > ECS K7S5A Motherboard > 1024 mb ram > Matrox G450 > > I have been experiencing the exact same lockups. I have upgraded the kernel > to 2.4.19 and installed the XFree4.2 from the sources. Everything was > recompiled for athlon. Everything seemed ok for a while, but then it locked > up again just yesterday when I was logging in. Right after the xdm login > screen disappeared, but before the desktop had a chance to appear... The > root partition ended up being badly damaged, I am assuming as a result of > the hard reset. The lockup must've happened at some critical point? > > Actually, I did noticed that usually there is a whole lot more filesystem > damage in the result of the X lockup than, for example, when the computer > goes off because of a power blackout. It happened to me several times (I > don't have the UPS). In fact, there is this one error that I only get after > the lockup. I can't remember exactly what it says, but it's something along > the lines that several files (not links to files) end up pointing at the > same cluster on the hard drive, so it asks if I want to duplicate the > cluster. Those would usually be the files that I had open at the time of > lockup...
I doubt X in particular but rather system load in general influences the severity of a crash. If you don't use a journalling filesystem already, that might be a good idea. -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
