Created attachment 113815 [details] GPU crash dump Feb 16 15:06:19 teodor kernel: [drm] stuck on render ring Feb 16 15:06:19 teodor kernel: [drm] GPU HANG: ecode 0:0xffffffff, in Xorg.bin [1422], reason: Ring hung, action: reset Feb 16 15:06:19 teodor kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Feb 16 15:06:19 teodor kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Feb 16 15:06:19 teodor kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Feb 16 15:06:19 teodor kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Feb 16 15:06:19 teodor kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error Feb 16 15:06:19 teodor kernel: [drm:intel_pipe_set_base] *ERROR* pin & fence failed Feb 16 15:06:20 teodor kernel: [drm:i915_reset] *ERROR* Failed to reset chip: -110 Feb 16 15:06:20 teodor kernel: fuse init (API version 7.23)
Timeout, closing. Please reopen if the problem persists with latest kernels.
Yes, it still exists as the kernel still doesn't disable outputs it doesn't take over.
Does this fix the issue http://patchwork.freedesktop.org/patch/msgid/1448297312-18558-1-git-send-email-matthew.d.roper@intel.com
(In reply to Jani Nikula from comment #3) > Does this fix the issue > http://patchwork.freedesktop.org/patch/msgid/1448297312-18558-1-git-send- > email-matthew.d.roper@intel.com Timeout. Assuming that it is fixed by now. If this is not the case, please re-test with latest kernel & Mesa to see if this issue is still occurring since there were improvements pushed in kernel and Mesa that will benefit to your system.
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.