Created attachment 124819 [details] GPU_Hang_Crash_Dump.gz I was investigating this bug https://bugzilla.gnome.org/show_bug.cgi?id=767180 (don't know if there will be any relevance, but thought I would mention it just in case) and came across the following messages in my syslog: Jun 30 22:52:18 <Computer-Name> kernel: [16090.619806] [drm] stuck on render ring Jun 30 22:52:18 <Computer-Name> kernel: [16090.620319] [drm] GPU HANG: ecode 6:0:0x84fefffc, in gnome-shell [1910], reason: Ring hung, action: reset Jun 30 22:52:18 <Computer-Name> kernel: [16090.620321] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Jun 30 22:52:18 <Computer-Name> kernel: [16090.620322] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Jun 30 22:52:18 <Computer-Name> kernel: [16090.620323] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Jun 30 22:52:18 <Computer-Name> kernel: [16090.620324] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Jun 30 22:52:18 <Computer-Name> kernel: [16090.620325] [drm] GPU crash dump saved to /sys/class/drm/card0/error Jun 30 22:52:18 <Computer-Name> kernel: [16090.622412] drm/i915: Resetting chip after gpu hang Jun 30 22:52:24 <Computer-Name> kernel: [16096.656115] [drm] stuck on render ring Jun 30 22:52:24 <Computer-Name> kernel: [16096.656640] [drm] GPU HANG: ecode 6:0:0x84fefffc, in gnome-shell [1910], reason: Ring hung, action: reset Jun 30 22:52:24 <Computer-Name> kernel: [16096.658736] drm/i915: Resetting chip after gpu hang So here I am. I am running Ubuntu GNOME 16.04 64-bit with GNOME 3.20 and Linux kernel version 4.4.0-28-generic. My machine is a Lenovo B590 laptop. I have attached the crash dump as instructed.
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 0x053b02bc, with 0x7a000003 (PIPE_CONTROL) as IPEHR. Batch extract (around 0x053b02bc): 0x053b0290: 0x7b003c04: 3DPRIMITIVE: rect list sequential 0x053b0294: 0x00000003: vertex count 0x053b0298: 0x00000000: start vertex 0x053b029c: 0x00000001: instance count 0x053b02a0: 0x00000000: start instance 0x053b02a4: 0x00000000: index bias 0x053b02a8: 0x7a000003: PIPE_CONTROL 0x053b02ac: 0x00100002: no write, cs stall, stall at scoreboard, 0x053b02b0: 0x00000000: destination address 0x053b02b4: 0x00000000: immediate dword low 0x053b02b8: 0x00000000: immediate dword high 0x053b02bc: 0x7a000003: PIPE_CONTROL 0x053b02c0: 0x00004000: qword write, 0x053b02c4: 0x7fb92004: destination address 0x053b02c8: 0x00000000: immediate dword low 0x053b02cc: 0x00000000: immediate dword high
Please test a new version of Mesa (12 or 13) and mark as REOPENED if you can reproduce and RESOLVED/* if you cannot reproduce.
How do I get a newer version of Mesa?
(In reply to cooks.go.hungry from comment #3) > How do I get a newer version of Mesa? From http://www.mesa3d.org/download.html you can download, build and install latest Mesa version. Alternatively, if you are not familiar with build (check 1st http://www.mesa3d.org/install.html, you have straight forward instructions), you may also update your system via your package manager of your distrution but may not benefit of latest Mesa version yet.
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.