[Bug 59089] [bisected, regression] flood of GPU fault detected in logs caused by 9af20... drm/radeon: fix fence locking in the pageflip callback

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Jan 13 22:01:26 PST 2013


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

--- Comment #6 from Alexandre Demers <alexandre.f.demers at gmail.com> ---
(In reply to comment #5)
> I get the GPU faults starting with mesa commit
> 
> 3e163a137be7f9a80ec720903c4bda028de5681f is the first bad commit
> commit 3e163a137be7f9a80ec720903c4bda028de5681f
> Author: Marek Olšák <maraeo at gmail.com>
> Date:   Thu Nov 29 02:55:01 2012 +0100
> 
>     gallium/postprocess: share pipe_context and cso_context with the state
> tracker
>     
>     Using one context instead of two is more efficient and
>     we can skip another context flush.
>     
>     Reviewed-by: Brian Paul <brianp at vmware.com>

Is it a flood? Other commits may create GPU faults, but it shouldn't flood your
logs. I think it would be better to track different sources of GPU faults in
different bugs.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130114/164243a8/attachment-0001.html>


More information about the dri-devel mailing list