Comment # 110
on bug 111481
from Sebastian Meyer
Created attachment 145773 [details]
umr output after sdma0 timeout
Another random sdma0 timeout while using kernel
drm.fixes.5.4.2019.10.16.r0.gd12c50857c6e-1 with all mentioned patches applied
(one of them already included on the drm-fixes branch). This time I didn't
forget about the umr debug output, but I'm not sure if it's even relevant
anymore considering the number of already submitted reports.
The system freeze happened after working with WebStorm and SmartGit for roughly
10 minutes on KDE Plasma while scrolling in one of the application's windows.
[39816.999159] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for
fences timed out!
[39816.999298] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for
fences timed out!
[39821.905604] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout,
signaled seq=3360854, emitted seq=3360856
[39821.905718] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process Xorg pid 717 thread Xorg:cs0 pid 718
[39821.905720] [drm] GPU recovery disabled.
I would really appreciate it if AMD and the AMDGPU devs could focus on fixing
these major stability issues of their now almost 4 months old mainstream
consumer GPUs. I'm sorry if this sounds harsh, but the hardware has been
advertised with Linux support and it's clearly unusable. This needs to be fixed
as soon as possible. Thank you!
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
