On Wed, May 18, 2005 at 03:53:37PM -0500, Gabriel Sechan wrote: > > > >From: Lan Barnes <[EMAIL PROTECTED]> > > > >Close to 100% -- perhaps all -- of the Linux system lock ups I've > >experienced (that weren't caused by a stupid compile on my part) have > >been from X. Over 80% (seat of the pants stats, of course) of these were > >resolvable by logging in over a network or serial port and killing X -- > >the kernel was cookin' along just fine. > > > >When we say "Linux," we usually mean the whole conglomerate, so X is > >part of it. But the kernel itself is close to bullet proof, which is > >really nice for servers. > > > > I actually managed one at work the other day. I still blame X at least > partially. I kicked the mouse cord out and lost all IO from the keyboard > and mouse (even after replugging). Unfortunately it wouldn't respond to > ssh either. I was forced to hard reboot. > > Gabe
Oh, I've had em, too. On this FC3 HPVectra VE at work, about 1 in 20 times startx lobotomizes it. No ping from the network, nada. The monitor light blinks and I have to power down. One of the Allen brothers (I can't keep em straight, which probably means I pay equal attention to their acumen) suggested that the video card is chancy to initialize. I live with it ... -- Lan Barnes [EMAIL PROTECTED] Linux Guy, SCM Specialist 858-354-0616 -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
