Matthew Gibson wrote: > I finally managed to network and run ssh, and here is some of what I > found. > This is while running xscreensaver sundancer2. > > > When my system was crashed, top displayed: > Xorg was using about 45% of my cpu, and a normal amount of memory. > Sundancer2 was using about 45% of my cpu, and a normal amount of memory > sshd was using about .5% CPU > mpd (music player deamon, which was playing music) was using about 4% > of CPU > top was using about 1% of CPU. > > I found that I couldn't kill either sundancer or Xorg unless I used > the -s KILL signal. dmesg showed no additional messages when my > computer was crashed, and no messages had been sent to Xorg.0.log > > I could still run stuff through ssh fine, just Xorg and the offending > program were hung up. No output was made to the screen, and no > keyboard input was received. (A But I could still kill programs and > start (non-graphical) programs in ssh.) > I could kill sundancer2, and then Xorg sat on 95 % of my processor, > still accomplishing nothing. > > I then tried killing Xorg. It shutsdown, my screen flashed blank, and > then top showed it started up again, under a new PID. Again, it sat on > 95 % of my resources, and was still frozen.
Is it better with xserver-xorg-video-sis 1:0.9.3-6 from unstable? (or at least the one from testing) Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
