On Fri, 2003-10-10 at 11:29, Helge Hafting wrote: > > It hangs at a black screen now, I don't get to play around > with the cursor for a few seconds first. > I mounted /var synchronously so I got a logfile. It > is attached as X-dri-log.
I don't see anything suspicious, this looks like a perfectly normal log. Does disabling the DRI make a difference? If yes, what about Option "ForcePCIMode"? If neither make a difference, what about disabling all acceleration? > >>Glxgears still hangs if I run it. The hang is not as > >>bad as the xserver hang, because I can use sysrq+S+U+B > >>to reboot without messing up filesystems. > > > > > > Can you also try logging in remotely and killing glxgears? > > > I haven't done that yet, but it seems like it could work. > I used sysrq+K instead (kill all programs on that virtual console) > That left the framebuffer in a unreadable state, but I was able > to log in as root and remove the X lockfile. > > Attempting to restart X led to a "no signal" warning on > my screen, so recovering the console by restarting X didn't work. > "shutdown -r now" did the trick though. So apparently the chip is in a rather bad state after it happens. I wonder if it could be a hardware problem to boot. Have you tried other OSs on this machine? -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
