https://bugs.freedesktop.org/show_bug.cgi?id=107095
Bug ID: 107095 Summary: Artifacts in X sessions, GPU fault 147 Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: andrewd18@gmail.com
Created attachment 140442 --> https://bugs.freedesktop.org/attachment.cgi?id=140442&action=edit dmesg
I purchased a new "MSI Radeon RX 580 Armor MK2 8G OC" this week. I am getting intermittend visual artifacts on some windows, but not others.
Arch Linux
linux 4.17.3-1 mesa 18.1.3-1 xf86-video-amdgpu 18.0.1-2 xorg-server 1.20.0-9
When I play games, the card performs admirably. No artifacting, no stutter. I've tripled-to-quadrupled my FPS, so accelleration works great. Where I'm having problems is on GUIs.
Text and GUI elements often show squares or lines. The color of the squares or lines are the color of the window or desktop below the active window. When I move or force a redraw on the active window, the squares/lines disappear or reappear in a new place on the active window. It occurs regularly in Firefox, xterm, Konsole, and kdesu4 permission popups.
The problem occurs both when I am running only GUIs, and when I am running games and GUIs simultaneously, so I don't think it's a power state issue.
To narrow down if it was Plasma or not, I rebooted and started Fluxbox. I started only xterms, ran some commands, and got no errors whatsoever. Then I started moving them around the screen. That's when I got this in my dmesg:
[ 200.335982] amdgpu 0000:01:00.0: GPU fault detected: 147 0x0508c402 [ 200.335986] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000FFAA1 [ 200.335988] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A0C4002 [ 200.335991] amdgpu 0000:01:00.0: VM fault (0x02, vmid 5, pasid 32768) at page 1047201, read from 'TC3' (0x54433300) (196)
From then on, artifacts appeared on all windows per usual. Gaming and heavy 3D
remained unaffected.
Should I RMA the card, or is this likely a software stack bug and I should wait for more Mesa/Kernel updates?
Please let me know if I can provide more information. Thanks!
https://bugs.freedesktop.org/show_bug.cgi?id=107095
--- Comment #1 from Andrew Dorney andrewd18@gmail.com --- Created attachment 140443 --> https://bugs.freedesktop.org/attachment.cgi?id=140443&action=edit lspci
https://bugs.freedesktop.org/show_bug.cgi?id=107095
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #140442|text/x-log |text/plain mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=107095
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- QA Contact| |dri-devel@lists.freedesktop | |.org Component|DRM/AMDgpu |Drivers/Gallium/radeonsi Product|DRI |Mesa
https://bugs.freedesktop.org/show_bug.cgi?id=107095
--- Comment #2 from Andrew Dorney andrewd18@gmail.com --- Created attachment 140457 --> https://bugs.freedesktop.org/attachment.cgi?id=140457&action=edit Xorg log
Log lasts 6 seconds, GPU Fault occurs at 123s into this log (that is, X doesn't report any issues).
https://bugs.freedesktop.org/show_bug.cgi?id=107095
Andrew Dorney andrewd18@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #140442|0 |1 is obsolete| |
--- Comment #3 from Andrew Dorney andrewd18@gmail.com --- Created attachment 140458 --> https://bugs.freedesktop.org/attachment.cgi?id=140458&action=edit dmesg
Updated dmesg from 2018-07-03. VM Fault occurs at 123s, in Fluxbox. I started Firefox around 120s which is the easiest way to get the crash.
https://bugs.freedesktop.org/show_bug.cgi?id=107095
--- Comment #4 from kyle.devir@mykolab.com --- You aren't alone.
I get the wonderful "GPU fault detected: 147" error with dolphin-emu. Turns out that using mogrify with OpenCL backend causes lockups also. Anything OpenCL-related in fact.
Frustrating and annoying.
I bet the devs are trying to find a solution, for months, but have had trouble narrowing down this strange bug, or a related set of bugs.
https://bugs.freedesktop.org/show_bug.cgi?id=107095
--- Comment #5 from Andrew Dorney andrewd18@gmail.com --- This is still occurring as of today using:
linux 4.18.6.arch1-1 mesa 18.2.0-1 xf86-video-amdgpu 18.0.1-2 xorg-server 1.20.1-1
Same error messages in dmesg.
https://bugs.freedesktop.org/show_bug.cgi?id=107095
--- Comment #6 from keramidasceid@gmail.com --- Same problem here.
kernel 4.18.14 mesa 18.0.5
https://bugs.freedesktop.org/show_bug.cgi?id=107095
GitLab Migration User gitlab-migration@fdo.invalid changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #7 from GitLab Migration User gitlab-migration@fdo.invalid --- -- 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/1319.
dri-devel@lists.freedesktop.org