From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 111481] AMD Navi GPU frequent freezes on both Manjaro/Ubuntu with kernel 5.3 and mesa 19.2 -git/llvm9 Date: Mon, 21 Oct 2019 01:24:42 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0097682014==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 1DB0C89913 for ; Mon, 21 Oct 2019 01:24:43 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0097682014== Content-Type: multipart/alternative; boundary="15716210831.e1ce.29043" Content-Transfer-Encoding: 7bit --15716210831.e1ce.29043 Date: Mon, 21 Oct 2019 01:24:43 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D111481 --- Comment #117 from Daniel Suarez --- (In reply to Mark Dietzer from comment #115) > For me it seems to happen commonly when I watch 60fps video (YouTube) usi= ng > 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. >=20 > I have not yet managed to reproduce the hang in gaming or benchmark use (= no > matter if OpenGL or Vulkan) >=20 > 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, par= am > 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=3D202333, emitted seq=3D202336 > [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process = pid > 0 thread pid 0 >=20 > The second time, it was only a short (few seconds) hang and yielded the > following kernel output, currently still up and running after that messag= e: > [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences ti= med > out or interrupted! Test out kernel 5.4rc4, it should have addressed this I believe. --=20 You are receiving this mail because: You are the assignee for the bug.= --15716210831.e1ce.29043 Date: Mon, 21 Oct 2019 01:24:43 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comm= ent # 117 on bug 11148= 1 from Daniel Suarez 
(In reply to Mark Dietzer from comment #115)
> 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.
>=20
> I have not yet managed to reproduce the hang in gaming or benchmark us=
e (no
> matter if OpenGL or Vulkan)
>=20
> 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, p=
aram
> 0x80
> amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb pa=
ram
> 0x80
> amdgpu: [powerplay] Failed to export SMU metrics table!
> amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb, p=
aram
> 0x80
> amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb pa=
ram
> 0x80
> amdgpu: [powerplay] Failed to export SMU metrics table!
> amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb, p=
aram
> 0x80
> amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb pa=
ram
> 0x80
> amdgpu: [powerplay] Failed to export SMU metrics table!
> amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb, p=
aram
> 0x80
> amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb pa=
ram
> 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 p=
aram
> 0x0
> amdgpu: [powerplay] [smu_v11_0_get_power_limit] get PPT limit failed!
> amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb, p=
aram
> 0x80
> amdgpu: [powerplay] Failed to send message 0xe, response 0xfffffffb pa=
ram
> 0x80
> amdgpu: [powerplay] Failed to export SMU metrics table!
> [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled
> seq=3D202333, emitted seq=3D202336
> [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: proces=
s  pid
> 0 thread  pid 0
>=20
> The second time, it was only a short (few seconds) hang and yielded the
> following kernel output, currently still up and running after that mes=
sage:
> [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences=
 timed
> out or interrupted!

Test out kernel 5.4rc4, it should have addressed this I believe.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15716210831.e1ce.29043-- --===============0097682014== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0097682014==--