Comment # 177 on bug 111481 from
I'm still getting freezes when using Nemo with the same sdma0 timeout, on
latest Manjaro 5.4 rc4 kernel built from latest PKGBUILD (which included the
sdma0 fix commits) and after applying the sdma_read_delay patch.

Additionally, I discovered that changing system icon themes on Cinnamon can
also trigger the freeze. Error codes are the same (ring sdma0 timeout).

Additionally, before this, last night I was able to generate a sdma1 error when
browsing with Chromium. This time it states chromium instead of Xorg as process
caused the ring timeout:

kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences
timed out!
kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled
seq=2140606, emitted seq=2140608
kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process
chromium pid 39450 thread chromium:cs0 pid 39509

It seems in all occurrences, the differences between emitted and signaled
values are always 2.

Is there any process regarding this issue? Or is there any more information
needed (and how to enable verbose logs in the system regarding amdgpu and
related parts)?


You are receiving this mail because: