[Bug 79675] Intel driver crash in brw_update_renderbuffer_surface

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79675

--- Comment #3 from Chris Wilson <chris at chris-wilson.co.uk> ---
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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140605/25e3ceb6/attachment.html>