More consistent for me on recent kernels too. I don't get an "oops"
though, just a total console freeze. I can still log in remotely and get
shut down cleanly but only if I kill the X server process itself.
No relation to VT switching - there used to be problems but those bugs
all solved for me some time ago and I think unrelated.
I am using the xorg-edgers PPA but I see the lockups if I switch back to
Jaunty versions.
I see the lockups under a variety of kernels including
- the most recent Ubuntu 2.6.28-11.40
- Various 2.6.29 builds including the Ubuntu RC1 version
- My build of 2.6.30RC1
Useful debug info depends on which kernel it happened with - in my build I have
some of the watchdogs switched on which may help? For instance:
Apr 8 16:31:03 vademecum kernel: [ 0.000000] Linux version 2.6.30-rc1ze
(r...@vademecum) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #1 SMP Wed Apr 8
12:16:38 BST 2009
Apr 8 17:20:20 vademecum kernel: [ 3000.768092] INFO: task events/0:9 blocked
for more than 120 seconds.
Apr 8 17:20:20 vademecum kernel: [ 3000.768108] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 8 17:20:20 vademecum kernel: [ 3000.768122] events/0 D 0000029d 0
9 2
Apr 8 17:20:20 vademecum kernel: [ 3000.768141] f7875f40 00000046 3c688907
0000029d f7b22fc0 00000000 00000000 c0568d24
Apr 8 17:20:20 vademecum kernel: [ 3000.768170] c056c7b0 f7836b70 f7836de8
c17097b0 00000000 0009d202 0901f1fd 0000029d
Apr 8 17:20:20 vademecum kernel: [ 3000.768198] c056c7b0 ee0fc700 f7836b70
c1705d24 f7836de8 5eefa7b0 00000278 00000000
Apr 8 17:20:20 vademecum kernel: [ 3000.768225] Call Trace:
Apr 8 17:20:20 vademecum kernel: [ 3000.768256] [<c03ad7cc>]
__mutex_lock_slowpath+0xc0/0x124
Apr 8 17:20:20 vademecum kernel: [ 3000.768276] [<c0132f39>] ?
add_timer+0x11/0x18
Apr 8 17:20:20 vademecum kernel: [ 3000.768292] [<c03ad65a>]
mutex_lock+0x1a/0x28
Apr 8 17:20:20 vademecum kernel: [ 3000.768337] [<f8d01d66>]
i915_gem_retire_work_handler+0x22/0x58 [i915]
Apr 8 17:20:20 vademecum kernel: [ 3000.768357] [<c013933f>]
worker_thread+0x13f/0x1f0
Apr 8 17:20:20 vademecum kernel: [ 3000.768396] [<f8d01d44>] ?
i915_gem_retire_work_handler+0x0/0x58 [i915]
Apr 8 17:20:20 vademecum kernel: [ 3000.768415] [<c013c910>] ?
autoremove_wake_function+0x0/0x34
Apr 8 17:20:20 vademecum kernel: [ 3000.768433] [<c0139200>] ?
worker_thread+0x0/0x1f0
Apr 8 17:20:20 vademecum kernel: [ 3000.768449] [<c013c5e3>] kthread+0x37/0x6c
Apr 8 17:20:20 vademecum kernel: [ 3000.768464] [<c013c5ac>] ?
kthread+0x0/0x6c
Apr 8 17:20:20 vademecum kernel: [ 3000.768481] [<c0103bcf>]
kernel_thread_helper+0x7/0x10
Apr 8 17:27:25 vademecum kernel: [ 3425.968132] [drm:i915_gem_idle] *ERROR*
hardware wedged
I don't think I get the "wedged" message until I have killed the X
server from a remote shell.
Just to demonstrate this happens on a known kernel (and so can report it here
as a bug...)
Apr 9 11:44:49 vademecum kernel: [ 0.000000] Linux version
2.6.28-11-generic (bui...@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) )
#40-Ubuntu SMP Fri Apr 3 17:39:51 UTC 2009 (Ubuntu 2.6.28-11.40-generic)
Apr 9 12:24:07 vademecum kernel: [ 2392.165112] [drm:i915_gem_idle] *ERROR*
hardware wedged
The trace from the .30RC1 kernel seems pretty consistent with what
Martin is seeing.
--
WARNING: at /build/buildd/linux-2.6.28/drivers/gpu/drm/i915/i915_gem.c:2475
i915_gem_idle+0x2ec/0x310 [i915]()
https://bugs.launchpad.net/bugs/345806
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
