<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [snb] Graphic corruptions and GPU hang" href="https://bugs.freedesktop.org/show_bug.cgi?id=106859#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [snb] Graphic corruptions and GPU hang" href="https://bugs.freedesktop.org/show_bug.cgi?id=106859">bug 106859</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to Lionel Landwerlin from <a href="show_bug.cgi?id=106859#c10">comment #10</a>) > It seems the kernel flags "Web Content" (which I'm guessing is Firefox) as > the culprit of the GPU hang. You have to be wary in this case. This is Sandybridge and it doesn't have segregated per-process memory, so any client can overwrite the memory of another. In this case, the corruption happened to be in a batch submitted by firefox, but that doesn't guarantee that it was firefox doing the stray writes. But it's a good start since to overwrite a batch buffer, the batch buffer must have been submitted to the GPU and waiting on execution; and the execution pipelines are typically short so the number of clients who may have overwritten the batch is small, and the submitter the prime suspect.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>