Created attachment 92471 [details]
dmesg with drm.debug=1
After connecting secondary monitor and opening Chromium with maps.google.com, I experience hangs in range of minutes. Following message appears in dmesg:
[ 2052.057508] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring
Attaching necessary debug info.
Created attachment 92472 [details]
glxinfo output on affected machine
Created attachment 92473 [details]
i915_error_state on affected machine after triggering bug
Created attachment 92474 [details]
Xorg.0.log on affected machine after triggering bug
Sorry no one ever investigated your bug.
Please reopen if you can still reproduce with Mesa 17.0.
Can't reproduce this bug on:
Linux Mint 18.3 (Kernel 4.16.0-041600-generic)
Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
Intel(R) Sandybridge Mobile (0x126)
chromium-browser (65.0.3325.181 Built on Ubuntu)
Mesa 10.0.2 (git-108e50c), Mesa 17.2.8 (from default install), Mesa 18.1.0-devel (git-108e50c)
In all cases chromium operated normally without any issues. Tried map, satellite and street views.
Note that this bug was filed back in 2014; I can not replicate this issue on the same hardware now.
No worries! Mesa has come a *long* way since 2014. I'm sure this bug was real (and frustrating) at the time. Sorry it took so long to address it.
Thank you for taking the time to write up the bug. We do read everything entered into bugzilla, although that may not have been true 4 years ago.
No strong feelings there at all -- I believe the whole stack has changed/improved so much that the bug could have gotten fixed as a side effect :) . So, thanks for all the fixes :)