OK I've been running the above intrepid debs since dec 29, and just now I got a look-up again, this time when logging in remote via vnc from home. The T61 at work is up running and locked by the screen-saver. The screen saver is running without any "effect" i.e. it is black. I first typed my passwd wrong and when I retyped the passwd and hit "enter" (or pressed "OK" don't remember which) X locked up. I logged in via ssh and saw the usual symptom: X process running at 100% (on one of the cores).
This time with no output in Xorg.0.log (at least not yet after about 20 minutes), but it is clearly the same problem as before. Nothing in syslog or messages. Compiz is enabled.
I vaguely recall that at least a couple of lock-ups have been associated with logging in from the screen-saver.
Attaching lspci output again.
Is there any other tests I can do while in lock-up state now during the week-end (I have to reboot on monday)?
OK I've been running the above intrepid debs since dec 29, and just now I got a look-up again, this time when logging in remote via vnc from home. The T61 at work is up running and locked by the screen-saver. The screen saver is running without any "effect" i.e. it is black. I first typed my passwd wrong and when I retyped the passwd and hit "enter" (or pressed "OK" don't remember which) X locked up. I logged in via ssh and saw the usual symptom: X process running at 100% (on one of the cores).
This time with no output in Xorg.0.log (at least not yet after about 20 minutes), but it is clearly the same problem as before. Nothing in syslog or messages. Compiz is enabled.
I vaguely recall that at least a couple of lock-ups have been associated with logging in from the screen-saver.
Attaching lspci output again.
Is there any other tests I can do while in lock-up state now during the week-end (I have to reboot on monday)?