Created attachment 98072 [details] GPU crash dump saved to /sys/class/drm/card0/error [drm] GPU crash dump saved to /sys/class/drm/card0/error [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. i915: render error detected, EIR: 0x00000010 i915: page table error i915: PGTBL_ER: 0x00010000 [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking i915: render error detected, EIR: 0x00000010 i915: page table error i915: PGTBL_ER: 0x00010000 After this bug GLX applications (e.g. glxgears) threw core dumps on startup, after displaying an empty black window. After applying the fence counting patch (attachment 75820 [details] [review] from https://bugs.freedesktop.org/show_bug.cgi?id=59771 ), dri applications continue to work, and the Xorg server process outputs a fence error almost on startup ("Fixing up fence counts; was -1, expected 0" - the patch only displays this error once). I don't know how to trigger the error, other than using 3d-accelerated programs for some time. Package versions (current debian unstable): mesa 10.1.0-5 libdrm 2.4.52-1 + fence counting patch applied xorg-xserver 2:1.15.1-1 linux-kernel 3.14.1 (own config) CONFIG_DRM_I915=m CONFIG_DRM_I915_KMS=y CONFIG_DRM_I915_FBDEV=y # CONFIG_DRM_I915_PRELIMINARY_HW_SUPPORT is not set # CONFIG_DRM_I915_UMS is not set
Created attachment 98073 [details] Xorg.0.log
Created attachment 98074 [details] lspci output
Created attachment 98075 [details] dmesg output from boot
Created attachment 98076 [details] xorg.conf configuration file
The overlay itself is not even active, nor changing. Presumably something in the update of neighbouring PTE upset the hw.
Could you please test with latest drm-intel-nightly to see if the issue is still present and paste new logs?
timeout. Feel free to reopen if you are still able to reproduce on recent kernels updating new logs.
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.