Hi, i got this message on kmesg after resuming from suspend to ram. I think it happens often, after resuming. But now i read this on kmesg, i hope this helps to solve some bug: [ 1471.834486] [drm] stuck on render ring [ 1471.834895] [drm] GPU HANG: ecode 6:0:0xf288fff9, in Xorg [2700], reason: Ring hung, action: reset [ 1471.834896] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 1471.834897] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 1471.834898] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 1471.834899] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 1471.834900] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 1471.836993] drm/i915: Resetting chip after gpu hang [ 1477.832636] [drm] stuck on render ring [ 1477.833230] [drm] GPU HANG: ecode 6:0:0xb2c8fffd, in Xorg [2700], reason: Ring hung, action: reset [ 1477.833332] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning! [ 1477.835356] drm/i915: Resetting chip after gpu hang [ 1483.841019] [drm] stuck on render ring [ 1483.841470] [drm] GPU HANG: ecode 6:0:0x84fefffc, in chrome [3403], reason: Ring hung, action: reset [ 1483.843559] drm/i915: Resetting chip after gpu hang
Created attachment 125714 [details] /sys/class/drm/card0/error
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 0x0052e21c, with 0x7a000002 (PIPE_CONTROL) as IPEHR. Batch extract (around 0x0052e21c): 0x0052e1f4: 0x7b003c04: 3DPRIMITIVE: rect list sequential 0x0052e1f8: 0x00000003: vertex count 0x0052e1fc: 0x00000000: start vertex 0x0052e200: 0x00000001: instance count 0x0052e204: 0x00000000: start instance 0x0052e208: 0x00000000: index bias 0x0052e20c: 0x7a000002: PIPE_CONTROL 0x0052e210: 0x00101000: no write, cs stall, render target cache flush, 0x0052e214: 0x00000000: 0x0052e218: 0x00000000: 0x0052e21c: 0x78011002: 3DSTATE_BINDING_TABLE_POINTERS: VS mod 0, GS mod 0, PS mod 1 0x0052e220: 0x00000000: VS binding table 0x0052e224: 0x00000000: GS binding table 0x0052e228: 0x0003ff60: WM binding table finally we may note that Instruction Stream interface done Register is not set to default: INSTDONE: 0x8888fffb busy: EU 32 busy: EU 31 busy: EU 30 busy: EU 22 busy: EU 21 busy: EU 20 busy: EU 12 busy: EU 11 busy: EU 10 busy: EU 02 busy: EU 01 busy: EU 00 busy: HIZ
Please test a new version of Mesa (12 or 13) and mark as REOPENED if you can reproduce and RESOLVED/* if you cannot reproduce.
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.