Since v3.9, when running Ubuntu 13.04 with the X and Mesa stack from https://launchpad.net/~xorg-edgers/+archive/ppa, I have been getting frequent hangs on my Thinkpad E220S running with a Sandy Bridge (8086:0116/Core i5-2537M) GPU: [10121.411125] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [10121.411131] [drm] capturing error event; look for more information in /sys/kernel/debug/dri/0/i915_error_state -- [53978.637042] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung -- [68285.759379] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [68285.759404] [drm:kick_ring] *ERROR* Kicking stuck semaphore on render ring -- [69825.557728] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [69825.557740] [drm] capturing error event; look for more information in /sys/kernel/debug/dri/0/i915_error_state In v3.9.x, X would freeze up, and I would have to kill X via Alt+SysRq+K in order to get out of the situation, but in v3.10 it looks like it's at least able to unhang itself without crashing X.
We need the error state file from debugfs (please attach as gzip to fit into bugzilla size limits).
Here you go: http://people.ubuntu.com/~hyperair/i915-error-state
We seem to be executing (or trying to) complete garbage ... or the error state capture code is doing something funny. I'm confused. Chris?
That's the old i965g gallium driver.
What? No, I'm not running i965g. I don't even have that installed.
Created attachment 105931 [details] i915_error_state from 3.10-rc6 If it helps, here's one from 3.10-rc6.
At this moment, glxinfo would be more useful. Those batches are profoundly incorrect (sending commands for the wrong generation of GPUs).
Created attachment 105941 [details] glxinfo -l output
That last error state is much cleaner; just the usual mesa blorp death.
Yeah, this smells like a mesa bug. Please retest with latest git mesa (if possible) and file a bug on bugs.freedesktop.org against Mesa -> Drivers/DRI/i965 with the error_state attached.