Created attachment 112696 [details] Error log I actually didn't know what happen, but as I open dmesg it shows this, so I just submit this. System is Archlinux 64-bit, Kernel 3.18 (as shown in the error log). The dmesg tells 2 error, but only produce 1 error log, for a reason I just don't know. Quoting dmesg: [182837.319770] [drm] GPU HANG: ecode 0:0x00ababab, in systemd-logind [248], reason: Ring hung, action: reset [182837.319772] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [182837.319774] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [182837.319775] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [182837.319776] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [182837.319777] [drm] GPU crash dump saved to /sys/class/drm/card0/error [183084.318376] [drm] stuck on render ring [183084.319809] [drm] GPU HANG: ecode 0:0x003d3d3d, in systemd-logind [248], reason: Ring hung, action: reset
There are a few cachelines worth of pixel data inside the batchbuffer - which is what the GPU hung on. The writes within the batches, up to the hang at least, are all contained within their respective target surfaces and shouldn't be the source of the scribbling. The batch doesn't overlap a fence register. It is not clear how we could end up with corruption in the middle of the batch. All I can ask is that you keep filing the error state in case one captures a clear violation, and if you could build debug packages of X, xf86-video-intel, mesa, the additional self-checks may find the culprit.
*** Bug 88798 has been marked as a duplicate of this bug. ***
Any update Christian?
(In reply to yann from comment #3) > Any update Christian? Timeout. Assuming that it is fixed by now. If this is not the case, please re-test with latest kernel & Mesa (12-13) to see if this issue is still occurring since there were improvements pushed in kernel and Mesa that will benefit to your system, and fill a new bug.
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.