Bug 1739766 - amd screen artifacts
Summary: amd screen artifacts
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-amdgpu
Version: 31
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Christopher Atherton
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-10 09:33 UTC by Łukasz Posadowski
Modified: 2020-11-24 15:22 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-11-24 15:22:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Photo of the screen. (72.26 KB, image/jpeg)
2019-08-10 09:33 UTC, Łukasz Posadowski
no flags Details
journalctl log from boot to reboot (724.67 KB, text/plain)
2020-01-19 08:18 UTC, Łukasz Posadowski
no flags Details
Photo of what I am seeing on my monitor (2.44 MB, image/jpeg)
2020-03-23 12:30 UTC, meltingrobot
no flags Details

Description Łukasz Posadowski 2019-08-10 09:33:19 UTC
Created attachment 1602426 [details]
Photo of the screen.

Description of problem:
Radeon is displaying artifacts on the screen. 
I have AMD RX 570.

Version-Release number of selected component (if applicable):
kernel-5.2.5-200.fc30.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Launch any resource hungry application (eg. Gnome, gdm, Euro Truck Simulator 2, etc...)
2. Wait about 2 seconds
3. Screen is full of artifacts.

Actual results:
I added photo of the monitor as an attachment.

Expected results:
No artifacts on the screen.

Additional info:
The system is perfectly usable in text mode, Lightdm is working, Fluxbox is working. It's crashing only when GPU goes to around 100% even for awhile.

Journald is logging:

sie 10 10:30:39 union kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!
sie 10 10:30:39 union kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=6201, emitted seq=6203
sie 10 10:30:39 union kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process steam pid 2926 thread steam:cs0 pid 2986
sie 10 10:30:39 union kernel: amdgpu 0000:01:00.0: GPU reset begin!
sie 10 10:30:41 union kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!
sie 10 10:30:41 union kernel: amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
sie 10 10:30:41 union kernel: [drm:gfx_v8_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed
sie 10 10:30:41 union kernel: cp is busy, skip halt cp
sie 10 10:30:41 union kernel: rlc is busy, skip halt rlc
sie 10 10:30:41 union kernel: amdgpu 0000:01:00.0: GPU pci config reset
sie 10 10:30:41 union kernel: amdgpu 0000:01:00.0: GPU reset succeeded, trying to resume
sie 10 10:30:41 union kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400900000).
sie 10 10:30:41 union kernel: [drm] VRAM is lost due to GPU reset!
sie 10 10:30:41 union kernel: [drm] SADs count is: 0, don't need to read it
sie 10 10:30:41 union kernel: [drm] UVD and UVD ENC initialized successfully.
sie 10 10:30:41 union kernel: [drm] VCE initialized successfully.
sie 10 10:30:41 union kernel: [drm] recover vram bo from shadow start
sie 10 10:30:41 union kernel: [drm] recover vram bo from shadow done
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: amdgpu 0000:01:00.0: GPU reset(2) succeeded!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm] Skip scheduling IBs!
sie 10 10:30:41 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:41 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:41 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:41 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:41 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:41 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:41 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:41 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:41 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:41 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:41 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:41 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:41 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:41 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:42 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:30:46 union systemd[1]: dbus-com.deepin.dde.lockservice.service: Succeeded.
sie 10 10:30:46 union audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-com.deepin.dde.lockservice comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sie 10 10:31:00 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:31:00 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:31:00 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:31:00 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:32:00 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:32:00 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:32:00 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
sie 10 10:32:00 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
^C
----------------------------------------------------------

I can use the system by ssh in and ewerything (besided AMD gpu) is working fine. I still can hear music from the game.

I tried to modify /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/power_dpm_force_performance_level to high before X starts, but it doesn't help.

If I unplug Radeon card from the power supply and use integrated Intel graphics, everything is back to normal.

# lspci
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]


------------------------------------

Some additional links with similar problems:

https://bugs.freedesktop.org/show_bug.cgi?id=108096
https://bugs.freedesktop.org/show_bug.cgi?id=108493
https://dri-devel.freedesktop.narkive.com/Mo86sj7v/bug-91880-radeonsi-on-grenada-cards-r9-390-exceptionally-unstable-and-poorly-performing


Thanks for any help.
Łukasz

