<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - (bisected) 32bit corruption with PIPE_USAGE_STREAM reverted"
href="https://bugs.freedesktop.org/show_bug.cgi?id=84627#c39">Comment # 39</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - (bisected) 32bit corruption with PIPE_USAGE_STREAM reverted"
href="https://bugs.freedesktop.org/show_bug.cgi?id=84627">bug 84627</a>
from <span class="vcard"><a class="email" href="mailto:nholland@tisys.org" title="Nils Holland <nholland@tisys.org>"> <span class="fn">Nils Holland</span></a>
</span></b>
<pre>(In reply to Igor Gnatenko from <a href="show_bug.cgi?id=84627#c38">comment #38</a>)
<span class="quote">> Any news? Seems patch works ok for people. can you sned it for 10.3 stable
> also?</span >
The patch that fixed the issue for us is actually a kernel patch and not a Mesa
patch and as such should work regardless of what Mesa version you're using.
Regarding the question on why this issue only seems to affect 32 bit kernels
and not 64 bit ones, and if the proposes patch can serve as a permanent fix or
is coupled with too many undesirable side-effects ... well, Michel can probably
give more qualified information about that.
As it stands, the patch disables write-combining and thus will probably have
negative effects on performance, although I don't really notice any difference
on my own machine compared to the time "when things worked fine without any
patching at all" (but I'm not really running very demanding stuff). Just using
a 64 bit kernel instead of going down the patch route should fix the problem
without these side-effects.</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>