<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - Intel driver crash in brw_update_renderbuffer_surface" href="https://bugs.freedesktop.org/show_bug.cgi?id=79675#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - Intel driver crash in brw_update_renderbuffer_surface" href="https://bugs.freedesktop.org/show_bug.cgi?id=79675">bug 79675</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>The problem is that we only capture the first error state (since it usually is the more interesting cause, and they can hog a lot of kernel memory) and we only free the error state when root does "echo > /sys/class/drm/card0/error". Since the two error here occur within a few seconds, capturing the second error does not seem practical. So what I want you to do is see if you get a GPU hang reported that doesn't take the system down with it, and attach that error state to see if it indicates a reason for the other hang. It may just be the system is not recovering from the GPU hang correctly - e.g. mesa did not invalidate its context and so subsequent batches referenced invalid state.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>