| Bug ID | 105910 |
|---|---|
| Summary | Graphical artifacts on unresposible surfaces on AMD Radeon RX= 570 |
| Product | Mesa |
| Version | 17.3 |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | nb@chebykin.org |
| QA Contact | dri-devel@lists.freedesktop.org |
Created attachment 138627 [details]
Example of artifacts
Hello,
I want to report some graphical artifacts with AMD Radeon RX 570 card.
I've been noticing some random artifacts when I open/resize/close windows.
I was able to narrow down this problem to mesa surfaces updating. For insta=
nce
if i suspend program with such surface and try to resize it, I will see the=
se
artifacts. So I think there is a moment between receiving resize event and
updating surface when driver somehow render those artifacts.
I'm using Arch Linux with i3, but I was able to reproduce this bug on wayla=
nd
by resizing alacritty terminal emulator.
Versions:
Kernel:
4.15.14-1-ARCH
Mesa:
libva-mesa-driver 17.3.7-1
mesa 17.3.7-1
mesa-vdpau 17.3.7-1
xf86-video-amdgpu 18.0.1-1
Created attachm=
ent 138628 [details]
Artifacts when window is opening
Created attachment 138629 [details]
Xeyes render artifacts instead of background
Created attachment 138630 [details]
dmesg full log
Created attachment 138631 [details]<=
/a>
glxinfo
Created attachment 138632 [detai=
ls]
Xorg log
| What | Removed | Added |
|---|---|---|
| Summary | Graphical artifacts on unresposible surfaces on AMD Radeon R= X 570 | Graphical artifacts on unresponsible surfaces on AMD Radeon = RX 570 |
| What | Removed | Added |
|---|---|---|
| QA Contact | dri-devel@lists.freedesktop.org | |
| Version | 17.3 | DRI git |
| Product | Mesa | DRI |
| Component | Drivers/Gallium/radeonsi | DRM/AMDgpu |
I think it's not just mesa, but some drivers issue.
Also still happens on linux 4.16 and mesa 18.0.2.
| What | Removed | Added |
|---|---|---|
| Severity | normal | major |
I'm also having graphical artifacts with i3. I have an amd rx = 580. Here's a thread with the issues I was getting: https://bbs= .archlinux.org/viewtopic.php?id=3D242727 I have also tried taking out my rx 580 card out of my computer and uninstal= led AMDGPU and tried running i3 through my iGPU, i7-7700k CPU. I still had graphical artifacts when I tried that. Here is a vid of the artifacting: https://streamable.com/yg3us https://my.mixtape.moe/bdxwtc= .ogv
| What | Removed | Added |
|---|---|---|
| Attachment #138632 mime type | text/x-log | text/plain |
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | NOTOURBUG |
At least with xeyes, this is expected with i3, see htt= ps://github.com/i3/i3/issues/2742#issuecomment-433304928 and later comm= ents. I suspect it could be similar with VirtualBox. The issue with alacritty on Wayland is probably different, maybe in Xwaylan= d, or if it uses the Wayland protocol directly, maybe one of the known issues described on https://github.= com/jwilm/alacritty =3D> https://github.com/t= omaka/winit/issues/306 . Anyway, I don't see clear evidence of a driver bug here.
Things are increasingly pointing to this being an i3 bug. It c= reates a cairo surface with cairo_xcb_surface_create and copies from that to its parent window. But according to /usr/include/cairo/cairo.h, cairo doesn't initiali= ze the contents of a surface created with cairo_xcb_surface_create, so i3 need= s to initialize them explicitly.