<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#c34">Comment # 34</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>Ok, I believe I can confirm smoki's findings that only 32 bit kernels are
affected while identically configured 64 bit ones are not.
I'm on Gentoo Linux where I've custom-compiled my whole system, including the
kernel (which, originally, was a 32 bit one). I now took my kernel config and
changed only two things: I turned on the option to compile a 64 bit kernel as
well as the option that allows me to run 32 bit binaries with the resulting
kernel. I then compiled the exact same kernel sources I had used before and
upon booting the new 64 bit kernel Mesa worked absolutely fine without any
visible corruption.
I guess that proves Michels point that this issue seems to be 32 bit toolchain
related.</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>