Comment 16 for bug 1848108

@kaihengfeng

Sorry about the delay. Life being distracting.

But it seems like the issue is /mostly/ fixed in the provided 2019-12-16 build and so far hasn't required me to hard shutdown which is good. What isn't particularly good is the occasional "freeze" where everything on screen stops for a few moments. Occasionally during these freezes, items that were occluded by something appeared in front of it instead, like desktop icons in front of Firefox with mild graphical glitching on a terminal window (tiling parts of a window somewhere else). It seems like the issue occurs when something even mildly graphically intensive (searching through a large webpage, alt-tabbing, etc.) will cause one of these freezes. I've even had it happen several times in a row before it finally recovered.

I did open journalctl -f and noted this:

Dec 16 16:12:29 DarkBolt kernel: [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out!
Dec 16 16:12:29 DarkBolt kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered
Dec 16 16:12:39 DarkBolt kernel: [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out!
Dec 16 16:12:39 DarkBolt kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered