Comment 111 for bug 1388612

(In reply to Kenneth Graunke from comment #86)
> Hi all. I believe this should be fixed with Mesa master - specifically,
> this commit:
>
> commit c4fd0c9052dd391d6f2e9bb8e6da209dfc7ef35b
> Author: Kenneth Graunke <email address hidden>
> Date: Sat Jan 17 23:21:15 2015 -0800
>
> i965: Work around mysterious Gen4 GPU hangs with minimal state changes.
>
> If you're able to test with Mesa master, I'd appreciate any reports of
> whether this solved the problem for you. It seems to have helped for me.

Hi.
On Archlinux 3.18.4-1-ARCH, with mesa 10.4.3-1, the crashes caused by chrome have gone away. However, visiting google.com/chrome on firefox now causes the same crash that chrome used to cause.

[179870.322075] [drm] stuck on render ring
[179870.323089] [drm] GPU HANG: ecode 0:0x7f64fafd, in firefox [14619], reason: Ring hung, action: reset
[179870.323092] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[179870.323093] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[179870.323095] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[179870.323097] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[179870.323098] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[179870.323548] [drm:i915_reset] *ERROR* Failed to reset chip: -19