<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - [snb] blorp hang" href="https://bugs.freedesktop.org/show_bug.cgi?id=72443#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - [snb] blorp hang" href="https://bugs.freedesktop.org/show_bug.cgi?id=72443">bug 72443</a> from <a class="email" href="mailto:greatquux@gmail.com" title="Mike Russo <greatquux@gmail.com>"> Mike Russo</a> <pre>So I decided to try this in 3.13rc6 and I do still get the error. I see that the verbiage of the error reported in syslog has been updated so I now see: Jan 2 14:20:12 ossy kernel: [ 128.655128] [drm] stuck on render ring Jan 2 14:20:12 ossy kernel: [ 128.655136] [drm] GPU crash dump saved to /sys/class/drm/card0/error Jan 2 14:20:12 ossy kernel: [ 128.655137] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Jan 2 14:20:12 ossy kernel: [ 128.655138] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Jan 2 14:20:12 ossy kernel: [ 128.655138] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Jan 2 14:20:12 ossy kernel: [ 128.655139] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Jan 2 14:20:12 ossy kernel: [ 128.658048] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x1260000 ctx 3) at 0x1261c20 Mesa was updated this morning and is: OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Desktop OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.1.0-devel (git-5a51c1b saucy-oibaf-ppa) Intel driver: [ 32.143] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.907+git1401021930.4d8f78~gd~s (Oibaf <<a href="mailto:fmrummey@gmail.com">fmrummey@gmail.com</a>>) I reproduced the same way as my original bug report. I also tried using the "ilo" driver and Gallium acceleration, but they both hung with similar messages. I haven't tried it recently but only "NoAccel" made it impossible to hit the desktop lockups. I will attach the new error file after this update.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>