<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:darktjm@gmail.com" title="Thomas J. Moore <darktjm@gmail.com>"> <span class="fn">Thomas J. Moore</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - cik_sdma_copy_texture broken on Carrizo (mesa 12)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97029">bug 97029</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Severity</td>
<td>normal
</td>
<td>major
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - cik_sdma_copy_texture broken on Carrizo (mesa 12)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97029#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - cik_sdma_copy_texture broken on Carrizo (mesa 12)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97029">bug 97029</a>
from <span class="vcard"><a class="email" href="mailto:darktjm@gmail.com" title="Thomas J. Moore <darktjm@gmail.com>"> <span class="fn">Thomas J. Moore</span></a>
</span></b>
<pre>(In reply to Marek Olšák from <a href="show_bug.cgi?id=97029#c7">comment #7</a>)
<span class="quote">> Do you have the latest amdgpu firmware from
> <a href="http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git">http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git</a> ?</span >
Do you know of a specific change to a carrizo firmware image that fixes this
bug? Because if not, I will not spend effort updating it. A check against the
current git head shows that I am not running the latest carrizo_vce.bin, but
all others are up-to-date (including the ones suspiciously containing "sdma" in
the name). Unless you can verify that the vce image will magically fix this, I
won't try it until it gets included in an official gentoo linux-firmware
update. Even if it is a firmware revision issue, there should be barrier code
in the function to prevent old firmware from screwing up.
In the mean time, I strongly suggest disabling this function call entirely
before releasing yet another broken Mesa. Having random memory copies spray
bytes all over the place based on size and alignment is completely
unacceptable.</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>