[Bug 111481] AMD Navi GPU frequent freezes on both Manjaro/Ubuntu with kernel 5.3 and mesa 19.2 -git/llvm9

[bugzilla-daemon at freedesktop.org]

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

--- Comment #115 from Mark Dietzer <freedesktop at doridian.net> ---
For me it seems to happen commonly when I watch 60fps video (YouTube) using
Firefox on my RX 5700 XT (currently on Fedora 31 with latest distro packages).
Even 4K video at 30fps does not seem to cause any issues.

I have not yet managed to reproduce the hang in gaming or benchmark use (no
matter if OpenGL or Vulkan)

The first time this happened today it was accompanied by the following kernel
messages and led to a full lockup of graphics until reboot:
amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb, param 0x80
amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb param 0x80
amdgpu: [powerplay] Failed to export SMU metrics table!
amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb, param 0x80
amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb param 0x80
amdgpu: [powerplay] Failed to export SMU metrics table!
amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb, param 0x80
amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb param 0x80
amdgpu: [powerplay] Failed to export SMU metrics table!
amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb, param 0x80
amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb param 0x80
amdgpu: [powerplay] Failed to export SMU metrics table!
amdgpu: [powerplay] Failed to send message 0x36, response 0xfffffffb, param 0x0
amdgpu: [powerplay] Failed to send message 0x36, response 0xfffffffb param 0x0
amdgpu: [powerplay] [smu_v11_0_get_power_limit] get PPT limit failed!
amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb, param 0x80
amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb param 0x80
amdgpu: [powerplay] Failed to export SMU metrics table!
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled
seq=202333, emitted seq=202336
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0
thread  pid 0

The second time, it was only a short (few seconds) hang and yielded the
following kernel output, currently still up and running after that message:
[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed
out or interrupted!

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20191020/d1c71ff0/attachment.html>