<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [snb 3.5] stale semaphore sync seqno (typically as seen on bcs->rcs)" href="https://bugs.freedesktop.org/show_bug.cgi?id=54226#c123">Comment # 123</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [snb 3.5] stale semaphore sync seqno (typically as seen on bcs->rcs)" href="https://bugs.freedesktop.org/show_bug.cgi?id=54226">bug 54226</a> from <a class="email" href="mailto:bugzilla@dderby.com" title="David <bugzilla@dderby.com>"> David</a> <pre>Created <a href="attachment.cgi?id=92710" name="attach_92710" title="i915_error_state">attachment 92710</a> <a href="attachment.cgi?id=92710&action=edit" title="i915_error_state">[details]</a> i915_error_state I'm also getting regular Sandybridge GPU lockups with Mesa 10.0.1 and Linux kernel 3.13. dmesg output: [ 918.876872] [drm] stuck on render ring [ 918.876876] [drm] stuck on blitter ring [ 918.876878] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 918.876879] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 918.876879] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 918.876880] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 918.876880] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 932.923240] [drm] stuck on render ring [ 932.923242] [drm] stuck on blitter ring Unfortunately the crash dump doesn't help - it's an empty file!</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>