From: <bug...@an...> - 2006-09-22 16:38:31
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8397 Summary: r430 infinite loop under radeon_do_cp_idle Product: DRI Version: XOrg CVS Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: DRM modules AssignedTo: dri...@li... ReportedBy: ari...@gm... The box contains a Radeon X800 XL (PCIE), an Athlon64, and a VIA VT8251/K8M800/whatchamacallit motherboard. It's running a recent Gentoo Linux, a vanilla 2.6.18 kernel (aside drm), X.org 7.1.1 with the corresponding DRI, plus libdrm and drm modules pulled from git today. Starting Xorg (just the server, no clients) causes CPU use to go to 100% in system according to top. The system can otherwise still be used with ssh, but the X server can't be killed even with kill -9. Here's some <a href="http://www.student.oulu.fi/~arirahik/xorg_problem/strace.txt.gz">strace</a> (65k gzipped) and <a href="http://www.student.oulu.fi/~arirahik/xorg_problem/gdb.txt">gdb</a>(10k) output about the process. strace indicates that we're stuck trying to use ioctl 0x6444 on /dev/dri/card0, getting -EBUSY every time, and gdb indicates that we're under some XAA code that's helping with cursor handling. I defined RADEON_FIFO_DEBUG 1 in radeon_cp.c, modprobed drm.ko with debug=1, and <a href="http://www.student.oulu.fi/~arirahik/xorg_problem/kmsg.txt">captured some /proc/kmsg output</a>(35k) from starting Xorg. It's pretty opaque to me, though, so I don't know how to go on from here. I've tried various settings in xorg.conf: SWCursor True, BusType PCI, BusType PCIE, and AccelMethod EXA. Apparently the same bug (I only checked that top showed 100% CPU usage in system) manifested in every case, though with EXA it took until I actually spawned a window, while with XAA it happens soon after the X server has started up. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |