https://bugs.freedesktop.org/show_bug.cgi?id=97029

--- Comment #2 from Franklin Titus cygnix@openmailbox.org --- Created attachment 125260 --> https://bugs.freedesktop.org/attachment.cgi?id=125260&action=edit distorted screenshot image

https://bugs.freedesktop.org/show_bug.cgi?id=97029

--- Comment #4 from Thomas J. Moore darktjm@gmail.com --- Created attachment 125266 --> https://bugs.freedesktop.org/attachment.cgi?id=125266&action=edit xwud results

Sorry for the poor quality, late posting, and the reflections in the image. This is what the xwud output looks like. Notice the perfectly fine rxvt on the left (except for the blue crap in it; that was caused by xwud). The window in the middle is where xwud is supposed to put its output. Instead, it lays wide stripes to its right (far enough to reach around back to the left). Looks a lot like the stride and offset are wrong, but it also corrupts pixels in the top button bar. Also, I wanted to make it clear that this affects xv, ImageMagick-display, xpdf, and many other apps, not just some ancient screen capture program. The only thing keeping this from being a "major" issue is that it's easy to cure.

https://bugs.freedesktop.org/show_bug.cgi?id=97029

--- Comment #6 from Johannes Hirte johannes.hirte@datenkhaos.de --- Additional info here, as 97119 is a duplicate of this. The flickering happens even with R600_DEBUG=nodma. I don't even need to put the video to fullscreen. This time flickering was just starting with the video. I've seen similar flickering on a kabini system. Don't know, if this could be related. I've never seen this on r600 systems (cedar, sumo), so I don't think it's a KDE bug.

https://bugs.freedesktop.org/show_bug.cgi?id=97029

Thomas J. Moore darktjm@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |major

--- Comment #8 from Thomas J. Moore darktjm@gmail.com --- (In reply to Marek Olšák from comment #7)

Do you have the latest amdgpu firmware from http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git ?

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.

https://bugs.freedesktop.org/show_bug.cgi?id=97029

--- Comment #10 from Thomas J. Moore darktjm@gmail.com --- (In reply to Marek Olšák from comment #9)

Right now the plan is to disable SDMA texture copying for Carrizo on master and Mesa 12.0.

Fine by me. Just wanted to make sure it was taken care of before the next Mesa release, in case you decide to wait more than a month to respond again, given approx. 2 months between Mesa releases.

https://bugs.freedesktop.org/show_bug.cgi?id=97029

Marek Olšák maraeo@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED

--- Comment #12 from Marek Olšák maraeo@gmail.com --- SDMA texture copying was disabled on Carrizo by: 3ff0b67e1b6b492d5793c1580f4be0c6f58a1bc2

Closing.