<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [gen4] GPU hang in firefox on Google Chrome homepage (webgl)" href="https://bugs.freedesktop.org/show_bug.cgi?id=84781#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [gen4] GPU hang in firefox on Google Chrome homepage (webgl)" href="https://bugs.freedesktop.org/show_bug.cgi?id=84781">bug 84781</a> from <a class="email" href="mailto:pac12referee@gmail.com" title="pac12referee@gmail.com">pac12referee@gmail.com</a> <pre>Created <a href="attachment.cgi?id=107569" name="attach_107569" title="/sys/class/drm/card0/error log #3">attachment 107569</a> <a href="attachment.cgi?id=107569&action=edit" title="/sys/class/drm/card0/error log #3">[details]</a> /sys/class/drm/card0/error log #3 Error log after upgrading to 3.17.0-031700-generic. dmesg output looks to be the same. $ dmesg -T | tail -8 [Wed Oct 8 09:29:36 2014] [drm] stuck on render ring [Wed Oct 8 09:29:36 2014] [drm] GPU HANG: ecode 0:0x46e4fafe, in firefox [2248], reason: Ring hung, action: reset [Wed Oct 8 09:29:36 2014] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [Wed Oct 8 09:29:36 2014] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [Wed Oct 8 09:29:36 2014] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [Wed Oct 8 09:29:36 2014] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [Wed Oct 8 09:29:36 2014] [drm] GPU crash dump saved to /sys/class/drm/card0/error [Wed Oct 8 09:29:36 2014] [drm:i915_reset] *ERROR* Failed to reset chip: -19</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>