Comment # 56
on bug 105733
from las@protonmail.ch
Also, forgot to mention, but the new GPU recovery thing doesn't work, and it
would make the following error in dmesg:
jan 16 16:43:26 las kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
sdma0 timeout, signaled seq=2792, emitted seq=2795
jan 16 16:43:26 las kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process
information: process pid 0 thread pid 0
jan 16 16:43:26 las kernel: amdgpu 0000:08:00.0: GPU reset begin!
jan 16 16:43:26 las kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, signaled seq=7013, emitted seq=7015
jan 16 16:43:26 las kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process
information: process sway pid 1328 thread sway:cs0 pid 1329
jan 16 16:43:26 las kernel: amdgpu 0000:08:00.0: GPU reset begin!
jan 16 16:43:26 las kernel: amdgpu: [powerplay]
failed to send message 261 ret is 0
jan 16 16:43:27 las kernel: amdgpu: [powerplay]
last message was failed ret is 0
jan 16 16:43:28 las kernel: amdgpu: [powerplay]
failed to send message 261 ret is 0
lines 955-1010/1010 (END)
(Fetched through `journalctl -ekb<boot ID>`)
This however stopped once I switched to DVI-D, since I now get no errors at
all.
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
