path: root/drivers/gpu/drm/i915/i915_suspend.c
diff options
authorChris Wilson <chris@chris-wilson.co.uk>2013-06-12 10:15:12 +0100
committerDaniel Vetter <daniel.vetter@ffwll.ch>2013-06-16 01:10:45 +0200
commit19b2dbde5732170a03bd82cc8bd442cf88d856f7 (patch)
tree2c3da40ef05cb5b8a48945b877600e39a5d40ca5 /drivers/gpu/drm/i915/i915_suspend.c
parent7d132055814ef17a6c7b69f342244c410a5e000f (diff)
drm/i915: Restore fences after resume and GPU resets
Stéphane Marchesin found that fences for pinned objects (i.e. the scanout) were not being restored upon resume, leading to corruption on the display and reference counting issues. This is due to a bug in commit 312817a39f17dbb4de000165b5b724e3728cd91c [2.6.38] Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Nov 22 11:50:11 2010 +0000 drm/i915: Only save and restore fences for UMS that zapped the pinned fences even though they were in use. Fortuitously, whilst we forced a VT switch during suspend and resume, no fences were ever pinned at the time. However, we now can do switchless S3 transitions and so the old bug finally surfaces. Reported-by: Stéphane Marchesin <marcheu@chromium.org> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Cc: Stéphane Marchesin <marcheu@chromium.org> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/gpu/drm/i915/i915_suspend.c')
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/gpu/drm/i915/i915_suspend.c b/drivers/gpu/drm/i915/i915_suspend.c
index 41f0fdecfbdc..369b3d8776ab 100644
--- a/drivers/gpu/drm/i915/i915_suspend.c
+++ b/drivers/gpu/drm/i915/i915_suspend.c
@@ -384,6 +384,7 @@ int i915_restore_state(struct drm_device *dev)
+ i915_gem_restore_fences(dev);
if (!drm_core_check_feature(dev, DRIVER_MODESET)) {