Created attachment 129277 [details] /sys/class/drm/card0/error Problem: plasma crash and black screen with only pointer for 5-10 seconds after resume from hibernate. After that system mostly operates normal with rare random hangs. Laptop: Lenovo Yoga 260 with i7 6500U Distributive: Arch DE: KDE uname: Linux kostya-laptop 4.9.6-1-ARCH #1 SMP PREEMPT Thu Jan 26 09:22:26 CET 2017 x86_64 GNU/Linux extra/intel-ucode 20161104-1 Microcode update files for Intel CPUs extra/mesa 13.0.3-1 an open-source implementation of the OpenGL specification extra/xf86-video-intel 1:2.99.917+747+g028c946d-1 (xorg-drivers) X.org Intel i810/i830/i915/945G/G965+ video drivers
Created attachment 129278 [details] dmesg
*** Bug 99281 has been marked as a duplicate of this bug. ***
*** Bug 99046 has been marked as a duplicate of this bug. ***
commit bafb2f7d4755bf1571bd5e9a03b97f3fc4fe69ae [v4.10-rc1] Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Wed Sep 21 14:51:08 2016 +0100 drm/i915/execlists: Reset RING registers upon resume There is a disparity in the context image saved to disk and our own bookkeeping - that is we presume the RING_HEAD and RING_TAIL match our stored ce->ring->tail value. However, as we emit WA_TAIL_DWORDS into the ring but may not tell the GPU about them, the GPU may be lagging behind our bookkeeping. Upon hibernation we do not save stolen pages, presuming that their contents are volatile. This means that although we start writing into the ring at tail, the GPU starts executing from its HEAD and there may be some garbage in between and so the GPU promptly hangs upon resume. Testcase: igt/gem_exec_suspend/basic-S4 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=96526 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Link: http://patchwork.freedesktop.org/patch/msgid/20160921135108.29574-3-chris@chris-wilson.co.uk *** This bug has been marked as a duplicate of bug 96526 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.