Created attachment 129223 [details] GPU crash dump
There are constant improvements pushed in kernel, xf86-video-intel and Mesa that will benefit to your system, so please re-test with latest kernel, xf86-video-intel & Mesa (12 or 13) and: - RESOLVED/* if you cannot reproduce. - After updating if you can reproduce issue, use modesetting DDX and re-test and finally mark as REOPENED ; attach fresh gpu error dump, kernel log & xorg log. *Details: - Kernel: 4.4.0-59-generic - Platform: SandyBridge (PCI ID: 0x0126) - Mesa: [Please confirm your version] - xf86-video-intel: [Please confirm your version] From this error dump, hung is happening in render ring batch with active head at 0x000a978c, with 0x7a000002 (PIPE_CONTROL) as IPEHR. Batch extract (around 0x000a978c): 0x000a9744: 0x79000002: 3DSTATE_DRAWING_RECTANGLE 0x000a9748: 0x00000000: top left: 0,0 0x000a974c: 0x028d04d8: bottom right: 1240,653 0x000a9750: 0x00000000: origin: 0,0 0x000a9754: 0x78011002: 3DSTATE_BINDING_TABLE_POINTERS: VS mod 0, GS mod 0, PS mod 1 0x000a9758: 0x00000000: VS binding table 0x000a975c: 0x00000000: GS binding table 0x000a9760: 0x0003fee0: WM binding table 0x000a9764: 0x7b003c04: 3DPRIMITIVE: rect list sequential 0x000a9768: 0x00000003: vertex count 0x000a976c: 0x00006c4b: start vertex 0x000a9770: 0x00000001: instance count 0x000a9774: 0x00000000: start instance 0x000a9778: 0x00000000: index bias 0x000a977c: 0x7a000002: PIPE_CONTROL 0x000a9780: 0x00101400: no write, cs stall, render target cache flush, texture cache invalidate, 0x000a9784: 0x00000000: 0x000a9788: 0x00000000: 0x000a978c: 0x7a000002: PIPE_CONTROL 0x000a9790: 0x0000c000: TIMESTAMP write,
Idmdev review Yann's reply, this will help to solve your GPU Hang, also is important to collaborate in order to find a solution to a problem. If the bug lacks activity from the submitter the bug will be closed, so please let us know how your testing goes with updated components remember if the problem is solved move it to Resoled, or if it continues update logs and change the status of bug to reopen
Based on the lack of activity and the no response from the submitter the bug will be close.
It's not wontfix as in all likely we have fixed it.
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.