Created attachment 114144 [details] GPU crash dump When running LibreOffice w/ OpenGL rendering enabled: [drm] stuck on render ring [drm] GPU HANG: ecode 0:0xfde5fafd, in soffice.bin [16924], reason: Ring hung, action: reset [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [drm] GPU crash dump saved to /sys/class/drm/card0/error [drm:i915_reset] *ERROR* Failed to reset chip: -19 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c)
Linux 3.18.6 Mesa 10.5.0-rc3 Xorg 1.17.1 xf86-video-intel 2.99.917 libdrm 2.4.59
It would be very helpful if you could make an apitrace that reproduces the hang.
Created attachment 116250 [details] Crash trace (In case posting links to third-party file sharing service is appropriate.)
Created attachment 116252 [details] GPU crash dump 2 [ 154.708214] [drm] stuck on render ring [ 154.709154] [drm] GPU HANG: ecode 4:0:0xfde5fafd, in soffice.bin [1798], reason: Ring hung, action: reset [ 154.709156] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 154.709157] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 154.709158] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 154.709159] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 154.709160] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 154.941322] drm/i915: Resetting chip after gpu hang [ 162.708217] [drm] stuck on render ring [ 162.709236] [drm] GPU HANG: ecode 4:0:0xfde5fafd, in soffice.bin [1798], reason: Ring hung, action: reset [ 162.735223] [drm:i915_gem_reset] *ERROR* gpu hanging too fast, banning! [ 162.735339] drm/i915: Resetting chip after gpu hang [ 230.704062] [drm] stuck on render ring [ 230.706507] [drm] GPU HANG: ecode 4:0:0xfde5fafd, in glretrace [2604], reason: Ring hung, action: reset [ 230.799803] drm/i915: Resetting chip after gpu hang [ 252.704067] [drm] stuck on render ring [ 252.704947] [drm] GPU HANG: ecode 4:0:0xfde5fafd, in glretrace [2604], reason: Ring hung, action: reset [ 252.727077] drm/i915: Resetting chip after gpu hang [ 285.704099] [drm] stuck on render ring [ 285.704968] [drm] GPU HANG: ecode 4:0:0xfde5fafd, in glretrace [2604], reason: Ring hung, action: reset [ 285.735096] drm/i915: Resetting chip after gpu hang [ 301.708138] [drm] stuck on render ring [ 301.709004] [drm] GPU HANG: ecode 4:0:0xfde5fafd, in glretrace [2604], reason: Ring hung, action: reset [ 301.738103] drm/i915: Resetting chip after gpu hang [ 309.708051] [drm] stuck on render ring [ 309.708989] [drm] GPU HANG: ecode 4:0:0xfde5fafd, in glretrace [2604], reason: Ring hung, action: reset [ 309.741060] [drm:i915_gem_reset] *ERROR* gpu hanging too fast, banning! [ 309.741152] drm/i915: Resetting chip after gpu hang [ 346.077895] Adding 1004056k swap on /dev/sda2. Priority:-1 extents:1 across:1004056k [ 1244.708063] [drm] stuck on render ring [ 1244.709063] [drm] GPU HANG: ecode 4:0:0xfde5fafd, in soffice.bin [8552], reason: Ring hung, action: reset [ 1244.737141] drm/i915: Resetting chip after gpu hang [ 1260.704272] [drm] stuck on render ring [ 1260.705301] [drm] GPU HANG: ecode 4:0:0xfde5fafd, in soffice.bin [8552], reason: Ring hung, action: reset [ 1260.724297] drm/i915: Resetting chip after gpu hang
Linux 4.0.4 Mesa 10.5.6 Xorg 1.17.1 xf86-video-intel 2.99.917 libdrm 2.4.60
Comment on attachment 116250 [details] Crash trace https://drive.google.com/file/d/0B5OOyjuMkJ_QV3JHcXpFbWtFd00/view?usp=sharing https://drive.google.com/file/d/0B5OOyjuMkJ_QZHAtVHctNHJ6VGs/view?usp=sharing
This looks like a GPU hang that was properly fixed in Mesa 10.6. Please try a newer Mesa. Feel free to reopen if you're still having trouble.
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.