[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@xxxxxxxxxxxxxxx · Mon, 14 Jan 2013 06:01:26 +0000

            Comment # 6
              on bug 59089
              from  Alexandre Demers

        (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@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@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.

_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel