Messages in this thread | | | Date | Fri, 27 Feb 2009 11:12:25 +0100 | From | Jiri Slaby <> | Subject | Re: i915 X lockup |
| |
On 27.2.2009 11:01, Peter Zijlstra wrote: > would be good to have sysrq-w output
There was nothing but events. So this is rather an intel driver userspace bug?
SysRq : Show Blocked State task PC stack pid father events/1 D 0000000000000000 0 11 2 ffff8801cb231da0 0000000000000046 ffff8801cb231d00 ffffffff80231ef8 0000003800000010 0000000000010180 ffff880028053840 ffff880028057180 ffff8801cb20c790 ffff8801cb20ca38 00000001ca3f90e8 00000000ffff7a0e Call Trace: [<ffffffff80231ef8>] ? dequeue_entity+0x18/0x1a0 [<ffffffff80230b50>] ? dequeue_task+0xb0/0xf0 [<ffffffff805fca2a>] __mutex_lock_slowpath+0xea/0x170 [<ffffffff803f60a0>] ? i915_gem_retire_work_handler+0x0/0x90 [<ffffffff805fc6f6>] mutex_lock+0x26/0x50 [<ffffffff803f60d8>] i915_gem_retire_work_handler+0x38/0x90 [<ffffffff80250792>] worker_thread+0x172/0x250 [<ffffffff80254da0>] ? autoremove_wake_function+0x0/0x40 [<ffffffff80250620>] ? worker_thread+0x0/0x250 [<ffffffff802549be>] kthread+0x9e/0xb0 [<ffffffff8020d3da>] child_rip+0xa/0x20 [<ffffffff80254920>] ? kthread+0x0/0xb0 [<ffffffff8020d3d0>] ? child_rip+0x0/0x20
| |