Created attachment 126272 [details] /sys/class/drm/card0/error Up-to-date Debian unstable with gnome-shell: linux-image-4.7.0-1-amd64 4.7.2-1 libdrm-intel1 2.4.70-1 libdrm2 2.4.70-1 libegl1-mesa 12.0.2-1 libgl1-mesa-dri 12.0.2-1 libgl1-mesa-glx 12.0.2-1 libglapi-mesa 12.0.2-1 libgles1-mesa 12.0.2-1 libgles2-mesa 12.0.2-1 libglu1-mesa 9.0.0-2.1 libwayland-egl1-mesa 12.0.2-1 [ 230.067203] [drm] stuck on render ring [ 230.069650] [drm] GPU HANG: ecode 6:0:0x85fffffc, in CivilizationV.e [1681], reason: Engine(s) hung, action: reset [ 230.069656] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 230.069657] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 230.069657] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 230.069658] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 230.069659] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 230.071336] drm/i915: Resetting chip after gpu hang [ 266.042285] [drm] stuck on render ring [ 266.044747] [drm] GPU HANG: ecode 6:0:0x85fffffc, in CivilizationV.e [1681], reason: Engine(s) hung, action: reset [ 266.044948] drm/i915: Resetting chip after gpu hang [ 296.064671] [drm] stuck on render ring [ 296.067246] [drm] GPU HANG: ecode 6:0:0x85fffffc, in CivilizationV.e [1681], reason: Engine(s) hung, action: reset [ 296.068700] drm/i915: Resetting chip after gpu hang [ 306.040244] [drm] stuck on render ring [ 306.043379] [drm] GPU HANG: ecode 6:0:0x85fffffc, in CivilizationV.e [1681], reason: Engine(s) hung, action: reset [ 306.045777] drm/i915: Resetting chip after gpu hang
Assigning to Mesa product (please let me know if I am mistaken with this GPU Hang). From this error dump, hung is happening in render ring batch with active head at 0x741eb764, with 0x7a000003 (PIPE_CONTROL) as IPEHR. Batch extract (around 0x741eb764): 0x741eb72c: 0x78090001: 3DSTATE_VERTEX_ELEMENTS 0x741eb730: 0x02400000: buffer 0: valid, type 0x0040, src offset 0x0000 bytes 0x741eb734: 0x11130000: (X, Y, Z, 1.0), dst offset 0x00 bytes 0x741eb738: 0x7b009004: 3DPRIMITIVE: tri list random 0x741eb73c: 0x0000000c: vertex count 0x741eb740: 0x00000000: start vertex 0x741eb744: 0x00000001: instance count 0x741eb748: 0x00000000: start instance 0x741eb74c: 0x00000000: index bias 0x741eb750: 0x7a000003: PIPE_CONTROL 0x741eb754: 0x00100002: no write, cs stall, stall at scoreboard, 0x741eb758: 0x00000000: destination address 0x741eb75c: 0x00000000: immediate dword low 0x741eb760: 0x00000000: immediate dword high 0x741eb764: 0x7a000003: PIPE_CONTROL 0x741eb768: 0x00004000: qword write, 0x741eb76c: 0x04933004: destination address 0x741eb770: 0x00000000: immediate dword low 0x741eb774: 0x00000000: immediate dword high 0x741eb778: 0x78151003: 3DSTATE_CONSTANT_VS_STATE 0x741eb77c: 0x00007641: dword 1 0x741eb780: 0x00000000: dword 2 0x741eb784: 0x00000000: dword 3 0x741eb788: 0x00000000: dword 4
Please test a new version of Mesa (13) and mark as REOPENED if you can reproduce and RESOLVED/* if you cannot reproduce. If you can reproduce, please capture and upload an apitrace (https://github.com/apitrace/apitrace) so that we can easily reproduce as well.
Dear Reporter, This Mesa bug has been in the "NEEDINFO" status for over 60 days. I am closing this bug based on lack of response but feel free to reopen if resolution is still needed. Please ensure you're supplying the correct information as requested. Thank you.
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.