Comment 1 Łukasz Posadowski 2019-08-10 09:43:41 UTC
A little more informative lspci

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef) (prog-if 00 [VGA controller])
	Subsystem: ASUSTeK Computer Inc. Device 051b
	Flags: bus master, fast devsel, latency 0, IRQ 38
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Memory at f0000000 (64-bit, prefetchable) [size=2M]
	I/O ports at e000 [size=256]
	Memory at f7d00000 (32-bit, non-prefetchable) [size=256K]
	Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: [48] Vendor Specific Information: Len=08 <?>
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Legacy Endpoint, MSI 00
	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Capabilities: [150] Advanced Error Reporting
	Capabilities: [200] Resizable BAR <?>
	Capabilities: [270] Secondary PCI Express <?>
	Capabilities: [2b0] Address Translation Service (ATS)
	Capabilities: [2c0] Page Request Interface (PRI)
	Capabilities: [2d0] Process Address Space ID (PASID)
	Capabilities: [320] Latency Tolerance Reporting
	Capabilities: [328] Alternative Routing-ID Interpretation (ARI)
	Capabilities: [370] L1 PM Substates
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

Comment 2 Łukasz Posadowski 2019-08-13 04:25:11 UTC
I have some more details. When I boot in multiuser target and change performance to low, by :

# echo 'low' > /sys/class/drm/card0/device/power_dpm_force_performance_level

and then isolate grapgical target, I am able to run X, Wayland, Gnome and games almost without a problem. It still crashed 2 times during 2 day testing period, but it is a progress.

Comment 3 Łukasz Posadowski 2019-08-25 14:25:42 UTC
I found exactly the same problem as mine and it is supposed to be fixed since Kernel 5.0.

https://bugs.freedesktop.org/show_bug.cgi?id=108493

Basically, voltage on vram is too low and the card can't operate at ~100% load. Voltage can be set manually (which is described here: https://wiki.archlinux.org/index.php/AMDGPU#Overclocking ). I'm not sure I could manually edit those settings without overheating and damaging the memory, which essentially would break the card.

Fedora has Kernel 5.2 and the fix is not working apparently.

Comment 4 Sebastian Dato 2019-09-29 15:37:55 UTC
I am running fedora 30 in my workstation, Radeon RX 580, and I started to experience the problem with kernel 5.2. Fedora 30 with kernels prior to 5.2 never had the problem, same as Ubuntu 19.04 with kernel 5.0, no problems. I did a manual kernel upgrade to 5.3.0-1.fc31.x86_64 and I haven't had the problem anymore.

Comment 5 Łukasz Posadowski 2019-09-29 15:50:25 UTC
Thank You for at least bringing a hope. :) I already unplugged the card from the motherboard, but already miss 2 hdmi outputs. Since i don't use any 3rd party kernel modules, I give 5.3 a try, too.

Comment 6 Łukasz Posadowski 2019-10-05 09:59:10 UTC
Indeed there is an improvement. On Fedora 31 with Kernel 5.3 Gnome runs fine. When I launch steam client the card craps out, display rainbow colours on the screen (similar to the attached image), but I see mouse moving. I don't have more time this weekend, but I will check it next week.

Comment 7 Łukasz Posadowski 2020-01-19 08:18:37 UTC
Created attachment 1653536 [details]
journalctl log from boot to reboot

I know this is a huge file, search for "GPU reset".

Comment 8 Łukasz Posadowski 2020-01-19 08:22:53 UTC
I attached full journald log from boot to reboot with RX 570 card. I know it is huge file, search for "GPU reset". It happens exactly when GPU is used for ~100% (the moment of Gnome desktop starting, or any game under less demanding desktop, like Fluxbox, for example Battletech, of Euro Truck Simulator 2). 

It's on Kernel 5.4 now:
Linux union 5.4.10-200.fc31.x86_64 #1 SMP Thu Jan 9 19:58:12 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Comment 9 meltingrobot 2020-03-04 13:15:49 UTC
I get something similar, but it's not the entire screen, but rather a small section of one of my monitors.  I'm on an RX580 I believe.  If I take a screenshot of the area, the garbage doesn't appear in the screenshot.

