>> That happened to me occasionally (1x or 2x a week) under X11R6 >> 6.8.2, which is why I decided to make the move to R7 last week. >> For what it's worth, it has not locked up on me yet... inlcuding >> when I run Mesa/DRI applications, which seemed to be the most >> frequent cause of lockups under R6. >> >> Is the computer standalone, or do you have another computer on a >> LAN you can use to telnet in and kill all X-related processes? If >> you can, that would at least tell you if the system itself is >> locked up or just the keyboard/console. > >I am unable to telnet in. It would seem the entire machine has become >unresponsive.
Sorry, I haven't been following this thread. But I just saw this. I had a problem with lockups when firefox caused an OOM crash. Turns out Linux was alive and well, but the console was just hosed. What I did was create a script that ran startx, then slept for 15s, then looped back. If there was no lockup, then ^C would terminate my "Groundhog Day" script. If there'd been a crash, in 15s X would be restarted. It wouldn't be able to recover to usability, but it WOULD enable me to feed in a CTL-ALT-DEL, which would shutdown Linux gracefully--better than punching the RESET button! Crude, but better than a lot of fsck repair runs! Paul Rogers ([EMAIL PROTECTED]) http://www.xprt.net/~pgrogers/ http://www.geocities.com/paulgrogers/ Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
