Created attachment 110398 [details]
When I tried to use Google Maps via Google chrome I got stuck interface and after graphics restart next msg in dmesg:
[ 4137.395603] [drm] stuck on render ring
[ 4137.396431] [drm] GPU HANG: ecode 0:0x85fffff8, in chrome , reason: Ring hung, action: reset
[ 4137.396434] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 4137.396436] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 4137.396437] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 4137.396438] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 4137.396439] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Fedora linux 20.
File /sys/class/drm/card0/error attached.
How reproducible is this? Occasional? Pretty frequent?
If you're up for building a patched Mesa, you might try the snb-always-flush branch of my tree - git://people.freedesktop.org/~kwg/mesa
It'd be great to know if it helps, or makes things worse.
(In reply to Kenneth Graunke from comment #1)
> How reproducible is this? Occasional? Pretty frequent?
> If you're up for building a patched Mesa, you might try the snb-always-flush
> branch of my tree - git://people.freedesktop.org/~kwg/mesa
> It'd be great to know if it helps, or makes things worse.
It's reproducing every time when I open Google Maps.
Sorry no one ever investigated your bug.
The good news is that everything seems to be working on kernel 4.9.5 and
Please reopen if you can still reproduce with Mesa 17.0.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1465.