Comment 10 Łukasz Posadowski 2020-03-15 07:52:11 UTC
Thank You. :) I was wondering if my card is broken. Could you post a photo of the screen? Or paste journal logs with line similar to

Jan 19 08:52:59 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Jan 19 08:52:59 union kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Jan 19 08:52:59 union gnome-shell[2155]: amdgpu: The CS has been cancelled because the context is lost.

Comment 11 Łukasz Posadowski 2020-03-19 16:42:19 UTC
I', trying with every new Kernel, so it is time for kernel-5.6.0-0.rc5.git0.2.fc32.x86_64 from Fedora 32:

This is a grep of amdgpu from journal

mar 19 17:16:03 union kernel: [drm] amdgpu kernel modesetting enabled.
mar 19 17:16:03 union kernel: fb0: switching to amdgpudrmfb from EFI VGA
mar 19 17:16:03 union kernel: amdgpu 0000:01:00.0: vgaarb: deactivate vga console
mar 19 17:16:03 union kernel: amdgpu 0000:01:00.0: No more image in the PCI ROM
mar 19 17:16:03 union kernel: amdgpu 0000:01:00.0: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used)
mar 19 17:16:03 union kernel: amdgpu 0000:01:00.0: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
mar 19 17:16:03 union kernel: [drm] amdgpu: 4096M of VRAM memory ready
mar 19 17:16:03 union kernel: [drm] amdgpu: 4096M of GTT memory ready.
mar 19 17:16:04 union kernel: amdgpu: [powerplay] hwmgr_sw_init smu backed is polaris10_smu
mar 19 17:16:04 union kernel: snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
mar 19 17:16:04 union kernel: fbcon: amdgpudrmfb (fb0) is primary device
mar 19 17:16:04 union kernel: amdgpu 0000:01:00.0: fb0: amdgpudrmfb frame buffer device
mar 19 17:16:04 union kernel: [drm] Initialized amdgpu 3.36.0 20150101 for 0000:01:00.0 on minor 1
mar 19 17:16:26 union /usr/libexec/gdm-x-session[2930]:         loading driver: amdgpu
mar 19 17:16:26 union /usr/libexec/gdm-x-session[2930]: (==) Matched amdgpu as autoconfigured driver 0
mar 19 17:16:26 union /usr/libexec/gdm-x-session[2930]: (II) LoadModule: "amdgpu"
mar 19 17:16:26 union /usr/libexec/gdm-x-session[2930]: (II) Loading /usr/lib64/xorg/modules/drivers/amdgpu_drv.so
mar 19 17:16:26 union /usr/libexec/gdm-x-session[2930]: (II) Module amdgpu: vendor="X.Org Foundation"
mar 19 17:16:26 union /usr/libexec/gdm-x-session[2930]:         All GPUs supported by the amdgpu kernel driver
mar 19 17:16:30 union kernel: amdgpu 0000:01:00.0: GPU fault detected: 147 0x09fa1002 for process gnome-shell pid 3204 thread gnome-shel:cs0 pid 3216
mar 19 17:16:30 union kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0010653F
mar 19 17:16:30 union kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03010002
mar 19 17:16:30 union kernel: amdgpu 0000:01:00.0: VM fault (0x02, vmid 1, pasid 32774) at page 1074495, write from 'CB3' (0x43423300) (16)
mar 19 17:16:30 union kernel: amdgpu 0000:01:00.0: GPU fault detected: 147 0x08ca1002 for process gnome-shell pid 3204 thread gnome-shel:cs0 pid 3216
mar 19 17:16:30 union kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00105FF2
mar 19 17:16:30 union kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03010014
mar 19 17:16:30 union kernel: amdgpu 0000:01:00.0: VM fault (0x14, vmid 1, pasid 32774) at page 1073138, write from 'CB3' (0x43423300) (16)
mar 19 17:16:35 union kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
mar 19 17:16:36 union kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
mar 19 17:16:41 union kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
mar 19 17:16:41 union kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=283, emitted seq=284
mar 19 17:16:41 union kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 3204 thread gnome-shel:cs0 pid 3216
mar 19 17:16:41 union kernel: amdgpu 0000:01:00.0: GPU reset begin!
mar 19 17:16:41 union kernel: amdgpu 0000:01:00.0: GPU BACO reset
mar 19 17:16:41 union kernel: amdgpu 0000:01:00.0: GPU reset succeeded, trying to resume
mar 19 17:16:42 union kernel: amdgpu 0000:01:00.0: GPU reset(2) succeeded!
mar 19 17:16:42 union gnome-shell[3204]: amdgpu: amdgpu_cs_query_fence_status failed.
mar 19 17:16:42 union gnome-shell[3204]: amdgpu: amdgpu_cs_query_fence_status failed.
mar 19 17:16:42 union gnome-shell[3204]: amdgpu: amdgpu_cs_query_fence_status failed.

