Created attachment 109636 [details]
gpu crash dump
[103115.648697] [drm] stuck on render ring
[103115.649344] [drm] GPU HANG: ecode 0:0x85fffff8, in chrome , reason: Ring hung, action: reset
[103115.649346] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[103115.649346] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[103115.649347] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[103115.649347] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[103115.649348] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[103117.649858] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
~ ❯❯❯ uname -a
Linux aoba 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Found this in dmesg as well:
[45315.265221] [drm] Wrong MCH_SSKPD value: 0x16040307
[45315.265222] [drm] This can cause pipe underruns and display issues.
[45315.265222] [drm] Please upgrade your BIOS to fix this.
[45317.161633] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
but not sure if it's related.
3.16 is too old to support (though it wasn't when you filed the bug... sorry). The good news is that *lots* of fixes went into the kernel and Mesa in the last two years.
In the future, please tell us how to reproduce the hang (if it's not reproducible, there's very little we can do about it) and at least the output of "glxinfo | grep Mesa".