diff options
author | Chris Wilson <chris@chris-wilson.co.uk> | 2010-02-10 09:45:13 +0000 |
---|---|---|
committer | Chris Wilson <chris@chris-wilson.co.uk> | 2010-02-10 09:52:36 +0000 |
commit | 4f0f871730b76730ca58209181d16725b0c40184 (patch) | |
tree | 16f3c8cf9e68992fdf733651232759ecfc3ab231 /intel/libdrm_intel.pc.in | |
parent | fdcde592c2c48e143251672cf2e82debb07606bd (diff) |
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).
References:
Bug 25475 - [i915] Xorg crash / Execbuf while wedged
http://bugs.freedesktop.org/show_bug.cgi?id=25475
Bug 25554 - i830_uxa_prepare_access: gtt bo map failed: Input/output error
http://bugs.freedesktop.org/show_bug.cgi?id=25554
(And probably every other weird bug in the last few months.)
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to 'intel/libdrm_intel.pc.in')
0 files changed, 0 insertions, 0 deletions