As far as the git logs are concerned I found this one related to some IB fixes of radeon. It's dated by Jul 2012, but correspond to the next branch. Does it mean that it is tested for some time before get to the mainline and stable?
commit b68bdc1bbab743e2911b40c27b91a0a8e641cfb7 Merge: 2993555 f312f09 Author: Dave Airlie <[email protected]> Date: Thu Jul 19 21:20:54 2012 -0400 Merge branch 'next' of git://people.freedesktop.org/~deathsimple/linux into drm-next This contains all the radeon documentation rebased on top of the ib fixes. * 'next' of git://people.freedesktop.org/~deathsimple/linux: drm/radeon: fix SS setup for DCPLL drm/radeon: fix up pll selection on DCE5/6 drm/radeon: start to document evergreen.c drm/radeon: start to document the functions r100.c drm/radeon: document VM functions in radeon_gart.c (v3) drm/radeon: document non-VM functions in radeon_gart.c (v2) drm/radeon: document radeon_ring.c (v4) drm/radeon: document radeon_fence.c (v2) drm/radeon: document radeon_asic.c drm/radeon: document radeon_irq_kms.c drm/radeon: document radeon_kms.c drm/radeon: document radeon_device.c (v2) drm/radeon: add rptr save support for r1xx-r5xx drm/radeon: update rptr saving logic for memory buffers drm/radeon: remove radeon_ring_index() drm/radeon: update ib_execute for SI (v2) drm/radeon: fix const IB handling v2 drm/radeon: let sa manager block for fences to wait for v2 drm/radeon: return an error if there is nothing to wait for -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069249 Title: [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(13) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069249/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
