I just ran into this again (but not with the updated intel driver and mesa packages; I have now installed them and will see what changes). Having rebooted, I examined the logs and tried to make it crash again, but without success.
I now think that this is what is happening: 1. the xserver dies 2. gdm starts a new xserver. logs are rotated. 3. the hardware was screwed in the crash, and the new xserver causes the system to lock up. 4. after rebooting, gdm starts the xserver and logs are rotated a second time So the log I originally posted is from the second xserver invocation that causes the system to lock up, not from the first xserver that originally screwed the hardware up. This time I was unable to switch to tty1 to do anything. Hopefully next time I'll have another system around to shell in and examine the situation. I will also try to remember to boot up in single user mode to try to recover the logs of the original xserver. -- Sam Morris <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]