Comment 21 for bug 487185

Description of problem:

My system runs into a soft lockup after some time, seemingly at random, but it could be that it only happens after ~30 min of idling.

The display goes blank, the monitor says "No signal", but I can still ssh into the machine. I am not able to wake it up by ctrl-alt-f2 or the like.

"init 3" as root does not work, and I can't seem to kill any running programs (over ssh, as root - the shell never returns)

In /var/log/messages I get:

INFO: task events/0:9 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
events/0 D ffff88012de02024 0 9 2
 ffff88012fb31d60 0000000000000046 0000000000000001 ffffffffa04774eb
 ffff88012fb31cf0 ffffffff81046bf0 ffff88012fb31cf0 000000008604ee9e
 ffff88012fb060e8 000000000000e2e8 ffff88012fb060e8 0000000000012cc0
Call Trace:
 [<ffffffffa04774eb>] ? mantis_query_rc+0x0/0x89 [mantis]
 [<ffffffff81046bf0>] ? dequeue_entity+0x2f/0x1e8
 [<ffffffff810477d8>] ? dequeue_task_fair+0x81/0xa0
 [<ffffffff810108f2>] ? __switch_to+0x19c/0x23c
 [<ffffffff814970e7>] __mutex_lock_common+0x12c/0x1a8
 [<ffffffff8149718f>] __mutex_lock_slowpath+0x2c/0x42
 [<ffffffff81497366>] mutex_lock+0x43/0x71
 [<ffffffffa00682ad>] i915_gem_retire_work_handler+0x40/0x96 [i915]
 [<ffffffffa006826d>] ? i915_gem_retire_work_handler+0x0/0x96 [i915]
 [<ffffffff8106b8b9>] worker_thread+0x1ab/0x25d
 [<ffffffff81070b57>] ? autoremove_wake_function+0x0/0x5f
 [<ffffffff8106b70e>] ? worker_thread+0x0/0x25d
 [<ffffffff81070665>] kthread+0x6d/0xae
 [<ffffffff8101313a>] child_rip+0xa/0x20
 [<ffffffff81012afd>] ? restore_args+0x0/0x30
 [<ffffffff810705f8>] ? kthread+0x0/0xae
 [<ffffffff81013130>] ? child_rip+0x0/0x20
INFO: task events/0:9 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
events/0 D ffff88012de02024 0 9 2
 ffff88012fb31d60 0000000000000046 0000000000000001 ffffffffa04774eb
 ffff88012fb31cf0 ffffffff81046bf0 ffff88012fb31cf0 000000008604ee9e
 ffff88012fb060e8 000000000000e2e8 ffff88012fb060e8 0000000000012cc0
Call Trace:
 [<ffffffffa04774eb>] ? mantis_query_rc+0x0/0x89 [mantis]
 [<ffffffff81046bf0>] ? dequeue_entity+0x2f/0x1e8
 [<ffffffff810477d8>] ? dequeue_task_fair+0x81/0xa0
 [<ffffffff810108f2>] ? __switch_to+0x19c/0x23c
 [<ffffffff814970e7>] __mutex_lock_common+0x12c/0x1a8
 [<ffffffff8149718f>] __mutex_lock_slowpath+0x2c/0x42
 [<ffffffff81497366>] mutex_lock+0x43/0x71
 [<ffffffffa00682ad>] i915_gem_retire_work_handler+0x40/0x96 [i915]
 [<ffffffffa006826d>] ? i915_gem_retire_work_handler+0x0/0x96 [i915]
 [<ffffffff8106b8b9>] worker_thread+0x1ab/0x25d
 [<ffffffff81070b57>] ? autoremove_wake_function+0x0/0x5f
 [<ffffffff8106b70e>] ? worker_thread+0x0/0x25d
 [<ffffffff81070665>] kthread+0x6d/0xae
 [<ffffffff8101313a>] child_rip+0xa/0x20
 [<ffffffff81012afd>] ? restore_args+0x0/0x30
 [<ffffffff810705f8>] ? kthread+0x0/0xae
 [<ffffffff81013130>] ? child_rip+0x0/0x20
INFO: task events/0:9 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
events/0 D ffff88012de02024 0 9 2
 ffff88012fb31d60 0000000000000046 0000000000000001 ffffffffa04774eb
 ffff88012fb31cf0 ffffffff81046bf0 ffff88012fb31cf0 000000008604ee9e
 ffff88012fb060e8 000000000000e2e8 ffff88012fb060e8 0000000000012cc0
Call Trace:
 [<ffffffffa04774eb>] ? mantis_query_rc+0x0/0x89 [mantis]
 [<ffffffff81046bf0>] ? dequeue_entity+0x2f/0x1e8
 [<ffffffff810477d8>] ? dequeue_task_fair+0x81/0xa0
 [<ffffffff810108f2>] ? __switch_to+0x19c/0x23c
 [<ffffffff814970e7>] __mutex_lock_common+0x12c/0x1a8
 [<ffffffff8149718f>] __mutex_lock_slowpath+0x2c/0x42
 [<ffffffff81497366>] mutex_lock+0x43/0x71
 [<ffffffffa00682ad>] i915_gem_retire_work_handler+0x40/0x96 [i915]
 [<ffffffffa006826d>] ? i915_gem_retire_work_handler+0x0/0x96 [i915]
 [<ffffffff8106b8b9>] worker_thread+0x1ab/0x25d
 [<ffffffff81070b57>] ? autoremove_wake_function+0x0/0x5f
 [<ffffffff8106b70e>] ? worker_thread+0x0/0x25d
 [<ffffffff81070665>] kthread+0x6d/0xae
 [<ffffffff8101313a>] child_rip+0xa/0x20
 [<ffffffff81012afd>] ? restore_args+0x0/0x30
 [<ffffffff810705f8>] ? kthread+0x0/0xae
 [<ffffffff81013130>] ? child_rip+0x0/0x20
Version-Release number of selected component (if applicable):

How reproducible:
Always, random.

Steps to Reproduce:
1. Leave the system idle.

Additional info:

http://www.smolts.org/client/show/pub_d59a227e-c82a-469a-94fb-68b8de343818

00:02.0 VGA compatible controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03)

# rpm -qa \*intel\*
xorg-x11-drv-intel-2.7.0-7.fc11.x86_64
xorg-x11-drv-intel-debuginfo-2.7.0-4.fc11.x86_64
intel-gpu-tools-2.7.0-7.fc11.x86_64
xorg-x11-drv-intel-devel-2.7.0-7.fc11.x86_64

kernel-2.6.30.5-43.fc11.x86_64

# modinfo mantis
filename: /lib/modules/2.6.30.5-43.fc11.x86_64/kernel/drivers/media/dvb/mantis/mantis.ko
license: GPL
author: Manu Abraham
description: Mantis PCI DTV bridge driver
srcversion: 1705C063CE013A7DAD9F6B0
alias: pci:v00001822d00004E35sv*sd*bc*sc*i*
depends: ir-common,dvb-core,stv0299,i2c-core,stb0899,tda10023,tda10021,stb6100,mb86a16,lnbp21
vermagic: 2.6.30.5-43.fc11.x86_64 SMP mod_unload
parm: adapter_nr:DVB adapter numbers (array of short)
parm: verbose:verbose startup messages, default is 1 (yes) (int)

The mantis driver is for the DVB-C card (digital TV card) that is in use on this media center pc.

Is the bug in
1. the intel driver?
2. the mantis driver
3. the kernel?
4. ? (what is events/0:9?)