Forwarding this bug for Ubuntu user jcastro:
GPU hang encountered on -intel 2.9.1 when using GnomeDo. Dump provided.
I was typing on my machine and it locked up. apw investigated and we determined that the GPU is hanging, I am attaching the dump from intel_gpu_dump.
Date: Wed Feb 3 10:33:51 2010
DistroRelease: Ubuntu 10.04
MachineType: LENOVO 7454CTO
Package: xserver-xorg-video-intel 2:2.9.1-1ubuntu3
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-12-generic root=UUID=28816996-d619-4556-9483-a0084b8a200d ro splash quiet
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
Uname: Linux 2.6.32-12-generic x86_64
dmi.bios.version: 6DET28WW (1.05 )
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.version: Not Available
dmi.product.version: ThinkPad X200
architecture: x86_64kernel: 2.6.32-12-generic
Created attachment 33036 [details]
Created attachment 33037 [details]
Created attachment 33038 [details]
Created attachment 33039 [details]
Created attachment 33040 [details]
Created attachment 33041 [details]
For any bugs showing mysterious Intel-graphics crashes with libdrm 2.4.17,
please encourage the bug reporters to re-try with libdrm 2.4.18 (just
released today). It includes the commit below.
I'll mark this as NEEDINFO for now. Please update the bug (and clear
NEEDINFO) after adding results of testing with libdrm 2.4.18.
Author: Chris Wilson <firstname.lastname@example.org>
Date: Wed Feb 10 09:45:13 2010 +0000
intel: Handle resetting of input params after EINTR during SET_TILING
The SET_TILING is pernicious in that it overwrites the input arguments
following an error in order to report the current tiling state of the
buffer. This caught us by surprise as we then fed those arguments back
into to the ioctl unmodified following an EINTR and so the kernel then
reported success for the no-op. We interpreted this success as meaning
that the tiling on the buffer had changed so updated our state and
started using the buffer incorrectly in the new tiled/untiled manner.
This lead to all sorts of random corruption and GPU hangs, even though
the batch buffers would look sane (when the GPU had not wandered off
into forbidden territory).
Bug 25475 - [i915] Xorg crash / Execbuf while wedged
Bug 25554 - i830_uxa_prepare_access: gtt bo map failed: Input/output error
(And probably every other weird bug in the last few months.)
Signed-off-by: Chris Wilson <email@example.com>
2.4.18 seems to have fixed this problem. Thanks!