http://imgur.com/a/4JS4S hard to articulate, just whats going on, but a picture is worth many words. using: [plague@Ookami ~]$ uname -a Linux Ookami 4.11.3-1-ARCH #1 SMP PREEMPT Sun May 28 10:40:17 CEST 2017 x86_64 GNU/Linux mesa 17 xorg 1.19 and latest xf86-video-amdgpu [plague@Ookami ~]$ glxinfo -B name of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: X.Org (0x1002) Device: AMD OLAND (DRM 3.10.0 / 4.11.3-1-ARCH, LLVM 4.0.0) (0x6613) Version: 17.1.1 Accelerated: yes Video memory: 2019MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD OLAND (DRM 3.10.0 / 4.11.3-1-ARCH, LLVM 4.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.1.1 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 3.0 Mesa 17.1.1 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.1.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 lspci: https://pastebin.com/rfPYgxsh xorg log: https://pastebin.com/L7nhRhib full glxinfo: https://pastebin.com/k77Wd8zw
Looks like https://bugzilla.kernel.org/show_bug.cgi?id=194761 , can you try the latest patch attached there? P.S. In the future, please attach files here directly instead of linking to external sites (especially pastebins).
-- 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/drm/amd/issues/185.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.