On Sun, 06 Feb 2005 13:45:47 -0500, Michel Dänzer <[EMAIL PROTECTED]> wrote: > Does it also happen without either or all of the options in the radeon > device section?
I just removed the AGPFastWrite and DynamicClocks options. The crashes still happen though. First I played some gish. I was able to play it for 15 minutes or so, after that I got a black screen with vertical lines. See http://www.stellingwerff.com/crash.jpg for a shot I took. After that I tried some Neverball for 15 minutes, but no crashes. Then, I tried Enemy Territory . I never actually got into the game, it would keep crashing. But unlike before, it would not crash the whole system. I was able to log in with ssh, where I noticed the following: X froze completely et.x86 was using 100% CPU A little black square is drawn over the panel (I am running ET in windowed mode). I am able to kill et.x86, but as a result the 'X' process now starts using 100% CPU. I tried killing X, but that results in nothing. I did notice that X now uses 0 VIRT, 0 RES and 0 SHR memory. The state of the X process is now 'R'. dmesg shows nothing, neither does Xorg.0.log. So I issue the 'reboot' command, and as a result I'm left with a completely unresponsive system. Network connections are dead, everything is. Have to hard-reboot. Hopefully this sounds familiar to someone... ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