It survived GDM, but crashed as soon as Gnome started. I'm postiing it just because those errors are different than previous ones: Failed to initalize parser is missing. The card is, as usual, trying to reset itself and fails.

Comment 12 meltingrobot 2020-03-23 12:30:46 UTC
Created attachment 1672677 [details]
Photo of what I am seeing on my monitor

Again, my system doesn't crash due to this it seems.  I'm just stuck with it until I reboot next.  If I take a screenshot, it doesn't show in the screenshot at all.  I had to manually take a picture with my phone.

Comment 13 meltingrobot 2020-04-02 12:29:36 UTC
Also, not sure if related, but I sometimes get a phantom cursor after unlocking the screen.  I may need to open a separate ticket for that though.

Comment 14 meltingrobot 2020-04-02 12:31:43 UTC
Actually, the phantom cursor just turned into the spot where the awful red box appeared.  So, it may actually be related.

Comment 15 meltingrobot 2020-04-03 12:51:01 UTC
Today, it managed to appear on three out of the four monitors in the same space in the lower right corner.

Comment 16 meltingrobot 2020-04-10 23:54:36 UTC
Update, today I renamed my home directory and let a new one be created for me.  So far, no screen artifacts or hangups.  I wonder if something in the Gnome settings was unhappy since I upgraded originally from Fedora 30 to 31 and now to 32.  I am going to wait a couple of days also before adding back in the one or two Gnome extensions I use.  It might be one of them.

Comment 17 meltingrobot 2020-04-12 16:33:36 UTC
I spoke too soon.  It returned today.  :(

Comment 18 Łukasz Posadowski 2020-04-12 17:35:01 UTC
> I spoke too soon.  It returned today.  :(

It is The worst thing about it. Sometimes think I got this figured out and 4 days later is happens again. :)

Comment 19 meltingrobot 2020-04-14 15:11:54 UTC
I switched out the RX590 for an old HD7850 today.  Will see if that fixes things for me.  If so, then that sucks because I would rather not use an ancient video card.  But with working from home full time, I need something I can rely on not rebooting me in the middle of a meeting or working on a server remotely.

Comment 20 Łukasz Posadowski 2020-04-14 15:24:55 UTC
Thanks. let us know if it helped. It yes, I would consider bigger power supply, but it is another expense and shot in the dark.

Comment 21 meltingrobot 2020-04-14 17:26:23 UTC
Probably too early to tell, but so far today since I changed the graphics card out, I have not had a stuck mouse pointer, weird graphic block, or surprise reboot/hang.  If I make it a few days, then I will definitely believe the issue is with the amd_gpu driver for the RX590 card.

Comment 22 meltingrobot 2020-04-15 14:41:17 UTC
So far, day 2 with no graphical issues.  Also, as a disclaimer, I removed my wireless card also when I switched out the video card.  I really don't think it was that, but I just wanted to add that information as well.

Comment 23 meltingrobot 2020-04-20 17:04:35 UTC
Yeah, still no graphical issues when using the 7850.  It sucks because obviously, the RX590 is a much newer/better card.  But at this point, I need my home workstation to stay running.

Comment 24 meltingrobot 2020-04-22 12:27:10 UTC
Been a full week now with zero graphical glitches since switching out the card.  So, definitely something to do with the amd_gpu driver and the RX500 cards I am guessing.

Comment 25 Ben Cotton 2020-11-03 17:03:25 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 26 meltingrobot 2020-11-03 21:19:38 UTC
I haven't had this issue in awhile on F33.  I think we can close this issue for now.

Comment 27 Ben Cotton 2020-11-24 15:22:48 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.