| Bug ID | 108916 |
|---|---|
| Summary | polaris11 d3d9 rendering issue |
| Product | Mesa |
| Version | unspecified |
| Hardware | Other |
| OS | All |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | roman.elshin@gmail.com |
| QA Contact | dri-devel@lists.freedesktop.org |
Created attachment 142680= [details] corruption example System is ubuntu 16.04 with kernel 4.16.18 and oibaf ppa, wine-nine-staging-3.18 compiled from commendsarnex ppa. ~$ glxinfo |grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 560 Series (POLARIS11, DRM 3.23.0, 4.16.1= 8, LLVM 7.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.0-devel (git-37f9788 2018-11-30 xenial-oibaf-ppa) Using d3d9 nine course a visual problem, it looks like flickering noise. d3d9 trace from windows: https://drive.google.com/file/d/1CGd-CR5vQmwe4jy4Fsux-jDypJUHJP7-/v= iew
Hi, I just wanted to confirm the trace reproduces the issue, but it may not be a nine issue but a radeonsi llvm issue. The trace has no glitches on llvmpipe= .
I can't reproduce this on CIK (Kabini) using provided trace. So, this sounds like hardware specific bug somewhere, probably llvm.
I saw some reports with distortions which looks similar to thi= s and it was fixed in llvm-8. Installing llvm-8 from ht= tp://apt.llvm.org/ and recompiling libdrm + mesa from git does't solve this issue. $ glxinfo |grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 560 Series (POLARIS11, DRM 3.27.0, 4.19.9, LLVM 8.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.0-devel (git-8e9ad592c3)
> I can't reproduce this on CIK (Kabi= ni) using provided trace. > > So, this sounds like hardware specific bug somew= here, probably llvm. There are similar distorsions with verde (hd7770 with amdgpu), but it less noticeable there.
| What | Removed | Added |
|---|---|---|
| Resolution | --- | MOVED |
| Status | NEW | RESOLVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1344.