Created an attachment (id=24962)
GPU dump with 2.6.30rc2
I tried to reproduce this with linux 2.6.30RC2 and libdrm 2.4.9, so that I could use intel_gpu_dump (standard Jaunty, where I encountered the hang before, has 2.6.28.8 and libdrm 2.4.5). However, the symptomps are now slightly different, so I'm not sure whether this is useful at all:
- I get hangs without any special VT switches/suspend/etc after a few hours.
- After suspend, the first hang again occurs after a few minutes
- Unlike with standard jaunty, I can recover from the hang with a VT switch, but then it again happends after a few minutes. GPU dump attached (compressed, sorry, raw file was too big for bugzilla)
- This also happens without compositing (where as disabling compiz was a good workaround for the original bug here).
For each hang that happens, I get
[ 204.095061] [drm:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
Created an attachment (id=24962)
GPU dump with 2.6.30rc2
I tried to reproduce this with linux 2.6.30RC2 and libdrm 2.4.9, so that I could use intel_gpu_dump (standard Jaunty, where I encountered the hang before, has 2.6.28.8 and libdrm 2.4.5). However, the symptomps are now slightly different, so I'm not sure whether this is useful at all:
- I get hangs without any special VT switches/ suspend/ etc after a few hours.
- After suspend, the first hang again occurs after a few minutes
- Unlike with standard jaunty, I can recover from the hang with a VT switch, but then it again happends after a few minutes. GPU dump attached (compressed, sorry, raw file was too big for bugzilla)
- This also happens without compositing (where as disabling compiz was a good workaround for the original bug here).
For each hang that happens, I get
[ 204.095061] [drm:i915_ get_vblank_ counter] *ERROR* trying to get vblank count for disabled pipe 1
in dmesg.