Created attachment 120918 [details] GPU crash dump from /sys/class/drm/card0/error While playing Minecraft, I am getting the following error in dmesg: [ 137.782060] [drm] stuck on render ring [ 137.784210] [drm] GPU HANG: ecode 9:0:0x84df7efc, in java [1628], reason: Ring hung, action: reset [ 137.784215] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 137.784217] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 137.784219] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 137.784221] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 137.784224] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 137.786226] drm/i915: Resetting chip after gpu hang [ 139.757724] [drm] RC6 on
PCI ID: 0x1912 Skylake
*** Bug 97395 has been marked as a duplicate of this bug. ***
There were workaround for SKL and improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring. In the meantime, assigning to Mesa product. From this error dump, hung is happening in render ring batch with active head at 0x0b6fbb04, with 0x7b000005 (3DPRIMITIVE) as IPEHR. Batch extract (around 0x0b6fbb04): 0x0b6fbadc: 0x78490001: 3D UNKNOWN: 3d_965 opcode = 0x7849 0x0b6fbae0: 0x00000003: MI_NOOP 0x0b6fbae4: 0x00000000: MI_NOOP Bad length 7 in (null), expected 6-6 0x0b6fbae8: 0x7b000005: 3DPRIMITIVE: fail sequential 0x0b6fbaec: 0x00000007: vertex count 0x0b6fbaf0: 0x000002e8: start vertex 0x0b6fbaf4: 0x00000000: instance count 0x0b6fbaf8: 0x00000001: start instance 0x0b6fbafc: 0x00000000: index bias 0x0b6fbb00: 0x00000000: MI_NOOP 0x0b6fbb04: 0x784a0000: 3D UNKNOWN: 3d_965 opcode = 0x784a 0x0b6fbb08: 0x00000000: MI_NOOP
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.