<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - [bisected, regression] flood of GPU fault detected in logs caused by 9af20... drm/radeon: fix fence locking in the pageflip callback"
href="https://bugs.freedesktop.org/show_bug.cgi?id=59089#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - [bisected, regression] flood of GPU fault detected in logs caused by 9af20... drm/radeon: fix fence locking in the pageflip callback"
href="https://bugs.freedesktop.org/show_bug.cgi?id=59089">bug 59089</a>
from <span class="vcard"><a class="email" href="mailto:alexandre.f.demers@gmail.com" title="Alexandre Demers <alexandre.f.demers@gmail.com>"> <span class="fn">Alexandre Demers</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=59089#c5">comment #5</a>)
<span class="quote">> I get the GPU faults starting with mesa commit
>
> 3e163a137be7f9a80ec720903c4bda028de5681f is the first bad commit
> commit 3e163a137be7f9a80ec720903c4bda028de5681f
> Author: Marek Olšák <<a href="mailto:maraeo@gmail.com">maraeo@gmail.com</a>>
> 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 <<a href="mailto:brianp@vmware.com">brianp@vmware.com</a>></span >
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>