Comment 35 for bug 365994

Reopening for the second time, sorry. Actually, I experienced it again with kernel 2.6.30rc6 and driver 2.7.99.1+git20090519. The output of dmesg is exactly the same as that of the first dump linked here:
[ 1320.512119] Call Trace:
[ 1320.512137] [<c02d296e>] ? rb_erase+0xbe/0x130
[ 1320.512150] [<c0512ed4>] __mutex_lock_slowpath+0xa4/0x100
[ 1320.512159] [<c0512c10>] mutex_lock+0x20/0x40
[ 1320.512197] [<e0a4d688>] i915_gem_retire_work_handler+0x28/0x70 [i915]
[ 1320.512209] [<c014c8bd>] run_workqueue+0x6d/0x130
[ 1320.512238] [<e0a4d660>] ? i915_gem_retire_work_handler+0x0/0x70 [i915]
[ 1320.512248] [<c014cf48>] worker_thread+0x88/0xe0
[ 1320.512259] [<c01505a0>] ? autoremove_wake_function+0x0/0x40
[ 1320.512268] [<c014cec0>] ? worker_thread+0x0/0xe0
[ 1320.512277] [<c01501fc>] kthread+0x4c/0x80
[ 1320.512284] [<c01501b0>] ? kthread+0x0/0x80
[ 1320.512294] [<c01039c7>] kernel_thread_helper+0x7/0x10

Only difference: mouse cursor was frozen too this time (not sure those data are really meaningful).

See http://launchpadlibrarian.net/27031541/dri_debug.tgz for the full dump.