Am Freitag, den 17.02.2006, 21:02 +0100 schrieb Markus Dahms: > Hi there, > > I have some stability problems with radeon cards in my system. Doing > something involving 3D graphics (e.g. Blender) after a while > (often within minutes) the screen locks up (mouse is still movable) > and the Xorg process goes up to 99% CPU. To use the screen again I > have to reboot. > > From the GDB backtrace of the X server I suspect it's a kernel > module problem: > > #0 0xa7f11cc4 in ioctl () from /lib/tls/libc.so.6 > #1 0x080a2890 in xf86ioctl () > #2 0xa7a92672 in drmCommandNone () from > /usr/X11R6/lib/modules/linux/libdrm.so > #3 0xa7a5181a in RADEONWaitForIdleCP () from > /usr/X11R6/lib/modules/drivers/radeon_drv.so > #4 0xa786758d in XAAInit () from /usr/X11R6/lib/modules/libxaa.so > #5 0xa78b19d7 in xf86InitCursor () from /usr/X11R6/lib/modules/libramdac.so > #6 0x08089e03 in xf86Wakeup () > #7 0x080ca3f3 in WakeupHandler () > #8 0x080e8731 in WaitForSomething () > #9 0x080c9970 in Dispatch () > #10 0x080d6765 in main () > > (at least the upper 4 calls are always the same, the rest differs) >
The backtrace only tells you that the engine stopped processing commands. But it doesn't tell you why. Finding the exact trigger can be very hard. > Does somebody have a hint? I don't want to believe it's a broken > mainboard or something... > > Software: > * Debian Etch (testing) > * Xorg 6.9.0 (same with 6.8.0) > * Linux Kernel 2.6.16-rc2+e (GIT, same with older kernels) > * radeon.ko from kernel > > Hardware: > * 2 x P3 1000MHz on Asus CUV266-D, 1 GB RAM > * Radeon 9250, same problem with Radeon 7500 > > Everything is done with AGP 1x mode, as higher rates increase the > chance to crash this system (even in 2D mode). If you have AGPFastWrites enabled, do disable them. Did you set any other funny options in the configuration file? It may also be related to AGP writeback of engine status. It doesn't work reliably with some AGP bridges and leads to the symptoms described above. In that case the engine is finished processing commands and ready for new ones, but the driver never knows about it. It's pretty simple to disable this feature in the radeon.ko source. Search for "Writeback" in radeon_cp.c. There is a test whether writeback works. At the end of the test just set dev_priv->writeback_works = 0; unconditionally. > I don't think it's a heat problem as there are enough fans and the > cooler on the graphics card stays cold. > > Markus Hope this helps, Felix -- | Felix Kühling <[EMAIL PROTECTED]> http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
