| Bug ID | 97029 |
|---|---|
| Summary | cik_sdma_copy_texture broken on Carrizo (mesa 12) |
| Product | Mesa |
| Version | git |
| Hardware | Other |
| OS | All |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | darktjm@gmail.com |
| QA Contact | dri-devel@lists.freedesktop.org |
Created attachment 125240 [details]
xwd output with bug
Mesa 12 corrupts large image displays in X on my hardware, using
xf86-video-amdgpu 1.1.0 (glamor). To reproduce, xwd | xwud. The xwd captu=
re
is garbled (see attached), and xwud sprays the garbled mess in disconnected
chunks to its right. I noticed this in pre-12 git as well, but didn't repo=
rt
because I have limited net access and limited machine availability and hoped
someone better equipped would discover and deal with it. The commit which
caused this is 70934de00eb42ba6fc43d104875962dfb260a1b3. Removing the call=
to
cik_sdma_copy_texture "fixes" it. This was observed on two diffe=
rent machines,
but similar hardware (A10 Carrizo). Verfied still broken as of
4f89cf4941db0a5cd8a85b943121840000cf8e4f.
This could be related to the GPUVM faults discussed in this ma= iling list thread: https://lists.freedesktop.org/archives/amd-gfx/2016-June/0000= 47.html
Created attachment 12=
5260 [details]
distorted screenshot image
I have similar issue since upgrading to Mesa 12 on the same AM= D hardware (A10 Carrizo). See attachment.
Created attachment 125266 =
[details]
xwud results
Sorry for the poor quality, late posting, and the reflections in the image.=
=20
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 w=
ide
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.
| What | Removed | Added |
|---|---|---|
| CC | johannes.hirte@datenkhaos.de |
*** Bug 97119 has been marked as a dupl= icate of this bug. ***
Additional info here, as 97119 is a duplicate of this. The fli=
ckering happens
even with R600_DEBUG=3Dnodma. I don't even need to put the video to fullscr=
een.
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 n=
ever
seen this on r600 systems (cedar, sumo), so I don't think it's a KDE bug.
Do you have the latest amdgpu firmware from http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmwar= e.git ?
| What | Removed | Added |
|---|---|---|
| Severity | normal | major |
(In reply to Marek Ol=C5=A1=C3=A1k from comment #7) > Do you have the latest amdgpu firmware from > http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-fi= rmware.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 thi= s, 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 c= ode 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.
If I had known about the issue, we wouldn't have committed the= change. Right now the plan is to disable SDMA texture copying for Carrizo on master= and Mesa 12.0.
(In reply to Marek Ol=C5=A1=C3=A1k from comment #9) > Right now the plan is to disable SDMA texture co= pying 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, giv= en approx. 2 months between Mesa releases.
(In reply to Johannes Hirte from comment #6) > The flickering happens even with R600_DEBUG=3Dno= dma. The flickering should be tracked separately from this report then. Feel fre= e to re-open bug 97119 for that, but you'll need= to provide more information about the flickering.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | FIXED |
SDMA texture copying was disabled on Carrizo by: 3ff0b67e1b6b492d5793c1580f4be0c6f58a1bc2 Closing.