http://bugs.freedesktop.org/show_bug.cgi?id=16549
--- Comment #13 from Michel Dänzer <[email protected]> 2009-01-25 02:45:40 PST --- (In reply to comment #12) > Using libdrm-2.3.0, mesa-6.5.2 and xserver-1.3 -> DRI works What about the problem you reported originally? > Nothing in the locking code in libdrm/xf86drm.h (DRM_CAS etc) has changed from > libdrm 2.3.0 to 2.4.4. Is that using the same kernel / DRM modules? If so, you should be able to isolate the userspace change which broke things for you. Anyway, looking at the debugging output: [drm:drm_lock] 3 (pid 3454) requests lock (0x00000001), flags = 0x00000000 [drm:drm_lock] 3 has lock [drm:drm_ioctl] pid=3454, cmd=0x80206450, nr=0x50, dev 0xe200, auth=1 [drm:radeon_cp_cmdbuf] *ERROR* radeon_cp_cmdbuf called without lock held, held 0 owner fffffc00f2a57c00 fffffc00f2a57c00 The first two lines indicate that drm_lock_take() succeeds for glxgears' context, but then LOCK_TEST_WITH_RETURN() fails in radeon_cp_cmdbuf(). There does seem to be an inconsistency. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
