From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 11 Mar 2019 11:27:10 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1602009167==" 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 B0E848999C for ; Mon, 11 Mar 2019 11:27:10 +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 --===============1602009167== Content-Type: multipart/alternative; boundary="15523036301.daFF0B70D.5060" Content-Transfer-Encoding: 7bit --15523036301.daFF0B70D.5060 Date: Mon, 11 Mar 2019 11:27:10 +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=3D109955 Michel D=C3=A4nzer changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop |org |.org Component|Mesa core |Drivers/Gallium/radeonsi QA Contact|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop |org |.org --=20 You are receiving this mail because: You are the assignee for the bug.= --15523036301.daFF0B70D.5060 Date: Mon, 11 Mar 2019 11:27:10 +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 = Michel D=C3=A4nzer changed bug 10995= 5
What Removed Added
Assignee mesa-dev@lists.freedesktop.org dri-devel@lists.freedesktop.org
Component Mesa core Drivers/Gallium/radeonsi
QA Contact mesa-dev@lists.freedesktop.org dri-devel@lists.freedesktop.org

You are receiving this mail because:
  • You are the assignee for the bug.
= --15523036301.daFF0B70D.5060-- --===============1602009167== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1602009167==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Fri, 22 Mar 2019 20:01:01 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1650250124==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2C75189A7A for ; Fri, 22 Mar 2019 20:01:01 +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 --===============1650250124== Content-Type: multipart/alternative; boundary="15532848611.9EBcddD6.8578" Content-Transfer-Encoding: 7bit --15532848611.9EBcddD6.8578 Date: Fri, 22 Mar 2019 20:01:01 +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=3D109955 --- Comment #1 from Mauro Gaspari --- Created attachment 143759 --> https://bugs.freedesktop.org/attachment.cgi?id=3D143759&action=3Dedit syslog lines relevant to the crash --=20 You are receiving this mail because: You are the assignee for the bug.= --15532848611.9EBcddD6.8578 Date: Fri, 22 Mar 2019 20:01:01 +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

Commen= t # 1 on bug 10995= 5 from = Mauro Gaspari 
Created attac=
hment 143759 [details]
syslog lines relevant to the crash

You are receiving this mail because:
  • You are the assignee for the bug.
= --15532848611.9EBcddD6.8578-- --===============1650250124== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1650250124==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Fri, 22 Mar 2019 20:02:04 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1798159360==" 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 0002A6E332 for ; Fri, 22 Mar 2019 20:02:03 +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 --===============1798159360== Content-Type: multipart/alternative; boundary="15532849230.E8c57.8601" Content-Transfer-Encoding: 7bit --15532849230.E8c57.8601 Date: Fri, 22 Mar 2019 20:02:03 +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=3D109955 --- Comment #2 from Mauro Gaspari --- Created attachment 143760 --> https://bugs.freedesktop.org/attachment.cgi?id=3D143760&action=3Dedit full dmesg after crash --=20 You are receiving this mail because: You are the assignee for the bug.= --15532849230.E8c57.8601 Date: Fri, 22 Mar 2019 20:02:03 +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

You are receiving this mail because:
  • You are the assignee for the bug.
= --15532849230.E8c57.8601-- --===============1798159360== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1798159360==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Fri, 22 Mar 2019 20:02:15 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0326097593==" 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 5AA006E3B7 for ; Fri, 22 Mar 2019 20:02:15 +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 --===============0326097593== Content-Type: multipart/alternative; boundary="15532849351.CBF2dF2.8601" Content-Transfer-Encoding: 7bit --15532849351.CBF2dF2.8601 Date: Fri, 22 Mar 2019 20:02:15 +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=3D109955 --- Comment #3 from Mauro Gaspari --- New reports as the issue is still happening: I found a link on phoronix that describes with pictures exactly what is happening: https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/open-sou= rce-amd-linux/1049483-amd-devs-error-ring-gfx-timeout OS: OpenSUSE tumbleweed x86_64 updated (2019 03 23) Kernel: 5.0.2-1-default Desktop Environment: KDE Plasma (x11) OpenGL version: string: 4.5 (Compatibility Profile) Mesa 19.0.0 GPU: AMD Radeon RX Vega 64 8GB Attaching log files and dmesg after crash. --=20 You are receiving this mail because: You are the assignee for the bug.= --15532849351.CBF2dF2.8601 Date: Fri, 22 Mar 2019 20:02:15 +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

Commen= t # 3 on bug 10995= 5 from = Mauro Gaspari 
New reports as the issue is still happening:

I found a link on phoronix that describes with pictures exactly what is
happening:
https://w=
ww.phoronix.com/forums/forum/linux-graphics-x-org-drivers/open-source-amd-l=
inux/1049483-amd-devs-error-ring-gfx-timeout


OS: OpenSUSE tumbleweed x86_64 updated (2019 03 23)
Kernel: 5.0.2-1-default
Desktop Environment: KDE Plasma (x11)
OpenGL version: string: 4.5 (Compatibility Profile) Mesa 19.0.0
GPU: AMD Radeon RX Vega 64 8GB

Attaching log files and dmesg after crash.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15532849351.CBF2dF2.8601-- --===============0326097593== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0326097593==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 11 Apr 2019 06:37:46 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1164860337==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id BCA9B897F5 for ; Thu, 11 Apr 2019 06:37:45 +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 --===============1164860337== Content-Type: multipart/alternative; boundary="15549646650.B9e066A6C.26665" Content-Transfer-Encoding: 7bit --15549646650.B9e066A6C.26665 Date: Thu, 11 Apr 2019 06:37:45 +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=3D109955 --- Comment #4 from Mauro Gaspari --- Issue still happens despite kernel updates and mesa updates on openSUSE Tumbleweed. Same happens on Kubuntu with oibaf ppa, and on Arch. It seems this bug affects many people on linux using AMDGPUS, and found some interesting workarounds. Had a look at kernel options, applied to grub, and= so far it has been 2 weeks of extensive testing, and I did not have a single system freeze or hang. -> BEGIN KENEL PARAMETERS <- This is what I am using now. Please note that some of those settings are to enable debugging and should not left there forever. I will remove those once I am confident with the stability of the system. AMDGPU amdgpu.dc=3D1 amdgpu.vm_update_mode=3D0 amdgpu.dpm=3D-1 amdgpu.ppfeaturemask=3D0xffffffff amdgpu.vm_fault_stop=3D2 amdgpu.vm_debug= =3D1 amdgpu.gpu_recovery=3D0 - Kernel parameters explained from: https://www.kernel.org/doc/html/latest/gpu/amdgpu.html --- dc (int) Disable/Enable Display Core driver for debugging (1 =3D enable, 0 =3D disab= le). The default is -1 (automatic for each asic). --- dpm (int) Override for dynamic power management setting (1 =3D enable, 0 =3D disable)= . The default is -1 (auto). --- vm_update_mode (int) Override VM update mode. VM updated by using CPU (0 =3D never, 1 =3D Graphi= cs only, 2 =3D Compute only, 3 =3D Both). The default is -1 (Only in large BAR= (LB) systems Compute VM tables will be updated by CPU, otherwise 0, never). --- ppfeaturemask (uint) Override power features enabled. See enum PP_FEATURE_MASK in drivers/gpu/drm/amd/include/amd_shared.h. The default is the current set of stable power features. --- vm_fault_stop (int) Stop on VM fault for debugging (0 =3D never, 1 =3D print first, 2 =3D alway= s). The default is 0 (No stop). --- vm_debug (int) Debug VM handling (0 =3D disabled, 1 =3D enabled). The default is 0 (Disabl= ed). -gpu_recovery (int) Set to enable GPU recovery mechanism (1 =3D enable, 0 =3D disable). The def= ault is -1 (auto, disabled except SRIOV). -> END KERNEL PARAMETERS <- --=20 You are receiving this mail because: You are the assignee for the bug.= --15549646650.B9e066A6C.26665 Date: Thu, 11 Apr 2019 06:37:45 +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

Commen= t # 4 on bug 10995= 5 from = Mauro Gaspari 
Issue still happens despite kernel updates and mesa updates on=
 openSUSE
Tumbleweed. Same happens on Kubuntu with oibaf ppa, and on Arch.

It seems this bug affects many people on linux using AMDGPUS, and found some
interesting workarounds. Had a look at kernel options, applied to grub, and=
 so
far it has been 2 weeks of extensive testing, and I did not have a single
system freeze or hang.

-> BEGIN KENEL PARAMETERS <-
This is what I am using now. Please note that some of those settings are to
enable debugging and should not left there forever. I will remove those once
I am confident with the stability of the system.

AMDGPU
amdgpu.dc=3D1 amdgpu.vm_update_mode=3D0 amdgpu.dpm=3D-1
amdgpu.ppfeaturemask=3D0xffffffff amdgpu.vm_fault_stop=3D2 amdgpu.vm_debug=
=3D1
amdgpu.gpu_recovery=3D0


- Kernel parameters explained from:
https://=
www.kernel.org/doc/html/latest/gpu/amdgpu.html

--- dc (int)
Disable/Enable Display Core driver for debugging (1 =3D enable, 0 =3D disab=
le).
The default is -1 (automatic for each asic).


--- dpm (int)
Override for dynamic power management setting (1 =3D enable, 0 =3D disable)=
. The
default is -1 (auto).

--- vm_update_mode (int)
Override VM update mode. VM updated by using CPU (0 =3D never, 1 =3D Graphi=
cs
only, 2 =3D Compute only, 3 =3D Both). The default is -1 (Only in large BAR=
(LB)
systems Compute VM tables will be updated by CPU, otherwise 0, never).

--- ppfeaturemask (uint)
Override power features enabled. See enum PP_FEATURE_MASK in
drivers/gpu/drm/amd/include/amd_shared.h. The default is the current set of
stable power features.

--- vm_fault_stop (int)
Stop on VM fault for debugging (0 =3D never, 1 =3D print first, 2 =3D alway=
s). The
default is 0 (No stop).

--- vm_debug (int)
Debug VM handling (0 =3D disabled, 1 =3D enabled). The default is 0 (Disabl=
ed).

-gpu_recovery (int)
Set to enable GPU recovery mechanism (1 =3D enable, 0 =3D disable). The def=
ault
is -1 (auto, disabled except SRIOV).

-> END KERNEL PARAMETERS <-

You are receiving this mail because:
  • You are the assignee for the bug.
= --15549646650.B9e066A6C.26665-- --===============1164860337== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1164860337==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Fri, 12 Apr 2019 21:37:54 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0683324635==" 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 AA6D8899E7 for ; Fri, 12 Apr 2019 21:37:54 +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 --===============0683324635== Content-Type: multipart/alternative; boundary="15551050743.638BC06.8568" Content-Transfer-Encoding: 7bit --15551050743.638BC06.8568 Date: Fri, 12 Apr 2019 21:37:54 +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=3D109955 --- Comment #5 from Jaap Buurman --- I have the exact same problem with my Vega 64. Crashes when playing games. Happens with Vulkan games (RADV), OpenGL games (RadeonSI) and DirectX 9 gam= es via Wine (Gallium9). It happens only for some games, presumably because it depends on the workload. I am also suspecting power management issues. This might be a long shot, but worth a try. I know for a fact that Power management works slightly differe= nt when multiple monitors are connected, as memory isn't clocked back as much = in that case. For the people also experiencing this issue, are you guys running multiple monitors like I am? --=20 You are receiving this mail because: You are the assignee for the bug.= --15551050743.638BC06.8568 Date: Fri, 12 Apr 2019 21:37:54 +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

Commen= t # 5 on bug 10995= 5 from Jaap Buurman 
I have the exact same problem with my Vega 64. Crashes when pl=
aying games.
Happens with Vulkan games (RADV), OpenGL games (RadeonSI) and DirectX 9 gam=
es
via Wine (Gallium9). It happens only for some games, presumably because it
depends on the workload.

I am also suspecting power management issues. This might be a long shot, but
worth a try. I know for a fact that Power management works slightly differe=
nt
when multiple monitors are connected, as memory isn't clocked back as much =
in
that case. For the people also experiencing this issue, are you guys running
multiple monitors like I am?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15551050743.638BC06.8568-- --===============0683324635== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0683324635==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Fri, 12 Apr 2019 22:10:26 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1462073262==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 243B68999A for ; Fri, 12 Apr 2019 22:10:26 +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 --===============1462073262== Content-Type: multipart/alternative; boundary="15551070261.fC97ffea.21803" Content-Transfer-Encoding: 7bit --15551070261.fC97ffea.21803 Date: Fri, 12 Apr 2019 22:10:26 +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=3D109955 --- Comment #6 from Jaap Buurman --- Another question: What is the output of the following command for you guys? cat /sys/class/drm/card0/device/vbios_version=20 I am running the following version: 113-D0500100-103 According to the techpowerup GPU bios database, this is a vega bios that was replaced two days (!) later by a new version. Perhaps issues were found that required another bios update? I might install Windows on a spare HDD and tr= y to flash my Vega to see if that changes anything. --=20 You are receiving this mail because: You are the assignee for the bug.= --15551070261.fC97ffea.21803 Date: Fri, 12 Apr 2019 22:10:26 +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

Commen= t # 6 on bug 10995= 5 from Jaap Buurman 
Another question: What is the output of the following command =
for you guys?

cat /sys/class/drm/card0/device/vbios_version=20

I am running the following version:

113-D0500100-103

According to the techpowerup GPU bios database, this is a vega bios that was
replaced two days (!) later by a new version. Perhaps issues were found that
required another bios update? I might install Windows on a spare HDD and tr=
y to
flash my Vega to see if that changes anything.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15551070261.fC97ffea.21803-- --===============1462073262== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1462073262==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 13 Apr 2019 09:34:26 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0978278521==" 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 215AB892D6 for ; Sat, 13 Apr 2019 09:34:26 +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 --===============0978278521== Content-Type: multipart/alternative; boundary="15551480660.c55FFe.21230" Content-Transfer-Encoding: 7bit --15551480660.c55FFe.21230 Date: Sat, 13 Apr 2019 09:34:25 +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=3D109955 --- Comment #7 from Mauro Gaspari --- @ Jaap Buurman=20 I run a single monitor, ultra-wide 3440xx1440 @100hz. my bios version: 113-D0500100-103 --=20 You are receiving this mail because: You are the assignee for the bug.= --15551480660.c55FFe.21230 Date: Sat, 13 Apr 2019 09:34:26 +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

Commen= t # 7 on bug 10995= 5 from = Mauro Gaspari 
@ Jaap Buurman=20
I run a single monitor, ultra-wide 3440xx1440 @100hz.

my bios version: 113-D0500100-103

You are receiving this mail because:
  • You are the assignee for the bug.
= --15551480660.c55FFe.21230-- --===============0978278521== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0978278521==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 13 Apr 2019 09:41:44 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1229103419==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 970F6892E6 for ; Sat, 13 Apr 2019 09:41:44 +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 --===============1229103419== Content-Type: multipart/alternative; boundary="15551485040.44834990a.23300" Content-Transfer-Encoding: 7bit --15551485040.44834990a.23300 Date: Sat, 13 Apr 2019 09:41:44 +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=3D109955 --- Comment #8 from Jaap Buurman --- I guess we can rule out a multi-monitor issue then. But I find is VERY interesting that you also run the exact same bios version, that was replaced two days later, so it should be fairly rare. Perhaps it is buggy and was therefor replaced only 2 days after it was released? I am going to try and flash my GPU in Windows on a separate HDD and see if that fixes anything. --=20 You are receiving this mail because: You are the assignee for the bug.= --15551485040.44834990a.23300 Date: Sat, 13 Apr 2019 09:41:44 +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

Commen= t # 8 on bug 10995= 5 from Jaap Buurman 
I guess we can rule out a multi-monitor issue then. But I find=
 is VERY
interesting that you also run the exact same bios version, that was replaced
two days later, so it should be fairly rare. Perhaps it is buggy and was
therefor replaced only 2 days after it was released? I am going to try and
flash my GPU in Windows on a separate HDD and see if that fixes anything.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15551485040.44834990a.23300-- --===============1229103419== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1229103419==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 13 Apr 2019 09:49:00 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0291381247==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 190F9892EF for ; Sat, 13 Apr 2019 09:49:00 +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 --===============0291381247== Content-Type: multipart/alternative; boundary="15551489400.fD84537a.26324" Content-Transfer-Encoding: 7bit --15551489400.fD84537a.26324 Date: Sat, 13 Apr 2019 09:49:00 +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=3D109955 --- Comment #9 from Mauro Gaspari --- Interesting catch the one about the BIOS of the card. I have a separate SSD with windows10 I use to test this card stability. I w= ill check my windows MSI update tool, see if it offers me an updated BIOS. If I= do have an updated bios I will temporarily remove my workarounds and see how it goes. --=20 You are receiving this mail because: You are the assignee for the bug.= --15551489400.fD84537a.26324 Date: Sat, 13 Apr 2019 09:49:00 +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

Commen= t # 9 on bug 10995= 5 from = Mauro Gaspari 
Interesting catch the one about the BIOS of the card.

I have a separate SSD with windows10 I use to test this card stability. I w=
ill
check my windows MSI update tool, see if it offers me an updated BIOS. If I=
 do
have an updated bios I will temporarily remove my workarounds and see how it
goes.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15551489400.fD84537a.26324-- --===============0291381247== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0291381247==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 13 Apr 2019 09:52:32 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1128331445==" 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 2FDB6892EE for ; Sat, 13 Apr 2019 09:52:32 +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 --===============1128331445== Content-Type: multipart/alternative; boundary="15551491520.AE2Ee.26833" Content-Transfer-Encoding: 7bit --15551491520.AE2Ee.26833 Date: Sat, 13 Apr 2019 09:52:32 +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=3D109955 --- Comment #10 from Jaap Buurman --- You will have to flash using Atiflash: https://www.techpowerup.com/download/ati-atiflash/ And downloading the latest bios for your card from Techpowerup as well: https://www.techpowerup.com/vgabios/ Bios updates are usually not supported directly by the vendor, but I have n= ever worked with MSI update tool, so I am not 100% sure. Make sure you are very careful when picking the bios. Some bioses are for t= he watercooling variant, variants with aftermarket coolers, or overclocked one= s. --=20 You are receiving this mail because: You are the assignee for the bug.= --15551491520.AE2Ee.26833 Date: Sat, 13 Apr 2019 09:52:32 +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

Comme= nt # 10 on bug 10995= 5 from Jaap Buurman 
You will have to flash using Atiflash:

https://www.=
techpowerup.com/download/ati-atiflash/

And downloading the latest bios for your card from Techpowerup as well:

https://www.techpowerup.co=
m/vgabios/

Bios updates are usually not supported directly by the vendor, but I have n=
ever
worked with MSI update tool, so I am not 100% sure.

Make sure you are very careful when picking the bios. Some bioses are for t=
he
watercooling variant, variants with aftermarket coolers, or overclocked one=
s.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15551491520.AE2Ee.26833-- --===============1128331445== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1128331445==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 13 Apr 2019 11:34:47 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0888586406==" 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 370E4892B5 for ; Sat, 13 Apr 2019 11:34:47 +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 --===============0888586406== Content-Type: multipart/alternative; boundary="15551552870.1f12.30114" Content-Transfer-Encoding: 7bit --15551552870.1f12.30114 Date: Sat, 13 Apr 2019 11:34:47 +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=3D109955 --- Comment #11 from Mauro Gaspari --- You are right. MSI tools do not offer any BIOS update for GPU. I downloaded the utility and filtered BIOS by vendor and DeviceID, I saw th= e 3 BIOS version and the one that, as you said was released 2 days after the on= e we are using. I do not have high hopes, because with current BIOS, all games on windows r= un fine. But well, cannot hurt to try the upgrade. Worst case I will re-introd= uce my workarounds. I had zero freezes with those enabled in the last 2 weeks.= =20 And if I end up bricking my GPU out of warranty, I have the excuse to get a= new RadeonVII :D --=20 You are receiving this mail because: You are the assignee for the bug.= --15551552870.1f12.30114 Date: Sat, 13 Apr 2019 11:34:47 +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

Comme= nt # 11 on bug 10995= 5 from = Mauro Gaspari 
You are right. MSI tools do not offer any BIOS update for GPU.

I downloaded the utility and filtered BIOS by vendor and DeviceID, I saw th=
e 3
BIOS version and the one that, as you said was released 2 days after the on=
e we
are using.

I do not have high hopes, because with current BIOS, all games on windows r=
un
fine. But well, cannot hurt to try the upgrade. Worst case I will re-introd=
uce
my workarounds. I had zero freezes with those enabled in the last 2 weeks.=
=20

And if I end up bricking my GPU out of warranty, I have the excuse to get a=
 new
RadeonVII :D

You are receiving this mail because:
  • You are the assignee for the bug.
= --15551552870.1f12.30114-- --===============0888586406== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0888586406==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 13 Apr 2019 13:19:33 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1183954343==" 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 5A661892C2 for ; Sat, 13 Apr 2019 13:19:33 +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 --===============1183954343== Content-Type: multipart/alternative; boundary="15551615730.f3E2A.6694" Content-Transfer-Encoding: 7bit --15551615730.f3E2A.6694 Date: Sat, 13 Apr 2019 13:19:33 +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=3D109955 --- Comment #12 from Jaap Buurman --- My Vega64 was also 100% stable on the exact same build under Windows 10. So= I am also not getting my hopes up, but I am really frustrated. I am hoping it= is some kind of incompatibility problem. I have honestly tried so many things, that I am willing to give the long-shots a chance as well.=20 Since my Switch to Linux ~1.5 years ago, stability with the Vega64 has been very finicky. Some games run fine, while some games cause this crash pretty reliably. Very, very frustrating. --=20 You are receiving this mail because: You are the assignee for the bug.= --15551615730.f3E2A.6694 Date: Sat, 13 Apr 2019 13:19:33 +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

Comme= nt # 12 on bug 10995= 5 from Jaap Buurman 
My Vega64 was also 100% stable on the exact same build under W=
indows 10. So I
am also not getting my hopes up, but I am really frustrated. I am hoping it=
 is
some kind of incompatibility problem. I have honestly tried so many things,
that I am willing to give the long-shots a chance as well.=20

Since my Switch to Linux ~1.5 years ago, stability with the Vega64 has been
very finicky. Some games run fine, while some games cause this crash pretty
reliably. Very, very frustrating.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15551615730.f3E2A.6694-- --===============1183954343== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1183954343==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 13 Apr 2019 13:45:06 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1984555386==" 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 8F5FD89296 for ; Sat, 13 Apr 2019 13:45:06 +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 --===============1984555386== Content-Type: multipart/alternative; boundary="15551631061.E6b2.16539" Content-Transfer-Encoding: 7bit --15551631061.E6b2.16539 Date: Sat, 13 Apr 2019 13:45:06 +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=3D109955 --- Comment #13 from Mauro Gaspari --- Status update: I updated the BIOS and now disabled all kernel parameters I previously used. It might take some time to make sure the system is stable.= =20 Regarding your frustrations, AMD released open source drivers and that is a major improvement for people= on Linux. I got the Vega RX64 to support that. I expected a few bumps in the r= oad but well, it is taking longer than anticipated. Having said that, there you are all kernel parameters I enabled, and with t= hose as I said, I was unable to get a single freeze. Those are not fixes, most likely optimizations and workarounds. Still, work pretty well for me. CPU rcu_nocbs=3D0-15 (adjust to the number of cores of your cpu) idle=3Dnomwait processor.max_cstate=3D5 pcie_aspm=3Doff=20 GPU amdgpu.dc=3D1 amdgpu.vm_update_mode=3D0 amdgpu.dpm=3D-1 amdgpu.ppfeaturemask=3D0xffffffff amdgpu.vm_fault_stop=3D2 amdgpu.vm_debug=3D1 amdgpu.gpu_recovery=3D0 --=20 You are receiving this mail because: You are the assignee for the bug.= --15551631061.E6b2.16539 Date: Sat, 13 Apr 2019 13:45:06 +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

Comme= nt # 13 on bug 10995= 5 from = Mauro Gaspari 
Status update: I updated the BIOS and now disabled all kernel =
parameters I
previously used. It might take some time to make sure the system is stable.=
=20

Regarding your frustrations,
AMD released open source drivers and that is a major improvement for people=
 on
Linux. I got the Vega RX64 to support that. I expected a few bumps in the r=
oad
but well, it is taking longer than anticipated.

Having said that, there you are all kernel parameters I enabled, and with t=
hose
as I said, I was unable to get a single freeze. Those are not fixes, most
likely optimizations and workarounds. Still, work pretty well for me.

CPU
rcu_nocbs=3D0-15 (adjust to the number of cores of your cpu)
idle=3Dnomwait
processor.max_cstate=3D5
pcie_aspm=3Doff=20

GPU
amdgpu.dc=3D1
amdgpu.vm_update_mode=3D0
amdgpu.dpm=3D-1
amdgpu.ppfeaturemask=3D0xffffffff
amdgpu.vm_fault_stop=3D2
amdgpu.vm_debug=3D1
amdgpu.gpu_recovery=3D0

You are receiving this mail because:
  • You are the assignee for the bug.
= --15551631061.E6b2.16539-- --===============1984555386== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1984555386==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 15 Apr 2019 12:51:58 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1006111463==" 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 DABE7896C7 for ; Mon, 15 Apr 2019 12:51:57 +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 --===============1006111463== Content-Type: multipart/alternative; boundary="15553327172.DE71Ab04D.8203" Content-Transfer-Encoding: 7bit --15553327172.DE71Ab04D.8203 Date: Mon, 15 Apr 2019 12:51:57 +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=3D109955 --- Comment #14 from Mauro Gaspari --- Quick update. OS: OpenSUSE tumbleweed x86_64 updated (2019 04 15) Kernel: 5.0.7-1-default Desktop Environment: KDE Plasma (x11) OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.0.1 GPU: AMD Radeon RX Vega 64 8GB GPU firmware upgrade did not change much.=20 I disabled kernel parameters on grub, upgraded BIOS, ran some games. Same o= ld system freeze on my system came back. After that, I re-enabled kernel parameters on grub, rebooted. no more system freeze on my system. --=20 You are receiving this mail because: You are the assignee for the bug.= --15553327172.DE71Ab04D.8203 Date: Mon, 15 Apr 2019 12:51:57 +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

Comme= nt # 14 on bug 10995= 5 from = Mauro Gaspari 
Quick update.


OS: OpenSUSE tumbleweed x86_64 updated (2019 04 15)
Kernel: 5.0.7-1-default
Desktop Environment: KDE Plasma (x11)
OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.0.1
GPU: AMD Radeon RX Vega 64 8GB


GPU firmware upgrade did not change much.=20
I disabled kernel parameters on grub, upgraded BIOS, ran some games. Same o=
ld
system freeze on my system came back.

After that, I re-enabled kernel parameters on grub, rebooted. no more system
freeze on my system.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15553327172.DE71Ab04D.8203-- --===============1006111463== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1006111463==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 25 Apr 2019 19:44:19 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1696452823==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 65D4889227 for ; Thu, 25 Apr 2019 19:44:19 +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 --===============1696452823== Content-Type: multipart/alternative; boundary="15562214594.Cf02.21947" Content-Transfer-Encoding: 7bit --15562214594.Cf02.21947 Date: Thu, 25 Apr 2019 19:44:19 +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=3D109955 --- Comment #15 from Jaap Buurman --- That's bad to hear :( Worth a try though. How often do you experience freez= es by the way? And is this for all games, or are some games completely stable?= For me, I am getting crashes in Kerbal Space Program, but not in Final Fantasy = XII or World of Warcraft, even after hundreds of hours in both of these stable games. Also, have you ever figured out which kernel parameter in particular makes = your setup stable? It might help identify where the problem exists. Or do you ne= ed that exact combination of all those parameters to get your system stable? --=20 You are receiving this mail because: You are the assignee for the bug.= --15562214594.Cf02.21947 Date: Thu, 25 Apr 2019 19:44:19 +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

Comme= nt # 15 on bug 10995= 5 from Jaap Buurman 
That's bad to hear :( Worth a try though. How often do you exp=
erience freezes
by the way? And is this for all games, or are some games completely stable?=
 For
me, I am getting crashes in Kerbal Space Program, but not in Final Fantasy =
XII
or World of Warcraft, even after hundreds of hours in both of these stable
games.

Also, have you ever figured out which kernel parameter in particular makes =
your
setup stable? It might help identify where the problem exists. Or do you ne=
ed
that exact combination of all those parameters to get your system stable?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15562214594.Cf02.21947-- --===============1696452823== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1696452823==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 28 Apr 2019 16:33:39 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1160164043==" 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 122EA89146 for ; Sun, 28 Apr 2019 16:33:39 +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 --===============1160164043== Content-Type: multipart/alternative; boundary="15564692190.E0b70D4Eb.8845" Content-Transfer-Encoding: 7bit --15564692190.E0b70D4Eb.8845 Date: Sun, 28 Apr 2019 16:33:38 +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=3D109955 --- Comment #16 from Jaap Buurman --- Just got a crash in World of Warcraft as well, running via vkd3d. It happens instantly after trying to log into the game world, so the issue is nicely reproducible for me. If you want me to get any traces, please let me know w= hat you would like me to run to get them. dmesg logs for now: [ 78.450637] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:= 158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237= 0) [ 78.450641] amdgpu 0000:09:00.0: in page starting at address 0x0000984ec2d4b000 from 27 [ 78.450642] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D [ 78.450648] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:= 158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237= 0) [ 78.450650] amdgpu 0000:09:00.0: in page starting at address 0x0000850e92553000 from 27 [ 78.450652] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D [ 78.450656] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:= 158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237= 0) [ 78.450658] amdgpu 0000:09:00.0: in page starting at address 0x0000984ec2d4e000 from 27 [ 78.450660] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D [ 78.450665] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:= 158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237= 0) [ 78.450666] amdgpu 0000:09:00.0: in page starting at address 0x0000850e92542000 from 27 [ 78.450668] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D [ 78.450673] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:= 158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237= 0) [ 78.450674] amdgpu 0000:09:00.0: in page starting at address 0x0000984ec2d42000 from 27 [ 78.450676] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D [ 78.450680] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:= 158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237= 0) [ 78.450682] amdgpu 0000:09:00.0: in page starting at address 0x0000850e92552000 from 27 [ 78.450683] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D [ 78.450688] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:= 158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237= 0) [ 78.450690] amdgpu 0000:09:00.0: in page starting at address 0x0000984ec2d40000 from 27 [ 78.450691] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D [ 78.450696] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:= 158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237= 0) [ 78.450697] amdgpu 0000:09:00.0: in page starting at address 0x0000850e92552000 from 27 [ 78.450699] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D [ 78.450703] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:= 158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237= 0) [ 78.450705] amdgpu 0000:09:00.0: in page starting at address 0x0000984ec2d49000 from 27 [ 78.450706] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D [ 78.450711] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:= 158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237= 0) [ 78.450713] amdgpu 0000:09:00.0: in page starting at address 0x0000850ea1eb2000 from 27 [ 78.450714] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D [ 78.454307] amdgpu 0000:09:00.0: IH ring buffer overflow (0x000BEDC0, 0x0003EEC0, 0x0003EDE0) [ 88.570062] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D25317, emitted seq=3D25319 [ 88.570099] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati= on: process WoW.exe pid 2349 thread WoW.exe:cs0 pid 2370 [ 88.570102] amdgpu 0000:09:00.0: GPU reset begin! [ 88.831392] amdgpu 0000:09:00.0: GPU reset [ 89.356679] [drm] psp mode1 reset succeed=20 [ 89.475356] amdgpu 0000:09:00.0: GPU reset succeeded, trying to resume [ 89.475465] [drm] PCIE GART of 512M enabled (table at 0x000000F400900000= ). [ 89.475508] [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* VRAM is los= t! [ 89.475642] [drm] PSP is resuming... [ 89.623052] [drm] reserve 0x400000 from 0xf400d00000 for PSP TMR SIZE [ 89.806625] [drm] SADs count is: -2, don't need to read it [ 89.856619] [drm] SADs count is: -2, don't need to read it [ 89.938255] [drm] UVD and UVD ENC initialized successfully. [ 90.038674] [drm] VCE initialized successfully. [ 90.039672] [drm] recover vram bo from shadow start [ 90.047496] [drm] recover vram bo from shadow done [ 90.047497] [drm] Skip scheduling IBs! [ 90.047499] [drm] Skip scheduling IBs! [ 90.047511] [drm] Skip scheduling IBs! [ 90.047518] [drm] Skip scheduling IBs! [ 90.047523] [drm] Skip scheduling IBs! [ 90.047524] [drm] Skip scheduling IBs! [ 90.047530] [drm] Skip scheduling IBs! [ 90.047531] [drm] Skip scheduling IBs! [ 90.047533] [drm] Skip scheduling IBs! [ 90.047535] [drm] Skip scheduling IBs! [ 90.047536] [drm] Skip scheduling IBs! [ 90.047538] [drm] Skip scheduling IBs! [ 90.047539] [drm] Skip scheduling IBs! [ 90.047555] amdgpu 0000:09:00.0: GPU reset(2) succeeded! [ 90.047796] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 90.049377] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 90.050524] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 90.051990] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 90.055576] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 90.136508] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 90.180374] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 90.181405] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 90.246698] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 90.313258] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 90.380264] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 90.446291] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 90.513947] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 90.579552] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.218785] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.218976] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.219571] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.219745] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.221821] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.221969] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.222145] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.222360] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.229911] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.230213] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.231183] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.231328] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.231487] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.231703] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.233480] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.247154] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.249213] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.249437] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.250924] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.251258] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.251320] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.252417] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.252532] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.252739] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.252994] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.254745] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.265835] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.265974] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.266056] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.266222] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.266342] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.266436] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.266516] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.266646] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.266796] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.266997] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.271605] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.274639] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.274699] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.274747] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.274794] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.274869] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.274929] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.274981] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.275033] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.275373] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.284443] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.286591] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.286881] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.302782] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.319311] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.335908] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.353111] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.369124] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.385670] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.402801] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.421232] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.737933] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.738054] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.742378] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.742737] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.742845] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.744592] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.744806] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.751833] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.752108] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.752371] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.752475] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.752604] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.752762] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.754128] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.765700] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.766154] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.766250] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.767140] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.767447] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.789098] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.789205] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.789293] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.789364] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.789473] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.789598] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.789675] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.789745] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.790301] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.803790] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.811866] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.821133] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.837593] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.841186] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.854467] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.870915] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.871297] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.887676] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.901326] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.902101] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.903913] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.927724] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.938301] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.941050] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.952885] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.975232] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.975468] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 99.986053] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.005910] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.018771] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.036370] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.052090] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.067194] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.067901] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.068016] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.081081] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.081359] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.081525] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.081618] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.081721] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.081845] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.082026] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.082151] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.082246] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.082329] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.082439] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.082579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.082757] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.086543] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.098769] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.102700] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.445931] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.446590] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.946103] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 100.946823] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 101.446237] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 101.446803] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 101.946107] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 101.946642] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 102.445541] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 102.446075] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 102.946163] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 102.946730] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 103.446040] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 103.446555] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 103.945513] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 103.945951] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 104.437414] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 104.437827] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 104.946771] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 104.947166] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 105.446585] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 105.447008] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 105.937954] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 105.938407] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 106.445966] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 106.446429] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 106.945528] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 106.945999] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 107.445983] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 107.446405] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 107.946131] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 107.946642] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 108.446428] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 108.446960] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 108.946992] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 108.947500] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 109.445052] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 109.445477] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 109.533707] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 109.946108] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 109.946604] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 110.445730] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 110.446232] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 110.943308] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 110.943823] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 111.036544] kauditd_printk_skb: 16509 callbacks suppressed [ 111.036545] audit: type=3D1006 audit(1556468881.509:99): pid=3D2590 uid= =3D0 old-auid=3D4294967295 auid=3D1000 tty=3D(none) old-ses=3D4294967295 ses=3D4= res=3D1 [ 111.446470] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 111.446899] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 111.945982] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 111.946413] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! --=20 You are receiving this mail because: You are the assignee for the bug.= --15564692190.E0b70D4Eb.8845 Date: Sun, 28 Apr 2019 16:33:39 +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

Comme= nt # 16 on bug 10995= 5 from Jaap Buurman 
Just got a crash in World of Warcraft as well, running via vkd=
3d. It happens
instantly after trying to log into the game world, so the issue is nicely
reproducible for me. If you want me to get any traces, please let me know w=
hat
you would like me to run to get them. dmesg logs for now:

[   78.450637] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:=
158
vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237=
0)
[   78.450641] amdgpu 0000:09:00.0:   in page starting at address
0x0000984ec2d4b000 from 27
[   78.450642] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D
[   78.450648] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:=
158
vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237=
0)
[   78.450650] amdgpu 0000:09:00.0:   in page starting at address
0x0000850e92553000 from 27
[   78.450652] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D
[   78.450656] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:=
158
vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237=
0)
[   78.450658] amdgpu 0000:09:00.0:   in page starting at address
0x0000984ec2d4e000 from 27
[   78.450660] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D
[   78.450665] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:=
158
vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237=
0)
[   78.450666] amdgpu 0000:09:00.0:   in page starting at address
0x0000850e92542000 from 27
[   78.450668] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D
[   78.450673] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:=
158
vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237=
0)
[   78.450674] amdgpu 0000:09:00.0:   in page starting at address
0x0000984ec2d42000 from 27
[   78.450676] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D
[   78.450680] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:=
158
vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237=
0)
[   78.450682] amdgpu 0000:09:00.0:   in page starting at address
0x0000850e92552000 from 27
[   78.450683] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D
[   78.450688] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:=
158
vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237=
0)
[   78.450690] amdgpu 0000:09:00.0:   in page starting at address
0x0000984ec2d40000 from 27
[   78.450691] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D
[   78.450696] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:=
158
vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237=
0)
[   78.450697] amdgpu 0000:09:00.0:   in page starting at address
0x0000850e92552000 from 27
[   78.450699] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D
[   78.450703] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:=
158
vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237=
0)
[   78.450705] amdgpu 0000:09:00.0:   in page starting at address
0x0000984ec2d49000 from 27
[   78.450706] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D
[   78.450711] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:=
158
vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 pid 237=
0)
[   78.450713] amdgpu 0000:09:00.0:   in page starting at address
0x0000850ea1eb2000 from 27
[   78.450714] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D
[   78.454307] amdgpu 0000:09:00.0: IH ring buffer overflow (0x000BEDC0,
0x0003EEC0, 0x0003EDE0)
[   88.570062] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=3D25317, emitted seq=3D25319
[   88.570099] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati=
on:
process WoW.exe pid 2349 thread WoW.exe:cs0 pid 2370
[   88.570102] amdgpu 0000:09:00.0: GPU reset begin!
[   88.831392] amdgpu 0000:09:00.0: GPU reset
[   89.356679] [drm] psp mode1 reset succeed=20
[   89.475356] amdgpu 0000:09:00.0: GPU reset succeeded, trying to resume
[   89.475465] [drm] PCIE GART of 512M enabled (table at 0x000000F400900000=
).
[   89.475508] [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* VRAM is los=
t!
[   89.475642] [drm] PSP is resuming...
[   89.623052] [drm] reserve 0x400000 from 0xf400d00000 for PSP TMR SIZE
[   89.806625] [drm] SADs count is: -2, don't need to read it
[   89.856619] [drm] SADs count is: -2, don't need to read it
[   89.938255] [drm] UVD and UVD ENC initialized successfully.
[   90.038674] [drm] VCE initialized successfully.
[   90.039672] [drm] recover vram bo from shadow start
[   90.047496] [drm] recover vram bo from shadow done
[   90.047497] [drm] Skip scheduling IBs!
[   90.047499] [drm] Skip scheduling IBs!
[   90.047511] [drm] Skip scheduling IBs!
[   90.047518] [drm] Skip scheduling IBs!
[   90.047523] [drm] Skip scheduling IBs!
[   90.047524] [drm] Skip scheduling IBs!
[   90.047530] [drm] Skip scheduling IBs!
[   90.047531] [drm] Skip scheduling IBs!
[   90.047533] [drm] Skip scheduling IBs!
[   90.047535] [drm] Skip scheduling IBs!
[   90.047536] [drm] Skip scheduling IBs!
[   90.047538] [drm] Skip scheduling IBs!
[   90.047539] [drm] Skip scheduling IBs!
[   90.047555] amdgpu 0000:09:00.0: GPU reset(2) succeeded!
[   90.047796] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   90.049377] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   90.050524] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   90.051990] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   90.055576] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   90.136508] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   90.180374] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   90.181405] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   90.246698] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   90.313258] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   90.380264] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   90.446291] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   90.513947] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   90.579552] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.218785] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.218976] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.219571] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.219745] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.221821] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.221969] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.222145] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.222360] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.229911] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.230213] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.231183] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.231328] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.231487] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.231703] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.233480] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.247154] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.249213] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.249437] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.250924] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.251258] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.251320] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.252417] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.252532] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.252739] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.252994] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.254745] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.265835] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.265974] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.266056] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.266222] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.266342] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.266436] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.266516] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.266646] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.266796] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.266997] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.271605] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.274639] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.274699] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.274747] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.274794] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.274869] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.274929] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.274981] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.275033] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.275373] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.284443] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.286591] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.286881] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.302782] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.319311] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.335908] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.353111] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.369124] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.385670] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.402801] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.421232] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.737933] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.738054] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.742378] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.742737] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.742845] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.744592] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.744806] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.751833] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.752108] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.752371] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.752475] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.752604] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.752762] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.754128] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.765700] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.766154] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.766250] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.767140] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.767447] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.789098] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.789205] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.789293] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.789364] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.789473] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.789598] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.789675] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.789745] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.790301] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.803790] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.811866] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.821133] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.837593] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.841186] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.854467] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.870915] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.871297] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.887676] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.901326] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.902101] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.903913] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.927724] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.938301] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.941050] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.952885] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.975232] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.975468] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[   99.986053] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.005910] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.018771] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.036370] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.052090] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.067194] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.067901] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.068016] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.081081] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.081359] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.081525] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.081618] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.081721] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.081845] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.082026] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.082151] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.082246] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.082329] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.082439] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.082579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.082757] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.086543] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.098769] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.102700] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.445931] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.446590] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.946103] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  100.946823] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  101.446237] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  101.446803] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  101.946107] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  101.946642] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  102.445541] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  102.446075] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  102.946163] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  102.946730] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  103.446040] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  103.446555] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  103.945513] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  103.945951] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  104.437414] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  104.437827] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  104.946771] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  104.947166] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  105.446585] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  105.447008] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  105.937954] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  105.938407] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  106.445966] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  106.446429] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  106.945528] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  106.945999] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  107.445983] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  107.446405] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  107.946131] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  107.946642] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  108.446428] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  108.446960] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  108.946992] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  108.947500] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  109.445052] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  109.445477] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  109.533707] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  109.946108] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  109.946604] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  110.445730] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  110.446232] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  110.943308] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  110.943823] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  111.036544] kauditd_printk_skb: 16509 callbacks suppressed
[  111.036545] audit: type=3D1006 audit(1556468881.509:99): pid=3D2590 uid=
=3D0
old-auid=3D4294967295 auid=3D1000 tty=3D(none) old-ses=3D4294967295 ses=3D4=
 res=3D1
[  111.446470] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  111.446899] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  111.945982] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  111.946413] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!

You are receiving this mail because:
  • You are the assignee for the bug.
= --15564692190.E0b70D4Eb.8845-- --===============1160164043== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1160164043==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 29 Apr 2019 01:15:49 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1083713017==" 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 EFA4F8901E for ; Mon, 29 Apr 2019 01:15:48 +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 --===============1083713017== Content-Type: multipart/alternative; boundary="15565005483.Be17.7909" Content-Transfer-Encoding: 7bit --15565005483.Be17.7909 Date: Mon, 29 Apr 2019 01:15:48 +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=3D109955 --- Comment #17 from Alex Deucher --- (In reply to Jaap Buurman from comment #16) > Just got a crash in World of Warcraft as well, running via vkd3d. It happ= ens > instantly after trying to log into the game world, so the issue is nicely > reproducible for me. If you want me to get any traces, please let me know > what you would like me to run to get them. dmesg logs for now: >=20 > [ 78.450637] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:= cs0 > pid 2370) > [ 78.450641] amdgpu 0000:09:00.0: in page starting at address > 0x0000984ec2d4b000 from 27 > [ 78.450642] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101= 13D > [ 78.450648] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:= cs0 > pid 2370) > [ 78.450650] amdgpu 0000:09:00.0: in page starting at address > 0x0000850e92553000 from 27 > [ 78.450652] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101= 13D > [ 78.450656] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:= cs0 > pid 2370) > [ 78.450658] amdgpu 0000:09:00.0: in page starting at address > 0x0000984ec2d4e000 from 27 > [ 78.450660] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101= 13D > [ 78.450665] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:= cs0 > pid 2370) > [ 78.450666] amdgpu 0000:09:00.0: in page starting at address > 0x0000850e92542000 from 27 > [ 78.450668] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101= 13D > [ 78.450673] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:= cs0 > pid 2370) > [ 78.450674] amdgpu 0000:09:00.0: in page starting at address > 0x0000984ec2d42000 from 27 > [ 78.450676] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101= 13D > [ 78.450680] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:= cs0 > pid 2370) > [ 78.450682] amdgpu 0000:09:00.0: in page starting at address > 0x0000850e92552000 from 27 > [ 78.450683] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101= 13D > [ 78.450688] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:= cs0 > pid 2370) > [ 78.450690] amdgpu 0000:09:00.0: in page starting at address > 0x0000984ec2d40000 from 27 > [ 78.450691] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101= 13D > [ 78.450696] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:= cs0 > pid 2370) > [ 78.450697] amdgpu 0000:09:00.0: in page starting at address > 0x0000850e92552000 from 27 > [ 78.450699] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101= 13D > [ 78.450703] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:= cs0 > pid 2370) > [ 78.450705] amdgpu 0000:09:00.0: in page starting at address > 0x0000984ec2d49000 from 27 > [ 78.450706] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101= 13D > [ 78.450711] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:= cs0 > pid 2370) > [ 78.450713] amdgpu 0000:09:00.0: in page starting at address > 0x0000850ea1eb2000 from 27 > [ 78.450714] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101= 13D > [ 78.454307] amdgpu 0000:09:00.0: IH ring buffer overflow (0x000BEDC0, > 0x0003EEC0, 0x0003EDE0) > [ 88.570062] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeou= t, > signaled seq=3D25317, emitted seq=3D25319 > [ 88.570099] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process > information: process WoW.exe pid 2349 thread WoW.exe:cs0 pid 2370 > [ 88.570102] amdgpu 0000:09:00.0: GPU reset begin! > [ 88.831392] amdgpu 0000:09:00.0: GPU reset > [ 89.356679] [drm] psp mode1 reset succeed=20 > [ 89.475356] amdgpu 0000:09:00.0: GPU reset succeeded, trying to resume > [ 89.475465] [drm] PCIE GART of 512M enabled (table at 0x000000F4009000= 00). > [ 89.475508] [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* VRAM is l= ost! > [ 89.475642] [drm] PSP is resuming... > [ 89.623052] [drm] reserve 0x400000 from 0xf400d00000 for PSP TMR SIZE > [ 89.806625] [drm] SADs count is: -2, don't need to read it > [ 89.856619] [drm] SADs count is: -2, don't need to read it > [ 89.938255] [drm] UVD and UVD ENC initialized successfully. > [ 90.038674] [drm] VCE initialized successfully. > [ 90.039672] [drm] recover vram bo from shadow start > [ 90.047496] [drm] recover vram bo from shadow done > [ 90.047497] [drm] Skip scheduling IBs! > [ 90.047499] [drm] Skip scheduling IBs! > [ 90.047511] [drm] Skip scheduling IBs! > [ 90.047518] [drm] Skip scheduling IBs! > [ 90.047523] [drm] Skip scheduling IBs! > [ 90.047524] [drm] Skip scheduling IBs! > [ 90.047530] [drm] Skip scheduling IBs! > [ 90.047531] [drm] Skip scheduling IBs! > [ 90.047533] [drm] Skip scheduling IBs! > [ 90.047535] [drm] Skip scheduling IBs! > [ 90.047536] [drm] Skip scheduling IBs! > [ 90.047538] [drm] Skip scheduling IBs! > [ 90.047539] [drm] Skip scheduling IBs! > [ 90.047555] amdgpu 0000:09:00.0: GPU reset(2) succeeded! The GPU reset succeeded. You'll need to restart your desktop manager to recover because currently no desktop managers handle GPU reset errors and re-initialize their contexts. --=20 You are receiving this mail because: You are the assignee for the bug.= --15565005483.Be17.7909 Date: Mon, 29 Apr 2019 01:15:48 +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

Comme= nt # 17 on bug 10995= 5 from Alex Deucher 
(In reply to Jaap Buurman from comment #16)
> Just got a crash in World of Warcraft as well, r=
unning via vkd3d. It happens
> instantly after trying to log into the game world, so the issue is nic=
ely
> reproducible for me. If you want me to get any traces, please let me k=
now
> what you would like me to run to get them. dmesg logs for now:
>=20
> [   78.450637] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0
> ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.e=
xe:cs0
> pid 2370)
> [   78.450641] amdgpu 0000:09:00.0:   in page starting at address
> 0x0000984ec2d4b000 from 27
> [   78.450642] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00=
10113D
> [   78.450648] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0
> ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.e=
xe:cs0
> pid 2370)
> [   78.450650] amdgpu 0000:09:00.0:   in page starting at address
> 0x0000850e92553000 from 27
> [   78.450652] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00=
10113D
> [   78.450656] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0
> ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.e=
xe:cs0
> pid 2370)
> [   78.450658] amdgpu 0000:09:00.0:   in page starting at address
> 0x0000984ec2d4e000 from 27
> [   78.450660] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00=
10113D
> [   78.450665] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0
> ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.e=
xe:cs0
> pid 2370)
> [   78.450666] amdgpu 0000:09:00.0:   in page starting at address
> 0x0000850e92542000 from 27
> [   78.450668] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00=
10113D
> [   78.450673] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0
> ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.e=
xe:cs0
> pid 2370)
> [   78.450674] amdgpu 0000:09:00.0:   in page starting at address
> 0x0000984ec2d42000 from 27
> [   78.450676] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00=
10113D
> [   78.450680] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0
> ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.e=
xe:cs0
> pid 2370)
> [   78.450682] amdgpu 0000:09:00.0:   in page starting at address
> 0x0000850e92552000 from 27
> [   78.450683] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00=
10113D
> [   78.450688] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0
> ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.e=
xe:cs0
> pid 2370)
> [   78.450690] amdgpu 0000:09:00.0:   in page starting at address
> 0x0000984ec2d40000 from 27
> [   78.450691] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00=
10113D
> [   78.450696] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0
> ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.e=
xe:cs0
> pid 2370)
> [   78.450697] amdgpu 0000:09:00.0:   in page starting at address
> 0x0000850e92552000 from 27
> [   78.450699] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00=
10113D
> [   78.450703] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0
> ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.e=
xe:cs0
> pid 2370)
> [   78.450705] amdgpu 0000:09:00.0:   in page starting at address
> 0x0000984ec2d49000 from 27
> [   78.450706] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00=
10113D
> [   78.450711] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0
> ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.e=
xe:cs0
> pid 2370)
> [   78.450713] amdgpu 0000:09:00.0:   in page starting at address
> 0x0000850ea1eb2000 from 27
> [   78.450714] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00=
10113D
> [   78.454307] amdgpu 0000:09:00.0: IH ring buffer overflow (0x000BEDC=
0,
> 0x0003EEC0, 0x0003EDE0)
> [   88.570062] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx tim=
eout,
> signaled seq=3D25317, emitted seq=3D25319
> [   88.570099] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process
> information: process WoW.exe pid 2349 thread WoW.exe:cs0 pid 2370
> [   88.570102] amdgpu 0000:09:00.0: GPU reset begin!
> [   88.831392] amdgpu 0000:09:00.0: GPU reset
> [   89.356679] [drm] psp mode1 reset succeed=20
> [   89.475356] amdgpu 0000:09:00.0: GPU reset succeeded, trying to res=
ume
> [   89.475465] [drm] PCIE GART of 512M enabled (table at 0x000000F4009=
00000).
> [   89.475508] [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* VRAM i=
s lost!
> [   89.475642] [drm] PSP is resuming...
> [   89.623052] [drm] reserve 0x400000 from 0xf400d00000 for PSP TMR SI=
ZE
> [   89.806625] [drm] SADs count is: -2, don't need to read it
> [   89.856619] [drm] SADs count is: -2, don't need to read it
> [   89.938255] [drm] UVD and UVD ENC initialized successfully.
> [   90.038674] [drm] VCE initialized successfully.
> [   90.039672] [drm] recover vram bo from shadow start
> [   90.047496] [drm] recover vram bo from shadow done
> [   90.047497] [drm] Skip scheduling IBs!
> [   90.047499] [drm] Skip scheduling IBs!
> [   90.047511] [drm] Skip scheduling IBs!
> [   90.047518] [drm] Skip scheduling IBs!
> [   90.047523] [drm] Skip scheduling IBs!
> [   90.047524] [drm] Skip scheduling IBs!
> [   90.047530] [drm] Skip scheduling IBs!
> [   90.047531] [drm] Skip scheduling IBs!
> [   90.047533] [drm] Skip scheduling IBs!
> [   90.047535] [drm] Skip scheduling IBs!
> [   90.047536] [drm] Skip scheduling IBs!
> [   90.047538] [drm] Skip scheduling IBs!
> [   90.047539] [drm] Skip scheduling IBs!
> [   90.047555] amdgpu 0000:09:00.0: GPU reset(2) succeeded!

The GPU reset succeeded.  You'll need to restart your desktop manager to
recover because currently no desktop managers handle GPU reset errors and
re-initialize their contexts.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15565005483.Be17.7909-- --===============1083713017== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1083713017==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 29 Apr 2019 10:41:42 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1262853091==" 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 40696892C2 for ; Mon, 29 Apr 2019 10:41:42 +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 --===============1262853091== Content-Type: multipart/alternative; boundary="15565345022.AFCcaB99.9150" Content-Transfer-Encoding: 7bit --15565345022.AFCcaB99.9150 Date: Mon, 29 Apr 2019 10:41:42 +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=3D109955 --- Comment #18 from Jaap Buurman --- I was aware of that. I was more curious if the bug that is causing the crash can be identified and hopefully fixed. I can provide traces if required, si= nce it seems I can easily reproduce the crash. --=20 You are receiving this mail because: You are the assignee for the bug.= --15565345022.AFCcaB99.9150 Date: Mon, 29 Apr 2019 10:41:42 +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

Comme= nt # 18 on bug 10995= 5 from Jaap Buurman 
I was aware of that. I was more curious if the bug that is cau=
sing the crash
can be identified and hopefully fixed. I can provide traces if required, si=
nce
it seems I can easily reproduce the crash.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15565345022.AFCcaB99.9150-- --===============1262853091== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1262853091==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 29 Apr 2019 11:35:27 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0792850944==" 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 F388788EFF for ; Mon, 29 Apr 2019 11:35:26 +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 --===============0792850944== Content-Type: multipart/alternative; boundary="15565377260.3698cFE.30568" Content-Transfer-Encoding: 7bit --15565377260.3698cFE.30568 Date: Mon, 29 Apr 2019 11:35:26 +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=3D109955 --- Comment #19 from Mauro Gaspari --- (In reply to Jaap Buurman from comment #15) > That's bad to hear :( Worth a try though. How often do you experience > freezes by the way? And is this for all games, or are some games complete= ly > stable? For me, I am getting crashes in Kerbal Space Program, but not in > Final Fantasy XII or World of Warcraft, even after hundreds of hours in b= oth > of these stable games. >=20 > Also, have you ever figured out which kernel parameter in particular makes > your setup stable? It might help identify where the problem exists. Or do > you need that exact combination of all those parameters to get your system > stable? Hi, regarding the parameters I am using. Unfortunately for me the issue is not easy to reproduce. Without the parame= ters enabled, it still takes hours for a crash to happen. On top of that, mesa a= nd kernel updates are really frequent on Tumbleweed, that is another variable = that makes it a bit harder to troubleshoot. Unless I can find a really fast way = to reproduce the issue. Regarding which game crash, with those kernel parameters applied, the only crashes I noticed were when I tried to run games through Wine in DX11 mode = with DXVK. Which i believe to be stable on Vega GPUs, would need at least LLVM8. Currently on my Tumbleweed I have LLVM7 so I just stick to NON-DXVK games, = or even better native ones, until LLVM8 is available for tumbleweed. If you want to give it a try and you run on ubuntu, you can check this arti= cle: https://github.com/lutris/lutris/wiki/Installing-drivers If you do so, I recommend you run a full system backup using clonezilla or similar software, those ppas are marked as unstable. --=20 You are receiving this mail because: You are the assignee for the bug.= --15565377260.3698cFE.30568 Date: Mon, 29 Apr 2019 11:35:26 +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

Comme= nt # 19 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Jaap Buurman from comment #15)
> That's bad to hear :( Worth a try though. How of=
ten do you experience
> freezes by the way? And is this for all games, or are some games compl=
etely
> stable? For me, I am getting crashes in Kerbal Space Program, but not =
in
> Final Fantasy XII or World of Warcraft, even after hundreds of hours i=
n both
> of these stable games.
>=20
> Also, have you ever figured out which kernel parameter in particular m=
akes
> your setup stable? It might help identify where the problem exists. Or=
 do
> you need that exact combination of all those parameters to get your sy=
stem
> stable?

Hi, regarding the parameters I am using.
Unfortunately for me the issue is not easy to reproduce. Without the parame=
ters
enabled, it still takes hours for a crash to happen. On top of that, mesa a=
nd
kernel updates are really frequent on Tumbleweed, that is another variable =
that
makes it a bit harder to troubleshoot. Unless I can find a really fast way =
to
reproduce the issue.

Regarding which game crash, with those kernel parameters applied, the only
crashes I noticed were when I tried to run games through Wine in DX11 mode =
with
DXVK. Which i believe to be stable on Vega GPUs, would need at least LLVM8.
Currently on my Tumbleweed I have LLVM7 so I just stick to NON-DXVK games, =
or
even better native ones, until LLVM8 is available for tumbleweed.

If you want to give it a try and you run on ubuntu, you can check this arti=
cle:
https:=
//github.com/lutris/lutris/wiki/Installing-drivers

If you do so, I recommend you run a full system backup using clonezilla or
similar software, those ppas are marked as unstable.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15565377260.3698cFE.30568-- --===============0792850944== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0792850944==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 29 Apr 2019 11:37:13 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1800880748==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id B413A892FD for ; Mon, 29 Apr 2019 11:37:13 +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 --===============1800880748== Content-Type: multipart/alternative; boundary="15565378333.84D9DEBE.31101" Content-Transfer-Encoding: 7bit --15565378333.84D9DEBE.31101 Date: Mon, 29 Apr 2019 11:37:13 +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=3D109955 --- Comment #20 from Jaap Buurman --- I already run LLVM 8.0.0, since it's the latest stable in Arch's repository. Thanks for the tip though :) --=20 You are receiving this mail because: You are the assignee for the bug.= --15565378333.84D9DEBE.31101 Date: Mon, 29 Apr 2019 11:37:13 +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

Comme= nt # 20 on bug 10995= 5 from Jaap Buurman 
I already run LLVM 8.0.0, since it's the latest stable in Arch=
's repository.
Thanks for the tip though :)

You are receiving this mail because:
  • You are the assignee for the bug.
= --15565378333.84D9DEBE.31101-- --===============1800880748== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1800880748==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 29 Apr 2019 13:52:33 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0550116927==" 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 E425F891AC for ; Mon, 29 Apr 2019 13:52:32 +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 --===============0550116927== Content-Type: multipart/alternative; boundary="15565459522.B0A2e.10442" Content-Transfer-Encoding: 7bit --15565459522.B0A2e.10442 Date: Mon, 29 Apr 2019 13:52:32 +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=3D109955 --- Comment #21 from Mauro Gaspari --- (In reply to Jaap Buurman from comment #20) > I already run LLVM 8.0.0, since it's the latest stable in Arch's reposito= ry. > Thanks for the tip though :) Since it is very easy for you to reproduce the freeze, it would be great if= you could add those kernel parameters, and see if they help. --=20 You are receiving this mail because: You are the assignee for the bug.= --15565459522.B0A2e.10442 Date: Mon, 29 Apr 2019 13:52:32 +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

Comme= nt # 21 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Jaap Buurman from comment #20)
> I already run LLVM 8.0.0, since it's the latest =
stable in Arch's repository.
> Thanks for the tip though :)

Since it is very easy for you to reproduce the freeze, it would be great if=
 you
could add those kernel parameters, and see if they help.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15565459522.B0A2e.10442-- --===============0550116927== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0550116927==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Fri, 24 May 2019 05:12:18 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1902271098==" 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 5A1EC6E088 for ; Fri, 24 May 2019 05:12:18 +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 --===============1902271098== Content-Type: multipart/alternative; boundary="15586747382.DD995eC.17416" Content-Transfer-Encoding: 7bit --15586747382.DD995eC.17416 Date: Fri, 24 May 2019 05:12:18 +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=3D109955 --- Comment #22 from Mauro Gaspari --- I ran more tests: 1. Installed Arch Linux, vulkan, llvm8 and ran wine games with DXVK. With s= ame kernel parameters on grub, no freezes, no crashes. Great performance. 2. Installed Ubuntu Budgie 19.04, Oibaf ppa, updated mesa and llvm8. Same as with Arch Linux: With same kernel parameters on grub, no freezes, no crashe= s. Great performance. The only issue I have not being able to reproduce the issue quickly, is to clearly understand when the issue is resolved by Mesa. It takes hours for m= e to get the freeze sometimes.=20 If someone has a quick way to trigger system freeze, I am happy to run more tests. --=20 You are receiving this mail because: You are the assignee for the bug.= --15586747382.DD995eC.17416 Date: Fri, 24 May 2019 05:12:18 +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

Comme= nt # 22 on bug 10995= 5 from = Mauro Gaspari 
I ran more tests:

1. Installed Arch Linux, vulkan, llvm8 and ran wine games with DXVK. With s=
ame
kernel parameters on grub, no freezes, no crashes. Great performance.

2. Installed Ubuntu Budgie 19.04, Oibaf ppa, updated mesa and llvm8. Same as
with Arch Linux: With same kernel parameters on grub, no freezes, no crashe=
s.
Great performance.

The only issue I have not being able to reproduce the issue quickly, is to
clearly understand when the issue is resolved by Mesa. It takes hours for m=
e to
get the freeze sometimes.=20
If someone has a quick way to trigger system freeze, I am happy to run more
tests.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15586747382.DD995eC.17416-- --===============1902271098== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1902271098==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: sylvain.bertrand@gmail.com Subject: Re: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Fri, 24 May 2019 12:24:56 +0000 Message-ID: <20190524122456.GA483@freedom> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) by gabe.freedesktop.org (Postfix) with ESMTPS id D0BDB6E101 for ; Fri, 24 May 2019 12:25:08 +0000 (UTC) Received: by mail-wm1-x331.google.com with SMTP id z23so4959082wma.4 for ; Fri, 24 May 2019 05:25:08 -0700 (PDT) Content-Disposition: inline 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: bugzilla-daemon@freedesktop.org Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org SXQgc2VlbXMgSSBnZXQgdGhlIHNhbWUgZnJlZXplcyB0aGFuIHlvdS4gSXQgdGFrZXMgaG91cnMg b2YgZ2FtaW5nIHRvIGdldCBzb21lCnJhbmRvbSBoYXJkIGhhbmcgKG5vIGxvZykuIEkgdGhvdWdo dCBJIHdhcyBvdmVyaGVhdGluZywgYnV0IHJlYWxpemVkIHRoYXQgbXkgc3lzdGVtIGlzIG9uCiJ2 YWNhdGlvbiIgd2hpbGUgcGxheWluZy4KbGludXggYW1kLXN0YWdpbmctZHJtLW5ldy94MTEgbmF0 aXZlL21lc2EvbGx2bShlcmsuLi4pLCBhbGwgZ2l0IG5vIG9sZGVyIHRoYW4gYQp3ZWVrLgpwbGF5 aW5nIG1vc3RseSBkb3RhMiB2dWxrYW4gb24gQU1EIFRBSElUSSBYVApfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpkcmktZGV2ZWwgbWFpbGluZyBsaXN0CmRy aS1kZXZlbEBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5mcmVlZGVza3RvcC5v cmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWw= From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Fri, 24 May 2019 12:25:11 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0285478920==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 0F7746E10A for ; Fri, 24 May 2019 12:25:11 +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 --===============0285478920== Content-Type: multipart/alternative; boundary="15587007110.59D189A21.23547" Content-Transfer-Encoding: 7bit --15587007110.59D189A21.23547 Date: Fri, 24 May 2019 12:25:11 +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=3D109955 --- Comment #23 from Sylvain BERTRAND --- It seems I get the same freezes than you. It takes hours of gaming to get s= ome random hard hang (no log). I thought I was overheating, but realized that my system is on "vacation" while playing. linux amd-staging-drm-new/x11 native/mesa/llvm(erk...), all git no older th= an a week. playing mostly dota2 vulkan on AMD TAHITI XT --=20 You are receiving this mail because: You are the assignee for the bug.= --15587007110.59D189A21.23547 Date: Fri, 24 May 2019 12:25:11 +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

Comme= nt # 23 on bug 10995= 5 from Sylvain BERTRAND 
It seems I get the same freezes than you. It takes hours of ga=
ming to get some
random hard hang (no log). I thought I was overheating, but realized that my
system is on
"vacation" while playing.
linux amd-staging-drm-new/x11 native/mesa/llvm(erk...), all git no older th=
an a
week.
playing mostly dota2 vulkan on AMD TAHITI XT

You are receiving this mail because:
  • You are the assignee for the bug.
= --15587007110.59D189A21.23547-- --===============0285478920== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0285478920==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Fri, 24 May 2019 13:44:27 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1020295505==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id D275D6E110 for ; Fri, 24 May 2019 13:44:26 +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 --===============1020295505== Content-Type: multipart/alternative; boundary="15587054662.3b4D2.6661" Content-Transfer-Encoding: 7bit --15587054662.3b4D2.6661 Date: Fri, 24 May 2019 13:44:26 +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=3D109955 --- Comment #24 from Mauro Gaspari --- (In reply to Sylvain BERTRAND from comment #23) > It seems I get the same freezes than you. It takes hours of gaming to get > some > random hard hang (no log). I thought I was overheating, but realized that= my > system is on > "vacation" while playing. > linux amd-staging-drm-new/x11 native/mesa/llvm(erk...), all git no older > than a > week. > playing mostly dota2 vulkan on AMD TAHITI XT Hi, a bit frustrating eh? :) I have been asking around and it seems that RadeonVII and RX590 do not suff= er those issues. Probably related to default clock speeds by manufacturers. Anyway, If you try the kernel parameters I mentioned above, those should he= lp. I have not had crashes in weeks after I enabled those on my grub. And not related to distribution, those grub kernel settings worked for me on Tumbleweed, Arch, Ubuntu Budgie. I hope it helps. --=20 You are receiving this mail because: You are the assignee for the bug.= --15587054662.3b4D2.6661 Date: Fri, 24 May 2019 13:44:26 +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

Comme= nt # 24 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Sylvain BERTRAND from comment #23)
> It seems I get the same freezes than you. It tak=
es hours of gaming to get
> some
> random hard hang (no log). I thought I was overheating, but realized t=
hat my
> system is on
> "vacation" while playing.
> linux amd-staging-drm-new/x11 native/mesa/llvm(erk...), all git no old=
er
> than a
> week.
> playing mostly dota2 vulkan on AMD TAHITI XT

Hi, a bit frustrating eh? :)
I have been asking around and it seems that RadeonVII and RX590 do not suff=
er
those issues. Probably related to default clock speeds by manufacturers.

Anyway, If you try the kernel parameters I mentioned above, those should he=
lp.
I have not had crashes in weeks after I enabled those on my grub. And not
related to distribution, those grub kernel settings worked for me on
Tumbleweed, Arch, Ubuntu Budgie.

I hope it helps.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15587054662.3b4D2.6661-- --===============1020295505== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1020295505==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 03 Jun 2019 08:07:58 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0875082073==" 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 8DE338918E for ; Mon, 3 Jun 2019 08:07:58 +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 --===============0875082073== Content-Type: multipart/alternative; boundary="15595492780.E3c9Af.3145" Content-Transfer-Encoding: 7bit --15595492780.E3c9Af.3145 Date: Mon, 3 Jun 2019 08:07:58 +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=3D109955 --- Comment #25 from Matt Coffin --- (In reply to Mauro Gaspari from comment #24) > Hi, a bit frustrating eh? :) > I have been asking around and it seems that RadeonVII and RX590 do not > suffer those issues. Probably related to default clock speeds by > manufacturers. FWIW, I'm seeing this exact same issue, and I'm on an RX590. --=20 You are receiving this mail because: You are the assignee for the bug.= --15595492780.E3c9Af.3145 Date: Mon, 3 Jun 2019 08:07:58 +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

Comme= nt # 25 on bug 10995= 5 from Matt Coffin 
(In reply to Mauro Gaspari from comment #24)

> Hi, a bit frustrating eh? :)
> I have been asking around and it seems that RadeonVII and RX590 do not
> suffer those issues. Probably related to default clock speeds by
> manufacturers.

FWIW, I'm seeing this exact same issue, and I'm on an RX590.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15595492780.E3c9Af.3145-- --===============0875082073== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0875082073==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 03 Jun 2019 20:10:26 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0508532885==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 1EB588933C for ; Mon, 3 Jun 2019 20:10:26 +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 --===============0508532885== Content-Type: multipart/alternative; boundary="15595926261.ca259e.15217" Content-Transfer-Encoding: 7bit --15595926261.ca259e.15217 Date: Mon, 3 Jun 2019 20:10:26 +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=3D109955 --- Comment #26 from Matt Coffin --- For reproducability, here's what I've been using. (I can reproduce this cra= sh on both the RADV and AMDVLK Vulkan implementations, and can reproduce it bo= th on top of sway 1.1 (wayland), and xfce4 (X11)). * 5.1.3-arch2-1-ARCH * LLVM 8.0.0 * mesa/vulkan-radeon: 19.0.4 * AMDVLK: (dev branch from nighttime Mountain time 20190602) * DXVK: winelib version - release 1.2.1 I run "House Flipper" from Steam with DXVK_FILTER_DEVICE_NAME=3D590. On 1080p@60Hz with v-sync, it runs quite well and stable (for hours). If I disable v-sync and framerate limiting, the crash occurs within a minute usually. At 2560x1440 resolution, no refresh rate works in a stable mannner, but I h= ave tried both 60Hz and 144Hz. With the game rendering 1080p but scaling up to a 2560x1440 display, I saw = it crash once, but was unable to duplicate it again. I'm new to low-level development, and would like to help. If I can provide = any information since I can reliably reproduce the issue, I'd love to. Let me k= now what would be useful and I'd be happy to get it out to you. I've also seen the bugs listed in my other comment on the other bug here: https://bugs.freedesktop.org/show_bug.cgi?id=3D102322#c82 --=20 You are receiving this mail because: You are the assignee for the bug.= --15595926261.ca259e.15217 Date: Mon, 3 Jun 2019 20:10:26 +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

Comme= nt # 26 on bug 10995= 5 from Matt Coffin 
For reproducability, here's what I've been using. (I can repro=
duce this crash
on both the RADV and AMDVLK Vulkan implementations, and can reproduce it bo=
th
on top of sway 1.1 (wayland), and xfce4 (X11)).

* 5.1.3-arch2-1-ARCH
* LLVM 8.0.0
* mesa/vulkan-radeon: 19.0.4
* AMDVLK: (dev branch from nighttime Mountain time 20190602)
* DXVK: winelib version - release 1.2.1

I run "House Flipper" from Steam with DXVK_FILTER_DEVICE_NAME=3D5=
90.

On 1080p@60Hz with v-sync, it runs quite well and stable (for hours). I=
f I
disable v-sync and framerate limiting, the crash occurs within a minute
usually.

At 2560x1440 resolution, no refresh rate works in a stable mannner, but I h=
ave
tried both 60Hz and 144Hz.

With the game rendering 1080p but scaling up to a 2560x1440 display, I saw =
it
crash once, but was unable to duplicate it again.

I'm new to low-level development, and would like to help. If I can provide =
any
information since I can reliably reproduce the issue, I'd love to. Let me k=
now
what would be useful and I'd be happy to get it out to you.

I've also seen the bugs listed in my other comment on the other bug here:
https://bugs.freedesktop.org/show_=
bug.cgi?id=3D102322#c82

You are receiving this mail because:
  • You are the assignee for the bug.
= --15595926261.ca259e.15217-- --===============0508532885== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0508532885==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 04 Jun 2019 21:43:38 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0680219239==" 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 BFDA689C9B for ; Tue, 4 Jun 2019 21:43:38 +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 --===============0680219239== Content-Type: multipart/alternative; boundary="15596846184.27Dc.4914" Content-Transfer-Encoding: 7bit --15596846184.27Dc.4914 Date: Tue, 4 Jun 2019 21:43:38 +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=3D109955 Sam changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |samueldgv@mailbox.org --- Comment #27 from Sam --- Hello! I can confirm that I have the same issues. I am using a Vega 56 and openSUSE Tumbleweed (X11 and KDE) with: Kernel Version: 5.1.5-1-default X Server Release: 12004000 Driver: X.Org Radeon RX Vega (VEGA10, DRM 3.30.0, 5.1.5-1-default, LLVM 7.= 0.1) I have been having the same freezes exactly as described here since, as far= as I can remember, mesa 19.0.4 and 5.0.13 (based on the Tumbleweed snapshots f= rom when this started happening) This was definitely not happening before on mesa 18.x/LLVM 6 and 7 and kern= el 4.20. I niehter run overclocks, never messed with firmware/BIOS...etc. Everything has been running as-is since Oct. 2018 so firmware or BIOS issues should be discarded, I guess. In my case, I have also experienced this issue when running non-demanding OpenGL games and even desktop applications (I had a crash happen on the des= ktop with just WxMaxima, a computer algebra system GUI, opened doing nothing) The easiest way for me to reproduce it is by simply leaving Pillars of Eter= nity (an OpenGL unity game) open and idle for an hour or so. I have tried settin= g up Kdump and trying to catch some error messages in the logs with no luck. I'm definitely open for directions on how to get more info if this can help. --=20 You are receiving this mail because: You are the assignee for the bug.= --15596846184.27Dc.4914 Date: Tue, 4 Jun 2019 21:43:38 +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 Sam changed bug 10995= 5
What Removed Added
CC   samueldgv@mailbox.org

Comme= nt # 27 on bug 10995= 5 from = Sam 
Hello! I can confirm that I have the same issues. I am using a=
 Vega 56 and
openSUSE Tumbleweed (X11 and KDE) with:

Kernel Version:  5.1.5-1-default
X Server Release:  12004000
Driver:  X.Org Radeon RX Vega (VEGA10, DRM 3.30.0, 5.1.5-1-default, LLVM 7.=
0.1)


I have been having the same freezes exactly as described here since, as far=
 as
I can remember, mesa 19.0.4 and 5.0.13 (based on the Tumbleweed snapshots f=
rom
when this started happening)

This was definitely not happening before on mesa 18.x/LLVM 6 and 7 and kern=
el
4.20. I niehter run overclocks, never messed with firmware/BIOS...etc.
Everything has been running as-is since Oct. 2018 so firmware or BIOS issues
should be discarded, I guess.

In my case, I have also experienced this issue when running non-demanding
OpenGL games and even desktop applications (I had a crash happen on the des=
ktop
with just WxMaxima, a computer algebra system GUI, opened doing nothing)

The easiest way for me to reproduce it is by simply leaving Pillars of Eter=
nity
(an OpenGL unity game) open and idle for an hour or so. I have tried settin=
g up
Kdump and trying to catch some error messages in the logs with no luck. I'm
definitely open for directions on how to get more info if this can help.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15596846184.27Dc.4914-- --===============0680219239== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0680219239==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 05 Jun 2019 06:34:02 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1389472596==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 9714B8957B for ; Wed, 5 Jun 2019 06:34:02 +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 --===============1389472596== Content-Type: multipart/alternative; boundary="15597164422.5349F7A.730" Content-Transfer-Encoding: 7bit --15597164422.5349F7A.730 Date: Wed, 5 Jun 2019 06:34:02 +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=3D109955 --- Comment #28 from Mauro Gaspari --- Thanks all for adding comments and testing to this bug. I believe if we pro= ve there is enough people affected on different cards, it will get the attenti= on it needs, and hopefully a permanent mesa fix can be found and implemented. For those affected, if you don't mind testing the kernel parameters workaro= und i described above, and post your results, that would be a nice start. If you need help on how to do that you can reach out to me via PM or email. --=20 You are receiving this mail because: You are the assignee for the bug.= --15597164422.5349F7A.730 Date: Wed, 5 Jun 2019 06:34:02 +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

Comme= nt # 28 on bug 10995= 5 from = Mauro Gaspari 
Thanks all for adding comments and testing to this bug. I beli=
eve if we prove
there is enough people affected on different cards, it will get the attenti=
on
it needs, and hopefully a permanent mesa fix can be found and implemented.

For those affected, if you don't mind testing the kernel parameters workaro=
und
i described above, and post your results, that would be a nice start.
If you need help on how to do that you can reach out to me via PM or email.=

You are receiving this mail because:
  • You are the assignee for the bug.
= --15597164422.5349F7A.730-- --===============1389472596== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1389472596==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 09 Jun 2019 18:46:37 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0037473338==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id EB30D894E3 for ; Sun, 9 Jun 2019 18:46:36 +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 --===============0037473338== Content-Type: multipart/alternative; boundary="15601059960.0c43e.25572" Content-Transfer-Encoding: 7bit --15601059960.0c43e.25572 Date: Sun, 9 Jun 2019 18:46:36 +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=3D109955 --- Comment #29 from Sam --- I have been trying myself for the moment to get some info with just debug parameters: amdgpu.dc=3D1=20 amdgpu.vm_fault_stop=3D2=20 amdgpu.vm_debug=3D1=20 amdgpu.gpu_recovery=3D0=20 Incidentally I couldn't get any freeze to happen after running two troubles= ome games for about two hours each (left idle but on load, Pillars of Eternity = and Surviving Mars) but this could mean anything as they happen completely randomly.=20 Perhaps someone who can reproduce the issue instantly can test the paramete= rs more reliably? --=20 You are receiving this mail because: You are the assignee for the bug.= --15601059960.0c43e.25572 Date: Sun, 9 Jun 2019 18:46:36 +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

Comme= nt # 29 on bug 10995= 5 from = Sam 
I have been trying myself for the moment to get some info with=
 just debug
parameters:

amdgpu.dc=3D1=20
amdgpu.vm_fault_stop=3D2=20
amdgpu.vm_debug=3D1=20
amdgpu.gpu_recovery=3D0=20

Incidentally I couldn't get any freeze to happen after running two troubles=
ome
games for about two hours each (left idle but on load, Pillars of Eternity =
and
Surviving Mars) but this could mean anything as they happen completely
randomly.=20

Perhaps someone who can reproduce the issue instantly can test the paramete=
rs
more reliably?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15601059960.0c43e.25572-- --===============0037473338== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0037473338==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 10 Jun 2019 17:13:57 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1789844013==" 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 64D9089165 for ; Mon, 10 Jun 2019 17:13:57 +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 --===============1789844013== Content-Type: multipart/alternative; boundary="15601868371.6f2efD.31651" Content-Transfer-Encoding: 7bit --15601868371.6f2efD.31651 Date: Mon, 10 Jun 2019 17:13:57 +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=3D109955 --- Comment #30 from Sam --- Update: I can now confirm, at least in my case, that the freezes DO occur u= sing the parameters above, and also with all of them (shown below), while doing another test round on Pillars of Eternity. amdgpu.dc=3D1=20 amdgpu.vm_update_mode=3D0=20 amdgpu.dpm=3D-1=20 amdgpu.ppfeaturemask=3D0xffffffff=20 amdgpu.vm_fault_stop=3D2=20 amdgpu.vm_debug=3D1=20 amdgpu.gpu_recovery=3D0=20 I was continuously writing dmesg to a file but yet again I didn't get any messages/warnings/errors. --=20 You are receiving this mail because: You are the assignee for the bug.= --15601868371.6f2efD.31651 Date: Mon, 10 Jun 2019 17:13:57 +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

Comme= nt # 30 on bug 10995= 5 from = Sam 
Update: I can now confirm, at least in my case, that the freez=
es DO occur using
the parameters above, and also with all of them (shown below), while doing
another test round on Pillars of Eternity.

amdgpu.dc=3D1=20
amdgpu.vm_update_mode=3D0=20
amdgpu.dpm=3D-1=20
amdgpu.ppfeaturemask=3D0xffffffff=20
amdgpu.vm_fault_stop=3D2=20
amdgpu.vm_debug=3D1=20
amdgpu.gpu_recovery=3D0=20

I was continuously writing dmesg to a file but yet again I didn't get any
messages/warnings/errors.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15601868371.6f2efD.31651-- --===============1789844013== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1789844013==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 13 Jun 2019 21:04:11 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0334570473==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 917688930C for ; Thu, 13 Jun 2019 21:04:11 +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 --===============0334570473== Content-Type: multipart/alternative; boundary="15604598513.a3b3dA4fD.14220" Content-Transfer-Encoding: 7bit --15604598513.a3b3dA4fD.14220 Date: Thu, 13 Jun 2019 21:04:11 +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=3D109955 --- Comment #31 from Sam --- I have attached another trace I managed to get today at 22:24 while playing Pillars Of Eternity (OpenGL)=20 It didn't freeze the whole as usual, just the whole Plasma and X sessions, = so the other TTYs were accessible. This is the first occurrence of this happen= ing. I was using the latest kernel default from the openSUSE Kernel:stable repo (5.1.9-5.1), as per request on https://bugzilla.opensuse.org/show_bug.cgi?id=3D1136293 To note that, as in the other dmesgs attached, the crash seems to be caused= by amdgpu. Should the bug category be moved there? --=20 You are receiving this mail because: You are the assignee for the bug.= --15604598513.a3b3dA4fD.14220 Date: Thu, 13 Jun 2019 21:04:11 +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

Comme= nt # 31 on bug 10995= 5 from = Sam 
I have attached another trace I managed to get today at 22:24 =
while playing
Pillars Of Eternity (OpenGL)=20

It didn't freeze the whole as usual, just the whole Plasma and X sessions, =
so
the other TTYs were accessible. This is the first occurrence of this happen=
ing.
I was using the latest kernel default from the openSUSE Kernel:stable repo
(5.1.9-5.1), as per request on
https:/=
/bugzilla.opensuse.org/show_bug.cgi?id=3D1136293

To note that, as in the other dmesgs attached, the crash seems to be caused=
 by
amdgpu. Should the bug category be moved there?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15604598513.a3b3dA4fD.14220-- --===============0334570473== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0334570473==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 13 Jun 2019 21:04:35 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0974528064==" 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 1CF5F8930F for ; Thu, 13 Jun 2019 21:04:35 +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 --===============0974528064== Content-Type: multipart/alternative; boundary="15604598751.18b1f3E4d.14388" Content-Transfer-Encoding: 7bit --15604598751.18b1f3E4d.14388 Date: Thu, 13 Jun 2019 21:04:35 +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=3D109955 --- Comment #32 from Sam --- Created attachment 144535 --> https://bugs.freedesktop.org/attachment.cgi?id=3D144535&action=3Dedit dmesg from the freeze which didn't completely bork everything. It starts on line 1181 --=20 You are receiving this mail because: You are the assignee for the bug.= --15604598751.18b1f3E4d.14388 Date: Thu, 13 Jun 2019 21:04:35 +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

Comme= nt # 32 on bug 10995= 5 from = Sam 
Created attachment 144535 [det=
ails]
dmesg from the freeze which didn't completely bork everything. It starts on
line 1181

You are receiving this mail because:
  • You are the assignee for the bug.
= --15604598751.18b1f3E4d.14388-- --===============0974528064== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0974528064==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Fri, 14 Jun 2019 05:48:33 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0081388390==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 9DE7689241 for ; Fri, 14 Jun 2019 05:48:33 +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 --===============0081388390== Content-Type: multipart/alternative; boundary="15604913131.BB81EAC.23610" Content-Transfer-Encoding: 7bit --15604913131.BB81EAC.23610 Date: Fri, 14 Jun 2019 05:48:33 +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=3D109955 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|dri-devel@lists.freedesktop | |.org | Component|Drivers/Gallium/radeonsi |DRM/AMDgpu Product|Mesa |DRI Version|18.3 |unspecified --- Comment #33 from Jiri Slaby --- (In reply to Sam from comment #32) > Created attachment 144535 [details] > dmesg from the freeze which didn't completely bork everything. It starts = on > line 1181 Attaching the relevant part inline: > [drm:amdgpu_dm_commit_planes.isra.0 [amdgpu]] *ERROR* Waiting for fences = timed out. > [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq= =3D726226, emitted seq=3D726228 > [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process P= illarsOfEterni pid 12250 thread PillarsOfE:cs0 pid 12254 > amdgpu 0000:1e:00.0: GPU reset begin! > [drm:amdgpu_dm_commit_planes.isra.0 [amdgpu]] *ERROR* Waiting for fences = timed out. > amdgpu 0000:1e:00.0: GPU BACO reset > amdgpu 0000:1e:00.0: GPU reset succeeded, trying to resume > [drm] PCIE GART of 512M enabled (table at 0x000000F400900000). > [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* VRAM is lost! > [drm] PSP is resuming... > [drm] reserve 0x400000 from 0xf400d00000 for PSP TMR SIZE > [drm] UVD and UVD ENC initialized successfully. > [drm] VCE initialized successfully. > [drm] recover vram bo from shadow start > [drm] recover vram bo from shadow done > [drm] Skip scheduling IBs! > [drm] Skip scheduling IBs! > amdgpu 0000:1e:00.0: GPU reset(2) succeeded! > [drm] Skip scheduling IBs! > ... > [drm] Skip scheduling IBs! > [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! > [drm] Skip scheduling IBs! > ... > [drm] Skip scheduling IBs! > [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! > [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! > [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! --=20 You are receiving this mail because: You are the assignee for the bug.= --15604913131.BB81EAC.23610 Date: Fri, 14 Jun 2019 05:48:33 +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 Jiri Slaby changed bug 10995= 5
What Removed Added
QA Contact dri-devel@lists.freedesktop.org  
Component Drivers/Gallium/radeonsi DRM/AMDgpu
Product Mesa DRI
Version 18.3 unspecified

Comme= nt # 33 on bug 10995= 5 from Jiri Slaby 
(In reply to Sam from comment #32)
> Created attachment 1445=
35 [details]
> dmesg from the freeze which didn't completely bork everything. It star=
ts on
> line 1181

Attaching the relevant part inline:

> [drm:amdgpu_dm_commit_planes.isra.0 [amdgpu]] *E=
RROR* Waiting for fences timed out.
> [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled =
seq=3D726226, emitted seq=3D726228
> [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: proces=
s PillarsOfEterni pid 12250 thread PillarsOfE:cs0 pid 12254
> amdgpu 0000:1e:00.0: GPU reset begin!
> [drm:amdgpu_dm_commit_planes.isra.0 [amdgpu]] *ERROR* Waiting for fenc=
es timed out.
> amdgpu 0000:1e:00.0: GPU BACO reset
> amdgpu 0000:1e:00.0: GPU reset succeeded, trying to resume
> [drm] PCIE GART of 512M enabled (table at 0x000000F400900000).
> [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* VRAM is lost!
> [drm] PSP is resuming...
> [drm] reserve 0x400000 from 0xf400d00000 for PSP TMR SIZE
> [drm] UVD and UVD ENC initialized successfully.
> [drm] VCE initialized successfully.
> [drm] recover vram bo from shadow start
> [drm] recover vram bo from shadow done
> [drm] Skip scheduling IBs!
> [drm] Skip scheduling IBs!
> amdgpu 0000:1e:00.0: GPU reset(2) succeeded!
> [drm] Skip scheduling IBs!
> ...
> [drm] Skip scheduling IBs!
> [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -12=
5!
> [drm] Skip scheduling IBs!
> ...
> [drm] Skip scheduling IBs!
> [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -12=
5!
> [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -12=
5!
> [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -12=
5!

You are receiving this mail because:
  • You are the assignee for the bug.
= --15604913131.BB81EAC.23610-- --===============0081388390== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0081388390==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Fri, 14 Jun 2019 14:33:47 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0032405569==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id E96A389971 for ; Fri, 14 Jun 2019 14:33:46 +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 --===============0032405569== Content-Type: multipart/alternative; boundary="15605228260.Bdc4c.28303" Content-Transfer-Encoding: 7bit --15605228260.Bdc4c.28303 Date: Fri, 14 Jun 2019 14:33:46 +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=3D109955 --- Comment #34 from Alex Deucher --- (In reply to Jiri Slaby from comment #33) > > amdgpu 0000:1e:00.0: GPU reset(2) succeeded! > > [drm] Skip scheduling IBs! > > ... > > [drm] Skip scheduling IBs! > > [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! > > [drm] Skip scheduling IBs! > > ... > > [drm] Skip scheduling IBs! > > [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! > > [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! > > [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! The GPU reset was successful. You need to restart your desktop environment= to recover. --=20 You are receiving this mail because: You are the assignee for the bug.= --15605228260.Bdc4c.28303 Date: Fri, 14 Jun 2019 14:33:46 +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

Comme= nt # 34 on bug 10995= 5 from Alex Deucher 
(In reply to Jiri Slaby from comment #33)
> > amdgpu 0000:1e:00.0: GPU reset(2) succeeded!
> > [drm] Skip scheduling IBs!
> > ...
> > [drm] Skip scheduling IBs!
> > [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parse=
r -125!
> > [drm] Skip scheduling IBs!
> > ...
> > [drm] Skip scheduling IBs!
> > [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parse=
r -125!
> > [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parse=
r -125!
> > [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parse=
r -125!

The GPU reset was successful.  You need to restart your desktop environment=
 to
recover.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15605228260.Bdc4c.28303-- --===============0032405569== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0032405569==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 06 Jul 2019 09:30:35 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0351459169==" 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 B82416E147 for ; Sat, 6 Jul 2019 09:30:35 +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 --===============0351459169== Content-Type: multipart/alternative; boundary="15624054351.e9a6.9712" Content-Transfer-Encoding: 7bit --15624054351.e9a6.9712 Date: Sat, 6 Jul 2019 09:30:35 +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=3D109955 --- Comment #35 from shadow.archemage@gmail.com --- (In reply to Mauro Gaspari from comment #22) > The only issue I have not being able to reproduce the issue quickly, is to > clearly understand when the issue is resolved by Mesa. It takes hours for= me > to get the freeze sometimes.=20 > If someone has a quick way to trigger system freeze, I am happy to run mo= re > tests. Hi Mauro, The issue happened to me much more frequently when I opted into Steam beta = and ran Monster Hunter: World. Before opting in, the crashes happen around 1-2 hours after the game starts. With Steam beta though, it happens around <5 minutes in. The only change that I noted when I opted into Steam beta was that the games suddenly downloaded some shader pre-caching stuff. Unfortunately, I'm not t= oo familiar with it, and I'm not too sure if it is related to the problem. I am running Manjaro, Gnome 3.32.2, Kernel version 5.1.15-1, Mesa 19.1.1. Let me know if I missed something. Thanks, Eph --=20 You are receiving this mail because: You are the assignee for the bug.= --15624054351.e9a6.9712 Date: Sat, 6 Jul 2019 09:30:35 +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

Comme= nt # 35 on bug 10995= 5 from sh= adow.archemage@gmail.com 
(In reply to Mauro Gaspari from comment #22)

> The only issue I have not being able to reproduc=
e the issue quickly, is to
> clearly understand when the issue is resolved by Mesa. It takes hours =
for me
> to get the freeze sometimes.=20
> If someone has a quick way to trigger system freeze, I am happy to run=
 more
> tests.

Hi Mauro,

The issue happened to me much more frequently when I opted into Steam beta =
and
ran Monster Hunter: World. Before opting in, the crashes happen around 1-2
hours after the game starts. With Steam beta though, it happens around <5
minutes in.

The only change that I noted when I opted into Steam beta was that the games
suddenly downloaded some shader pre-caching stuff. Unfortunately, I'm not t=
oo
familiar with it, and I'm not too sure if it is related to the problem.

I am running Manjaro, Gnome 3.32.2, Kernel version 5.1.15-1, Mesa 19.1.1.
Let me know if I missed something.

Thanks,
Eph

You are receiving this mail because:
  • You are the assignee for the bug.
= --15624054351.e9a6.9712-- --===============0351459169== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0351459169==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 07 Jul 2019 05:31:34 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1082189564==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 82D3A89C48 for ; Sun, 7 Jul 2019 05:31:34 +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 --===============1082189564== Content-Type: multipart/alternative; boundary="15624774941.ffebD2.25711" Content-Transfer-Encoding: 7bit --15624774941.ffebD2.25711 Date: Sun, 7 Jul 2019 05:31:34 +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=3D109955 --- Comment #36 from Mauro Gaspari --- (In reply to shadow.archemage from comment #35) > (In reply to Mauro Gaspari from comment #22) >=20 > > The only issue I have not being able to reproduce the issue quickly, is= to > > clearly understand when the issue is resolved by Mesa. It takes hours f= or me > > to get the freeze sometimes.=20 > > If someone has a quick way to trigger system freeze, I am happy to run = more > > tests. >=20 > Hi Mauro, >=20 > The issue happened to me much more frequently when I opted into Steam beta > and ran Monster Hunter: World. Before opting in, the crashes happen around > 1-2 hours after the game starts. With Steam beta though, it happens around > <5 minutes in. >=20 > The only change that I noted when I opted into Steam beta was that the ga= mes > suddenly downloaded some shader pre-caching stuff. Unfortunately, I'm not > too familiar with it, and I'm not too sure if it is related to the proble= m. >=20 > I am running Manjaro, Gnome 3.32.2, Kernel version 5.1.15-1, Mesa 19.1.1. > Let me know if I missed something. >=20 > Thanks, > Eph I am not an expert, but I am quite sure shaders have a big part in this. If= you can, disable shader caching. There are a few tests you can do: 1. Did you try with the kernel parameters I posted above? I always ran all = the parameters together. GPU+CPU and at the time, I did not have crashes for we= eks on my Vega64. I am using a RadeonVII now and it seems those parameters are = not needed. 2. Valve sponsored an interesting project that removes dependency of AMD Me= sa from LLVM. And instead uses ACO. Valve made this available for Arch based systems via AUR, and Ubuntu based system via PPA. If you want to test it, y= ou can check the posts below. I am going to test this myself on both Arch and Ubuntu.=20 https://steamcommunity.com/games/221410/announcements/detail/16026346096368= 94200 https://steamcommunity.com/app/221410/discussions/0/1640915206474070669/ --=20 You are receiving this mail because: You are the assignee for the bug.= --15624774941.ffebD2.25711 Date: Sun, 7 Jul 2019 05:31:34 +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

Comme= nt # 36 on bug 10995= 5 from = Mauro Gaspari 
(In reply to shadow.archemage from comment #35)
> (In reply to Mauro Gaspari from comment #22)
>=20
> > The only issue I have not being able to reproduce the issue quick=
ly, is to
> > clearly understand when the issue is resolved by Mesa. It takes h=
ours for me
> > to get the freeze sometimes.=20
> > If someone has a quick way to trigger system freeze, I am happy t=
o run more
> > tests.
>=20
> Hi Mauro,
>=20
> The issue happened to me much more frequently when I opted into Steam =
beta
> and ran Monster Hunter: World. Before opting in, the crashes happen ar=
ound
> 1-2 hours after the game starts. With Steam beta though, it happens ar=
ound
> <5 minutes in.
>=20
> The only change that I noted when I opted into Steam beta was that the=
 games
> suddenly downloaded some shader pre-caching stuff. Unfortunately, I'm =
not
> too familiar with it, and I'm not too sure if it is related to the pro=
blem.
>=20
> I am running Manjaro, Gnome 3.32.2, Kernel version 5.1.15-1, Mesa 19.1=
.1.
> Let me know if I missed something.
>=20
> Thanks,
> Eph

I am not an expert, but I am quite sure shaders have a big part in this. If=
 you
can, disable shader caching.
There are a few tests you can do:
1. Did you try with the kernel parameters I posted above? I always ran all =
the
parameters together. GPU+CPU and at the time, I did not have crashes for we=
eks
on my Vega64. I am using a RadeonVII now and it seems those parameters are =
not
needed.
2. Valve sponsored an interesting project that removes dependency of AMD Me=
sa
from LLVM. And instead uses ACO. Valve made this available for Arch based
systems via AUR, and Ubuntu based system via PPA. If you want to test it, y=
ou
can check the posts below. I am going to test this myself on both Arch and
Ubuntu.=20
https://steamcommunity.com/games/221410/announcements/det=
ail/1602634609636894200
https://steamcommunity.com/app/221410/discussions/0/1640915206474=
070669/

You are receiving this mail because:
  • You are the assignee for the bug.
= --15624774941.ffebD2.25711-- --===============1082189564== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1082189564==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 07 Jul 2019 10:55:49 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2103000578==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 9BF1589B78 for ; Sun, 7 Jul 2019 10:55:49 +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 --===============2103000578== Content-Type: multipart/alternative; boundary="15624969495.1aC8f.16400" Content-Transfer-Encoding: 7bit --15624969495.1aC8f.16400 Date: Sun, 7 Jul 2019 10:55:49 +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=3D109955 --- Comment #37 from shadow.archemage@gmail.com --- (In reply to Mauro Gaspari from comment #36) > (In reply to shadow.archemage from comment #35)=20 > I am not an expert, but I am quite sure shaders have a big part in this. = If > you can, disable shader caching. > There are a few tests you can do: > 1. Did you try with the kernel parameters I posted above? I always ran all > the parameters together. GPU+CPU and at the time, I did not have crashes = for > weeks on my Vega64. I am using a RadeonVII now and it seems those paramet= ers > are not needed. I tried the kernel parameters above, and the game still crashed for me. > 2. Valve sponsored an interesting project that removes dependency of AMD > Mesa from LLVM. And instead uses ACO. Valve made this available for Arch > based systems via AUR, and Ubuntu based system via PPA. If you want to te= st > it, you can check the posts below. I am going to test this myself on both > Arch and Ubuntu.=20 > https://steamcommunity.com/games/221410/announcements/detail/ > 1602634609636894200 > https://steamcommunity.com/app/221410/discussions/0/1640915206474070669/ Will check this out, but will also keep an eye on this thread about the res= ults of your tests. Thanks! --=20 You are receiving this mail because: You are the assignee for the bug.= --15624969495.1aC8f.16400 Date: Sun, 7 Jul 2019 10:55:49 +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

Comme= nt # 37 on bug 10995= 5 from sh= adow.archemage@gmail.com 
(In reply to Mauro Gaspari from comment #36)
> (In reply to shadow.archemage from comment #35)=20
> I am not an expert, but I am quite sure shaders have a big part in thi=
s. If
> you can, disable shader caching.
> There are a few tests you can do:
> 1. Did you try with the kernel parameters I posted above? I always ran=
 all
> the parameters together. GPU+CPU and at the time, I did not have crash=
es for
> weeks on my Vega64. I am using a RadeonVII now and it seems those para=
meters
> are not needed.

I tried the kernel parameters above, and the game still crashed for me.

> 2. Valve sponsored an interesting project that r=
emoves dependency of AMD
> Mesa from LLVM. And instead uses ACO. Valve made this available for Ar=
ch
> based systems via AUR, and Ubuntu based system via PPA. If you want to=
 test
> it, you can check the posts below. I am going to test this myself on b=
oth
> Arch and Ubuntu.=20
> https://steamcommunity.com/games/221410/announcements/detail/
> 1602634609636894200
> https://steamcommunity.com/app/221410/discussions/0/16409152=
06474070669/

Will check this out, but will also keep an eye on this thread about the res=
ults
of your tests. Thanks!

You are receiving this mail because:
  • You are the assignee for the bug.
= --15624969495.1aC8f.16400-- --===============2103000578== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============2103000578==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: sylvain.bertrand@gmail.com Subject: Re: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 7 Jul 2019 17:41:26 +0000 Message-ID: <20190707174126.GA1262@freedom> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Received: from mail-wr1-x442.google.com (mail-wr1-x442.google.com [IPv6:2a00:1450:4864:20::442]) by gabe.freedesktop.org (Postfix) with ESMTPS id A8BB08997E for ; Sun, 7 Jul 2019 17:42:12 +0000 (UTC) Received: by mail-wr1-x442.google.com with SMTP id n9so5436185wrr.4 for ; Sun, 07 Jul 2019 10:42:12 -0700 (PDT) Content-Disposition: inline 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: bugzilla-daemon@freedesktop.org Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org T24gU3VuLCBKdWwgMDcsIDIwMTkgYXQgMDU6MzE6MzRBTSArMDAwMCwgYnVnemlsbGEtZGFlbW9u QGZyZWVkZXNrdG9wLm9yZyB3cm90ZToKPiAyLiBWYWx2ZSBzcG9uc29yZWQgYW4gaW50ZXJlc3Rp bmcgcHJvamVjdCB0aGF0IHJlbW92ZXMgZGVwZW5kZW5jeSBvZiBBTUQgTWVzYQo+IGZyb20gTExW TS4gQW5kIGluc3RlYWQgdXNlcyBBQ08uIFZhbHZlIG1hZGUgdGhpcyBhdmFpbGFibGUgZm9yIEFy Y2ggYmFzZWQKPiBzeXN0ZW1zIHZpYSBBVVIsIGFuZCBVYnVudHUgYmFzZWQgc3lzdGVtIHZpYSBQ UEEuIElmIHlvdSB3YW50IHRvIHRlc3QgaXQsIHlvdQo+IGNhbiBjaGVjayB0aGUgcG9zdHMgYmVs b3cuIEkgYW0gZ29pbmcgdG8gdGVzdCB0aGlzIG15c2VsZiBvbiBib3RoIEFyY2ggYW5kCj4gVWJ1 bnR1LiAKPiBodHRwczovL3N0ZWFtY29tbXVuaXR5LmNvbS9nYW1lcy8yMjE0MTAvYW5ub3VuY2Vt ZW50cy9kZXRhaWwvMTYwMjYzNDYwOTYzNjg5NDIwMAo+IGh0dHBzOi8vc3RlYW1jb21tdW5pdHku Y29tL2FwcC8yMjE0MTAvZGlzY3Vzc2lvbnMvMC8xNjQwOTE1MjA2NDc0MDcwNjY5LwoKSHVobyEK CkNvbnM6CiAgICAtIGl0J3MgYysrCiAgICAtIG9ubHkgR0ZYOCBhbmQgR0ZYOSAoSSBoYXZlIEdG WDYgOiggKQogICAgLSBzb21lIG5hc3R5IHB5dGhvbiBzY3JpcHRzICh0aGVyZSBhcmUgdG9ucyBp biBtZXNhKQoKUHJvczoKICAgIC0gaXQncyBzZXZlcmFsIG9yZGVycyBvZiBtYWduaXR1ZGUgbGVz cyBicmFpbiBmKmNrZWQgdGhhbiBsbHZtLgogICAgLSBpdCBpcyBhY3R1YWwgd29ya2luZyBjb2Rl IHdoaWNoIGRvZXMgZGlzam9pbnQgbWVzYSBmcm9tIGxsdm0uCgpjb25jbHVzaW9uOgogICAgLSBm b3IgR0ZYOCBhbmQgR0ZYOSwgaXQncyBsZXNzIHdvcnNlIHRoYW4gbGx2bS4KICAgIC0gSSB3YXMg YXNraW5nIGZvciBhIGNsZWFuIEdDTiBBQkkgZGVmaW5pdGlvbiBkb2N1bWVudCBmcm9tIHNoYWRl cnMKICAgICAgcGVyc3BlY3RpdmUsIG1heWJlIHRoaXMgY29kZSB3aWxsIGhlbHAgdG8gd3JpdGUg b25lIChvciBpdCBpcyBhbiBBTUQKICAgICAgY29uZmlkZW50aWFsIGRvY3VtZW50Pz8pLgoKLS0g ClN5bHZhaW4KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18K ZHJpLWRldmVsIG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0 dHBzOi8vbGlzdHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 07 Jul 2019 17:42:14 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1295137242==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id DA2DA89A0E for ; Sun, 7 Jul 2019 17:42:14 +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 --===============1295137242== Content-Type: multipart/alternative; boundary="15625213342.9C9bD2.31447" Content-Transfer-Encoding: 7bit --15625213342.9C9bD2.31447 Date: Sun, 7 Jul 2019 17:42:14 +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=3D109955 --- Comment #38 from Sylvain BERTRAND --- On Sun, Jul 07, 2019 at 05:31:34AM +0000, bugzilla-daemon@freedesktop.org wrote: > 2. Valve sponsored an interesting project that removes dependency of AMD = Mesa > from LLVM. And instead uses ACO. Valve made this available for Arch based > systems via AUR, and Ubuntu based system via PPA. If you want to test it,= you > can check the posts below. I am going to test this myself on both Arch and > Ubuntu.=20 > https://steamcommunity.com/games/221410/announcements/detail/160263460963= 6894200 > https://steamcommunity.com/app/221410/discussions/0/1640915206474070669/ Huho! Cons: - it's c++ - only GFX8 and GFX9 (I have GFX6 :( ) - some nasty python scripts (there are tons in mesa) Pros: - it's several orders of magnitude less brain f*cked than llvm. - it is actual working code which does disjoint mesa from llvm. conclusion: - for GFX8 and GFX9, it's less worse than llvm. - I was asking for a clean GCN ABI definition document from shaders perspective, maybe this code will help to write one (or it is an AMD confidential document??). --=20 You are receiving this mail because: You are the assignee for the bug.= --15625213342.9C9bD2.31447 Date: Sun, 7 Jul 2019 17:42:14 +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

Comme= nt # 38 on bug 10995= 5 from Sylvain BERTRAND 
On Sun, Jul 07, 2019 at 05:31:34AM +0000, bugzilla-daemon@freedesktop.org
wrote:
> 2. Valve sponsored an interesting project that r=
emoves dependency of AMD Mesa
> from LLVM. And instead uses ACO. Valve made this available for Arch ba=
sed
> systems via AUR, and Ubuntu based system via PPA. If you want to test =
it, you
> can check the posts below. I am going to test this myself on both Arch=
 and
> Ubuntu.=20
> https://steamcommunity.com/games/221410/announcement=
s/detail/1602634609636894200
> https://steamcommunity.com/app/221410/discussions/0/16409152=
06474070669/

Huho!

Cons:
    - it's c++
    - only GFX8 and GFX9 (I have GFX6 :( )
    - some nasty python scripts (there are tons in mesa)

Pros:
    - it's several orders of magnitude less brain f*cked than llvm.
    - it is actual working code which does disjoint mesa from llvm.

conclusion:
    - for GFX8 and GFX9, it's less worse than llvm.
    - I was asking for a clean GCN ABI definition document from shaders
      perspective, maybe this code will help to write one (or it is an AMD
      confidential document??).

You are receiving this mail because:
  • You are the assignee for the bug.
= --15625213342.9C9bD2.31447-- --===============1295137242== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1295137242==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 08 Jul 2019 05:29:56 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1286886188==" 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 C01F4899D4 for ; Mon, 8 Jul 2019 05:29:56 +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 --===============1286886188== Content-Type: multipart/alternative; boundary="15625637965.5cEe56.17399" Content-Transfer-Encoding: 7bit --15625637965.5cEe56.17399 Date: Mon, 8 Jul 2019 05:29:56 +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=3D109955 --- Comment #39 from Samuel Sieb --- (In reply to shadow.archemage from comment #37) > I tried the kernel parameters above, and the game still crashed for me. Are you saying that the game is crashing or the graphics device is? --=20 You are receiving this mail because: You are the assignee for the bug.= --15625637965.5cEe56.17399 Date: Mon, 8 Jul 2019 05:29:56 +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

Comme= nt # 39 on bug 10995= 5 from Samuel Sieb 
(In reply to shadow.archemage from comment #37)
> I tried the kernel parameters above, and the gam=
e still crashed for me.

Are you saying that the game is crashing or the graphics device is?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15625637965.5cEe56.17399-- --===============1286886188== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1286886188==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 09 Jul 2019 14:29:41 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0510036087==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id D511389B60 for ; Tue, 9 Jul 2019 14:29:41 +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 --===============0510036087== Content-Type: multipart/alternative; boundary="15626825813.34dDCf97.12649" Content-Transfer-Encoding: 7bit --15626825813.34dDCf97.12649 Date: Tue, 9 Jul 2019 14:29:41 +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=3D109955 --- Comment #40 from Wilko Bartels --- Since i experience the same issue since june (didnt game much) i want to sh= are my system info. I am on Ryzen 2600X, Vega 56 Pulse, Strix B450. Using Arch 5.1. Tested every Windowmanager i know , tested also 60Hz and 144Hz. The crashes= are totally random. I only play Dota 2. Last friday i played like 6 games in a = row without a single issue. The day after i crashed like 7 times per game. Alwa= ys have to press reset on my PC.=20 Is it know that hits issue related to a kernel or mesa update? I mean it wa= snt always like this no? --=20 You are receiving this mail because: You are the assignee for the bug.= --15626825813.34dDCf97.12649 Date: Tue, 9 Jul 2019 14:29:41 +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

Comme= nt # 40 on bug 10995= 5 from = Wilko Bartels 
Since i experience the same issue since june (didnt game much)=
 i want to share
my system info.
I am on Ryzen 2600X, Vega 56 Pulse, Strix B450. Using Arch 5.1.
Tested every Windowmanager i know , tested also 60Hz and 144Hz. The crashes=
 are
totally random. I only play Dota 2. Last friday i played like 6 games in a =
row
without a single issue. The day after i crashed like 7 times per game. Alwa=
ys
have to press reset on my PC.=20
Is it know that hits issue related to a kernel or mesa update? I mean it wa=
snt
always like this no?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15626825813.34dDCf97.12649-- --===============0510036087== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0510036087==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: sylvain.bertrand@gmail.com Subject: Re: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 9 Jul 2019 18:05:27 +0000 Message-ID: <20190709180527.GA547@freedom> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) by gabe.freedesktop.org (Postfix) with ESMTPS id BFE8F6E086 for ; Tue, 9 Jul 2019 18:06:18 +0000 (UTC) Received: by mail-wm1-x332.google.com with SMTP id x15so4000554wmj.3 for ; Tue, 09 Jul 2019 11:06:18 -0700 (PDT) Content-Disposition: inline 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: bugzilla-daemon@freedesktop.org Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org R3V5cywKCkkgYW0gZ2V0dGluZyBmcmVlemVzIG9uIHRhaGl0aSB4dC9meDk1OTAgcmVjZW50bHku Li4gQnV0IEkgYW0gbm90IGxvZ2dpbmcgYSBidWcgeWV0CmJlY2F1c2UgSSB0aGluayB0aGUgcmVh c29uIGlzIHN1bW1lciBoZWF0LgoKVHJ5IHRvIGdhbWUgd2l0aCBhbiBvcGVuZWQgY29tcHV0ZXIg Y2FzZSB3aXRoIGEgYmlnIGZhbiBibG93aW5nCmludG8gaXQuCl9fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fCmRyaS1kZXZlbCBtYWlsaW5nIGxpc3QKZHJpLWRl dmVsQGxpc3RzLmZyZWVkZXNrdG9wLm9yZwpodHRwczovL2xpc3RzLmZyZWVkZXNrdG9wLm9yZy9t YWlsbWFuL2xpc3RpbmZvL2RyaS1kZXZlbA== From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 09 Jul 2019 18:06:21 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0157411796==" 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 03A7D6E098 for ; Tue, 9 Jul 2019 18:06:21 +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 --===============0157411796== Content-Type: multipart/alternative; boundary="15626955803.96A3.14044" Content-Transfer-Encoding: 7bit --15626955803.96A3.14044 Date: Tue, 9 Jul 2019 18:06:20 +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=3D109955 --- Comment #41 from Sylvain BERTRAND --- Guys, I am getting freezes on tahiti xt/fx9590 recently... But I am not logging a= bug yet because I think the reason is summer heat. Try to game with an opened computer case with a big fan blowing into it. --=20 You are receiving this mail because: You are the assignee for the bug.= --15626955803.96A3.14044 Date: Tue, 9 Jul 2019 18:06:20 +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

Comme= nt # 41 on bug 10995= 5 from Sylvain BERTRAND 
Guys,

I am getting freezes on tahiti xt/fx9590 recently... But I am not logging a=
 bug
yet
because I think the reason is summer heat.

Try to game with an opened computer case with a big fan blowing
into it.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15626955803.96A3.14044-- --===============0157411796== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0157411796==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 10 Jul 2019 07:25:35 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0431399851==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id A538489D5F for ; Wed, 10 Jul 2019 07:25:35 +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 --===============0431399851== Content-Type: multipart/alternative; boundary="15627435353.F0F6e30.4301" Content-Transfer-Encoding: 7bit --15627435353.F0F6e30.4301 Date: Wed, 10 Jul 2019 07:25:35 +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=3D109955 --- Comment #43 from Mauro Gaspari --- Hi, No it was not always like this. I was using Kubuntu and my games were really smooth for months. Zero crashes. Then after a mesa update, I do not recall exactly the version but was around 18.5 or something like that, it all got worse.=20 Same game on same PC same hardware same power supply, same cooling, but on windows, zero crashes. same game on same PC with NVIDIA gpu, zero crashes. I wish we could get the attention of someone @AMD because there is clearly = some issue going on. I would be very happy to help troubleshooting, if only we h= ad some contact with AMD.=20 I have not used AMDGPU-PRO in ages, anyone here got that one to check if the same issue happens with proprietary drivers? --=20 You are receiving this mail because: You are the assignee for the bug.= --15627435353.F0F6e30.4301 Date: Wed, 10 Jul 2019 07:25:35 +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

Comme= nt # 43 on bug 10995= 5 from = Mauro Gaspari 
Hi,
No it was not always like this. I was using Kubuntu and my games were really
smooth for months. Zero crashes. Then after a mesa update, I do not recall
exactly the version but was around 18.5 or something like that, it all got
worse.=20

Same game on same PC same hardware same power supply, same cooling, but on
windows, zero crashes.
same game on same PC with NVIDIA gpu, zero crashes.

I wish we could get the attention of someone @AMD because there is clea=
rly some
issue going on. I would be very happy to help troubleshooting, if only we h=
ad
some contact with AMD.=20

I have not used AMDGPU-PRO in ages, anyone here got that one to check if the
same issue happens with proprietary drivers?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15627435353.F0F6e30.4301-- --===============0431399851== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0431399851==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 10 Jul 2019 08:03:07 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0600537286==" 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 9CA916E0B9 for ; Wed, 10 Jul 2019 08:03:07 +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 --===============0600537286== Content-Type: multipart/alternative; boundary="15627457874.Ece66ddac.8521" Content-Transfer-Encoding: 7bit --15627457874.Ece66ddac.8521 Date: Wed, 10 Jul 2019 08:03:07 +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=3D109955 --- Comment #44 from Wilko Bartels --- (In reply to Mauro Gaspari from comment #43) > Hi, > No it was not always like this. I was using Kubuntu and my games were rea= lly > smooth for months. Zero crashes. Then after a mesa update, I do not recall > exactly the version but was around 18.5 or something like that, it all got > worse.=20 >=20 > Same game on same PC same hardware same power supply, same cooling, but on > windows, zero crashes. > same game on same PC with NVIDIA gpu, zero crashes. >=20 > I wish we could get the attention of someone @AMD because there is clearly > some issue going on. I would be very happy to help troubleshooting, if on= ly > we had some contact with AMD.=20 >=20 > I have not used AMDGPU-PRO in ages, anyone here got that one to check if = the > same issue happens with proprietary drivers? I was also thinking about GPU-PRO but i would want to install Ubuntu LTS on another disk then. That might take several weeks for me to test or even lon= ger. And i am not even sure if thats super helpful. Im pretty sure at least on A= rch at the end of 2018 i had zero problems. At least with my Vega ;-) Maybe i was wrong switching from green to red after 10 years. hehe --=20 You are receiving this mail because: You are the assignee for the bug.= --15627457874.Ece66ddac.8521 Date: Wed, 10 Jul 2019 08:03:07 +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

Comme= nt # 44 on bug 10995= 5 from = Wilko Bartels 
(In reply to Mauro Gaspari from comment #43)
> Hi,
> No it was not always like this. I was using Kubuntu and my games were =
really
> smooth for months. Zero crashes. Then after a mesa update, I do not re=
call
> exactly the version but was around 18.5 or something like that, it all=
 got
> worse.=20
>=20
> Same game on same PC same hardware same power supply, same cooling, bu=
t on
> windows, zero crashes.
> same game on same PC with NVIDIA gpu, zero crashes.
>=20
> I wish we could get the attention of someone @AMD because there is=
 clearly
> some issue going on. I would be very happy to help troubleshooting, if=
 only
> we had some contact with AMD.=20
>=20
> I have not used AMDGPU-PRO in ages, anyone here got that one to check =
if the
> same issue happens with proprietary drivers?

I was also thinking about GPU-PRO but i would want to install Ubuntu LTS on
another disk then. That might take several weeks for me to test or even lon=
ger.
And i am not even sure if thats super helpful. Im pretty sure at least on A=
rch
at the end of 2018 i had zero problems. At least with my Vega ;-)
Maybe i was wrong switching from green to red after 10 years. hehe

You are receiving this mail because:
  • You are the assignee for the bug.
= --15627457874.Ece66ddac.8521-- --===============0600537286== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0600537286==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 10 Jul 2019 08:19:30 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0929312626==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id C6B05891F2 for ; Wed, 10 Jul 2019 08:19:29 +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 --===============0929312626== Content-Type: multipart/alternative; boundary="15627467691.5CeE411e.11133" Content-Transfer-Encoding: 7bit --15627467691.5CeE411e.11133 Date: Wed, 10 Jul 2019 08:19:29 +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=3D109955 --- Comment #45 from Wilko Bartels --- (In reply to Mauro Gaspari from comment #43) > Hi, > No it was not always like this. I was using Kubuntu and my games were rea= lly > smooth for months. Zero crashes. Then after a mesa update, I do not recall > exactly the version but was around 18.5 or something like that, it all got > worse.=20 But it is proven that Mesa is the problem here? There was once an issue regarding linux-firmware package in early 2018 if i remember correctly. Use= rs had to rollback back than. I might rollback to mesa 18.3 to test if i can manage that regardless. --=20 You are receiving this mail because: You are the assignee for the bug.= --15627467691.5CeE411e.11133 Date: Wed, 10 Jul 2019 08:19:29 +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

Comme= nt # 45 on bug 10995= 5 from = Wilko Bartels 
(In reply to Mauro Gaspari from comment #43)
> Hi,
> No it was not always like this. I was using Kubuntu and my games were =
really
> smooth for months. Zero crashes. Then after a mesa update, I do not re=
call
> exactly the version but was around 18.5 or something like that, it all=
 got
> worse. 
But it is proven that Mesa is the problem here?  There was once an issue
regarding linux-firmware package in early 2018 if i remember correctly. Use=
rs
had to rollback back than.
I might rollback to mesa 18.3 to test if i can manage that regardless.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15627467691.5CeE411e.11133-- --===============0929312626== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0929312626==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 10 Jul 2019 08:26:23 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1782206931==" 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 B2B446E0C9 for ; Wed, 10 Jul 2019 08:26:23 +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 --===============1782206931== Content-Type: multipart/alternative; boundary="15627471832.A11cC.12337" Content-Transfer-Encoding: 7bit --15627471832.A11cC.12337 Date: Wed, 10 Jul 2019 08:26:23 +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=3D109955 --- Comment #46 from Mauro Gaspari --- This is exactly the reason why I wish we could get more attention to this issue.=20 I have seen so many people in forums on the internet replacing their AMD ca= rds with NVIDIA due to similar issues. Or switching back to windows.=20 I do not have the proof that the issue is just Mesa, could be a combination= of mesa, kernel, firmware for all I know.=20 I opened this bug to see if I could get help troubleshooting the issue and finding a permanent fix for all affected users. If there is a better place = to report this, I am happy to open as many tickets and sending as many emails = as needed :) Also It would be extremely helpful if we had a script or something to trigg= er the freeze quickly and consistently, so that troubleshooting mesa, kernel, = ad firmware combinations would be so much easier and reliable.=20 If anyone has a test suite or script or some automated check that can trigg= er the issue quickly, please share. --=20 You are receiving this mail because: You are the assignee for the bug.= --15627471832.A11cC.12337 Date: Wed, 10 Jul 2019 08:26:23 +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

Comme= nt # 46 on bug 10995= 5 from = Mauro Gaspari 
This is exactly the reason why I wish we could get more attent=
ion to this
issue.=20
I have seen so many people in forums on the internet replacing their AMD ca=
rds
with NVIDIA due to similar issues. Or switching back to windows.=20

I do not have the proof that the issue is just Mesa, could be a combination=
 of
mesa, kernel, firmware for all I know.=20

I  opened this bug to see if I could get help troubleshooting the issue and
finding a permanent fix for all affected users. If there is a better place =
to
report this, I am happy to open as many tickets and sending as many emails =
as
needed :)

Also It would be extremely helpful if we had a script or something to trigg=
er
the freeze quickly and consistently, so that troubleshooting mesa, kernel, =
ad
firmware combinations would be so much easier and reliable.=20
If anyone has a test suite or script or some automated check that can trigg=
er
the issue quickly, please share.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15627471832.A11cC.12337-- --===============1782206931== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1782206931==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 10 Jul 2019 09:41:22 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1124032961==" 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 5087389EB1 for ; Wed, 10 Jul 2019 09:41:22 +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 --===============1124032961== Content-Type: multipart/alternative; boundary="15627516824.0aFeCF08b.22009" Content-Transfer-Encoding: 7bit --15627516824.0aFeCF08b.22009 Date: Wed, 10 Jul 2019 09:41:22 +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=3D109955 --- Comment #47 from Sam --- The relevant issue and bug report here (the system freezing completely or if lucky just killing the X session, NOT games crashing) seems to be related exclusively to AMDGPU, and not to mesa. Whereas I got the same issues over = and over after trying out several versions of mesa, switching to older versions= of the kernel "fixes" it for me (the latest version I tried out which didn't h= ave these issues is Kernel 4.20.13, in my case from https://download.opensuse.org/repositories/home:/tiwai:/kernel:/4.20/standa= rd/x86_64/) There is also a report from another user which temporarily fixed it by forc= ing the gpu to run at the maximum power setting (https://bugzilla.opensuse.org/show_bug.cgi?id=3D1136293): # echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_lev= el # echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk and then to reset back to normal: # echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_level --=20 You are receiving this mail because: You are the assignee for the bug.= --15627516824.0aFeCF08b.22009 Date: Wed, 10 Jul 2019 09:41:22 +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

Comme= nt # 47 on bug 10995= 5 from = Sam 
The relevant issue and bug report here (the system freezing co=
mpletely or if
lucky just killing the X session, NOT games crashing) seems to be related
exclusively to AMDGPU, and not to mesa. Whereas I got the same issues over =
and
over after trying out several versions of mesa, switching to older versions=
 of
the kernel "fixes" it for me (the latest version I tried out whic=
h didn't have
these issues is Kernel 4.20.13, in my case from
https://download.opensuse.org/repositories/home:/tiw=
ai:/kernel:/4.20/standard/x86_64/)

There is also a report from another user which temporarily fixed it by forc=
ing
the gpu to run at the maximum power setting
(https:=
//bugzilla.opensuse.org/show_bug.cgi?id=3D1136293):

# echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_=
level
# echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk

and then to reset back to normal:

# echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_le=
vel

You are receiving this mail because:
  • You are the assignee for the bug.
= --15627516824.0aFeCF08b.22009-- --===============1124032961== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1124032961==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 10 Jul 2019 14:44:21 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1129848357==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 497AF6E0E4 for ; Wed, 10 Jul 2019 14:44:22 +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 --===============1129848357== Content-Type: multipart/alternative; boundary="15627698624.5d7F9Ff.30406" Content-Transfer-Encoding: 7bit --15627698624.5d7F9Ff.30406 Date: Wed, 10 Jul 2019 14:44:22 +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=3D109955 --- Comment #48 from Mauro Gaspari --- @Sam, Thank you, this is helpful. Since it is not distribution specific and not m= esa related, do you think we should keep the bug here, merge it with other simi= lar bugs, or create on other bug tracking? Happy to help and troubleshoot more from my side, and/or push for this to be resolved once and for all, for all AMDGPU users. Thanks Mauro --=20 You are receiving this mail because: You are the assignee for the bug.= --15627698624.5d7F9Ff.30406 Date: Wed, 10 Jul 2019 14:44:22 +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

Comme= nt # 48 on bug 10995= 5 from = Mauro Gaspari 
@Sam,

Thank you, this is helpful. Since it is not distribution specific and not m=
esa
related, do you think we should keep the bug here, merge it with other simi=
lar
bugs, or create on other bug tracking?
Happy to help and troubleshoot more from my side, and/or push for this to be
resolved once and for all, for all AMDGPU users.

Thanks
Mauro

You are receiving this mail because:
  • You are the assignee for the bug.
= --15627698624.5d7F9Ff.30406-- --===============1129848357== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1129848357==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 10 Jul 2019 18:42:53 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1467293421==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 722116E123 for ; Wed, 10 Jul 2019 18:42:53 +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 --===============1467293421== Content-Type: multipart/alternative; boundary="15627841734.f387c9.2918" Content-Transfer-Encoding: 7bit --15627841734.f387c9.2918 Date: Wed, 10 Jul 2019 18:42:53 +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=3D109955 --- Comment #49 from Wilko Bartels --- (In reply to Sam from comment #47) > The relevant issue and bug report here (the system freezing completely or= if > lucky just killing the X session, NOT games crashing) seems to be related > exclusively to AMDGPU, and not to mesa. Whereas I got the same issues over > and over after trying out several versions of mesa, switching to older > versions of the kernel "fixes" it for me (the latest version I tried out > which didn't have these issues is Kernel 4.20.13, in my case from > https://download.opensuse.org/repositories/home:/tiwai:/kernel:/4.20/ > standard/x86_64/) >=20 > There is also a report from another user which temporarily fixed it by > forcing the gpu to run at the maximum power setting > (https://bugzilla.opensuse.org/show_bug.cgi?id=3D1136293): >=20 > # echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_l= evel > # echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk >=20 > and then to reset back to normal: >=20 > # echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_lev= el I am currently on my 4th game of dota in a row when setting performance lev= el manual to 7. working so far. Everyone should test this now so we have more reliable data. As we all now the issue can be gone for several hours so my experience means nothing yet.=20 Would be amazing if we can pin down the issue to the performance level of = the cards. --=20 You are receiving this mail because: You are the assignee for the bug.= --15627841734.f387c9.2918 Date: Wed, 10 Jul 2019 18:42:53 +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

Comme= nt # 49 on bug 10995= 5 from = Wilko Bartels 
(In reply to Sam from comment #47)
> The relevant issue and bug report here (the syst=
em freezing completely or if
> lucky just killing the X session, NOT games crashing) seems to be rela=
ted
> exclusively to AMDGPU, and not to mesa. Whereas I got the same issues =
over
> and over after trying out several versions of mesa, switching to older
> versions of the kernel "fixes" it for me (the latest version=
 I tried out
> which didn't have these issues is Kernel 4.20.13, in my case from
> https://download.opensuse.org/repositories/home:/tiwai:/kernel:=
/4.20/
> standard/x86_64/)
>=20
> There is also a report from another user which temporarily fixed it by
> forcing the gpu to run at the maximum power setting
> (h=
ttps://bugzilla.opensuse.org/show_bug.cgi?id=3D1136293):
>=20
> # echo manual > /sys/class/drm/card0/device/power_dpm_force_perform=
ance_level
> # echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk
>=20
> and then to reset back to normal:
>=20
> # echo auto > /sys/class/drm/card0/device/power_dpm_force_performan=
ce_level

I am currently on my 4th game of dota in a row when setting performance lev=
el
manual to 7. working so far. Everyone should test this now so we have more
reliable data. As we all now the issue can be gone for several hours so my
experience means nothing yet.=20
Would be amazing if we can pin down the issue to the  performance level of =
the
cards.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15627841734.f387c9.2918-- --===============1467293421== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1467293421==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Fri, 12 Jul 2019 15:26:39 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1330148864==" 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 70C3B6E113 for ; Fri, 12 Jul 2019 15:26:39 +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 --===============1330148864== Content-Type: multipart/alternative; boundary="15629451994.FA9eD2B.25407" Content-Transfer-Encoding: 7bit --15629451994.FA9eD2B.25407 Date: Fri, 12 Jul 2019 15:26:39 +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=3D109955 --- Comment #50 from shadow.archemage@gmail.com --- (In reply to Samuel Sieb from comment #39) > (In reply to shadow.archemage from comment #37) > > I tried the kernel parameters above, and the game still crashed for me. >=20 > Are you saying that the game is crashing or the graphics device is? Apologies, what I meant by this is that my system locks up, not just the ga= me crashing. I can't recover from it except by resetting my PC using the power button. --=20 You are receiving this mail because: You are the assignee for the bug.= --15629451994.FA9eD2B.25407 Date: Fri, 12 Jul 2019 15:26:39 +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

Comme= nt # 50 on bug 10995= 5 from sh= adow.archemage@gmail.com 
(In reply to Samuel Sieb from comment #39)
> (In reply to shadow.archemage from comment #37)
> > I tried the kernel parameters above, and the game still crashed f=
or me.
>=20
> Are you saying that the game is crashing or the graphics device is?

Apologies, what I meant by this is that my system locks up, not just the ga=
me
crashing. I can't recover from it except by resetting my PC using the power
button.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15629451994.FA9eD2B.25407-- --===============1330148864== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1330148864==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 13 Jul 2019 17:22:41 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0946661762==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 1E3D189D30 for ; Sat, 13 Jul 2019 17:22:41 +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 --===============0946661762== Content-Type: multipart/alternative; boundary="15630385611.aBeE6BBC7.16922" Content-Transfer-Encoding: 7bit --15630385611.aBeE6BBC7.16922 Date: Sat, 13 Jul 2019 17:22:41 +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=3D109955 --- Comment #51 from shadow.archemage@gmail.com --- (In reply to Wilko Bartels from comment #49) > (In reply to Sam from comment #47) > > The relevant issue and bug report here (the system freezing completely = or if > > lucky just killing the X session, NOT games crashing) seems to be relat= ed > > exclusively to AMDGPU, and not to mesa. Whereas I got the same issues o= ver > > and over after trying out several versions of mesa, switching to older > > versions of the kernel "fixes" it for me (the latest version I tried out > > which didn't have these issues is Kernel 4.20.13, in my case from > > https://download.opensuse.org/repositories/home:/tiwai:/kernel:/4.20/ > > standard/x86_64/) > >=20 > > There is also a report from another user which temporarily fixed it by > > forcing the gpu to run at the maximum power setting > > (https://bugzilla.opensuse.org/show_bug.cgi?id=3D1136293): > >=20 > > # echo manual > /sys/class/drm/card0/device/power_dpm_force_performance= _level > > # echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk > >=20 > > and then to reset back to normal: > >=20 > > # echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_l= evel >=20 > I am currently on my 4th game of dota in a row when setting performance > level manual to 7. working so far. Everyone should test this now so we ha= ve > more reliable data. As we all now the issue can be gone for several hours= so > my experience means nothing yet.=20 > Would be amazing if we can pin down the issue to the performance level of > the cards. Played Monster Hunter and Dota 2 for quite a long time, and I didn't experi= ence any system freezes with the max performance settings. Will test again tomor= row to see if the workaround is consistent enough. --=20 You are receiving this mail because: You are the assignee for the bug.= --15630385611.aBeE6BBC7.16922 Date: Sat, 13 Jul 2019 17:22:41 +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

Comme= nt # 51 on bug 10995= 5 from sh= adow.archemage@gmail.com 
(In reply to Wilko Bartels from comment #49)
> (In reply to Sam from comment #47)
> > The relevant issue and bug report here (the system freezing compl=
etely or if
> > lucky just killing the X session, NOT games crashing) seems to be=
 related
> > exclusively to AMDGPU, and not to mesa. Whereas I got the same is=
sues over
> > and over after trying out several versions of mesa, switching to =
older
> > versions of the kernel "fixes" it for me (the latest ve=
rsion I tried out
> > which didn't have these issues is Kernel 4.20.13, in my case from
> > https://download.opensuse.org/repositories/home:/tiwai:/ke=
rnel:/4.20/
> > standard/x86_64/)
> >=20
> > There is also a report from another user which temporarily fixed =
it by
> > forcing the gpu to run at the maximum power setting
> > (https://bugzilla.opensuse.org/show_bug.cgi?id=3D1136293):
> >=20
> > # echo manual > /sys/class/drm/card0/device/power_dpm_force_pe=
rformance_level
> > # echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk
> >=20
> > and then to reset back to normal:
> >=20
> > # echo auto > /sys/class/drm/card0/device/power_dpm_force_perf=
ormance_level
>=20
> I am currently on my 4th game of dota in a row when setting performance
> level manual to 7. working so far. Everyone should test this now so we=
 have
> more reliable data. As we all now the issue can be gone for several ho=
urs so
> my experience means nothing yet.=20
> Would be amazing if we can pin down the issue to the  performance leve=
l of
> the cards.

Played Monster Hunter and Dota 2 for quite a long time, and I didn't experi=
ence
any system freezes with the max performance settings. Will test again tomor=
row
to see if the workaround is consistent enough.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15630385611.aBeE6BBC7.16922-- --===============0946661762== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0946661762==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 16 Jul 2019 08:28:22 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2046598171==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 594C26E0C5 for ; Tue, 16 Jul 2019 08:28:22 +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 --===============2046598171== Content-Type: multipart/alternative; boundary="15632657023.528cfc.25369" Content-Transfer-Encoding: 7bit --15632657023.528cfc.25369 Date: Tue, 16 Jul 2019 08:28:22 +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=3D109955 --- Comment #52 from Wilko Bartels --- i played like 30 dota 2 matches withour a single freeze. its save to say th= is is it. where is the right place to report this issue? --=20 You are receiving this mail because: You are the assignee for the bug.= --15632657023.528cfc.25369 Date: Tue, 16 Jul 2019 08:28:22 +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

Comme= nt # 52 on bug 10995= 5 from = Wilko Bartels 
i played like 30 dota 2 matches withour a single freeze. its s=
ave to say this
is it. where is the right place to report this issue?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15632657023.528cfc.25369-- --===============2046598171== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============2046598171==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 17 Jul 2019 03:34:31 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0288206276==" 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 D114689C6A for ; Wed, 17 Jul 2019 03:34:31 +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 --===============0288206276== Content-Type: multipart/alternative; boundary="15633344714.dE9FcB.16110" Content-Transfer-Encoding: 7bit --15633344714.dE9FcB.16110 Date: Wed, 17 Jul 2019 03:34:31 +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=3D109955 --- Comment #53 from Mauro Gaspari --- Thank you all for the great work. I will post on AMD support forums and add the link of this and other AMDGPU related bugs. --=20 You are receiving this mail because: You are the assignee for the bug.= --15633344714.dE9FcB.16110 Date: Wed, 17 Jul 2019 03:34:31 +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

Comme= nt # 53 on bug 10995= 5 from = Mauro Gaspari 
Thank you all for the great work.
I will post on AMD support forums and add the link of this and other AMDGPU
related bugs.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15633344714.dE9FcB.16110-- --===============0288206276== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0288206276==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: sylvain.bertrand@gmail.com Subject: Re: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 17 Jul 2019 16:02:22 +0000 Message-ID: <20190717160222.GA474@freedom> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) by gabe.freedesktop.org (Postfix) with ESMTPS id 2F0976E0DB for ; Wed, 17 Jul 2019 16:02:30 +0000 (UTC) Received: by mail-wr1-x431.google.com with SMTP id f9so25394799wre.12 for ; Wed, 17 Jul 2019 09:02:30 -0700 (PDT) Content-Disposition: inline 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: bugzilla-daemon@freedesktop.org Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org cG93ZXIgbWFuYWdlbWVudCByZWxhdGVkIGNvZGUgaXMgaW4gYW1kZ3B1LCB0aGVuIHRoZSByaWdo dCBwbGFjZSBpcyBoZXJlLCB0aGUgImRyaSIgYW5kCiJhbWRnZngiIG1haWxpbmcgbGlzdHMgKGFr YSBsaW51eCBncHUgZHJpdmVyIG1haWxpbmcgbGlzdHMpLgoKQXMgZmFyIGFzIEkgYW0gY29uY2Vy bmVkLCB3aGVuIEkgcGxheSBkb3RhMiwgSSBhbHdheXMgc3dpdGNoIHRoZSBHUFUgZHBtIHRvCmhp Z2ggYW5kIHRoZSBDUFUgZnJlcSBnb3Zlcm5vciB0byBwZXJmIChiZWNhdXNlLCBhbGwgdGhvc2Ug dGhpbmdzIHN0ZWFsIGEKc2lnbmlmaWNhbnQgYW1vdW50IG9mIGZwcy4uLiBhY3R1YWxseSwgSSBk byBzd2l0Y2ggbXkgR1BVIGRwbSB0byBoaWdoIGp1c3QgaW4KY2FzZSBpdCB3b3VsZCBiZSBuYXN0 eSBsaWtlIHRoZSBjcHUgZ292ZXJub3IpLgoKLS0gClN5bHZhaW4KX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVsIG1haWxpbmcgbGlzdApkcmkt ZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlzdHMuZnJlZWRlc2t0b3Aub3Jn L21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 17 Jul 2019 16:02:32 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0395320240==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id A71EE6E294 for ; Wed, 17 Jul 2019 16:02:32 +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 --===============0395320240== Content-Type: multipart/alternative; boundary="15633793527.fdA54eFa.8802" Content-Transfer-Encoding: 7bit --15633793527.fdA54eFa.8802 Date: Wed, 17 Jul 2019 16:02:32 +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=3D109955 --- Comment #54 from Sylvain BERTRAND --- power management related code is in amdgpu, then the right place is here, t= he "dri" and "amdgfx" mailing lists (aka linux gpu driver mailing lists). As far as I am concerned, when I play dota2, I always switch the GPU dpm to high and the CPU freq governor to perf (because, all those things steal a significant amount of fps... actually, I do switch my GPU dpm to high just = in case it would be nasty like the cpu governor). --=20 You are receiving this mail because: You are the assignee for the bug.= --15633793527.fdA54eFa.8802 Date: Wed, 17 Jul 2019 16:02:32 +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

Comme= nt # 54 on bug 10995= 5 from Sylvain BERTRAND 
power management related code is in amdgpu, then the right pla=
ce is here, the
"dri" and
"amdgfx" mailing lists (aka linux gpu driver mailing lists).

As far as I am concerned, when I play dota2, I always switch the GPU dpm to
high and the CPU freq governor to perf (because, all those things steal a
significant amount of fps... actually, I do switch my GPU dpm to high just =
in
case it would be nasty like the cpu governor).

You are receiving this mail because:
  • You are the assignee for the bug.
= --15633793527.fdA54eFa.8802-- --===============0395320240== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0395320240==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 18 Jul 2019 02:30:29 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1160460111==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id A48F86E2F5 for ; Thu, 18 Jul 2019 02:30:29 +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 --===============1160460111== Content-Type: multipart/alternative; boundary="15634170292.e6e3C088b.13593" Content-Transfer-Encoding: 7bit --15634170292.e6e3C088b.13593 Date: Thu, 18 Jul 2019 02:30:29 +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=3D109955 --- Comment #55 from Hadet --- So I think this might have something to do with something Xorg is doing bec= ause I've not had it happen while gaming for many hours since just seeing if it happened on wayland on a whim. I now have 21 hours of uptime with no random crashes. --=20 You are receiving this mail because: You are the assignee for the bug.= --15634170292.e6e3C088b.13593 Date: Thu, 18 Jul 2019 02:30:29 +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

Comme= nt # 55 on bug 10995= 5 from = Hadet 
So I think this might have something to do with something Xorg=
 is doing because
I've not had it happen while gaming for many hours since just seeing if it
happened on wayland on a whim. I now have 21 hours of uptime with no random
crashes.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15634170292.e6e3C088b.13593-- --===============1160460111== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1160460111==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: sylvain.bertrand@gmail.com Subject: Re: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 18 Jul 2019 13:44:17 +0000 Message-ID: <20190718134417.GA496@freedom> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) by gabe.freedesktop.org (Postfix) with ESMTPS id 0CFE76E3C7 for ; Thu, 18 Jul 2019 13:44:27 +0000 (UTC) Received: by mail-wr1-x42f.google.com with SMTP id r1so28750909wrl.7 for ; Thu, 18 Jul 2019 06:44:26 -0700 (PDT) Content-Disposition: inline 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: bugzilla-daemon@freedesktop.org Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org UGxheWluZyBkb3RhMiB2dWxrYW4gb3IgR0w/CgpJIGd1ZXNzIGl0J3MgdnVsa2FuOiBhbmQgdGhl cmUgSSBkb24ndCBrbm93IGhvdyB2dWxrYW4gZGVhbCB3aXRoIG11bHRpcGxlIFdTSXMsCmFuZCBo b3cgZG90YTIgc2VsZWN0cyB0aGUgb25lIGl0IHdpbGwgdXNlLgoKVGhlIGlkZWEgaXMgdG8gY2xl YXJseSBpZGVudGlmeSB0aGUgY29kZSBwYXRocyB3aGljaCB3b3VsZCBiZSAiYnVnZ3kiLgoKKG15 IGN1c3RvbSBkaXN0cm8gaXMgeDExIG5hdGl2ZSkKClRoYXQgc2FpZCwgSSBkb24ndCBrbm93IHRo ZSBzdGF0dXMgb2Ygd2F5bGFuZDogZGlkIHRoZXkgcmVhY2ggdGhlIHNhbWUgImNsdXN0ZXIKZipj ayIgbGV2ZWwgdGhhdCB4MTEgaXMgYXQ/IChpcm9ueSwgc2luY2Ugd2F5bGFuZCByZWFzb24gdG8g ZXhpc3QgaXMgdG8gYmUKb3JkZXJzIG9mIG1hZ25pdHVkZSBsZXNzIGtsdWRneSB0aGFuIHgxMSkK Ci0tIApTeWx2YWluCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fCmRyaS1kZXZlbCBtYWlsaW5nIGxpc3QKZHJpLWRldmVsQGxpc3RzLmZyZWVkZXNrdG9wLm9y ZwpodHRwczovL2xpc3RzLmZyZWVkZXNrdG9wLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RyaS1kZXZl bA== From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 18 Jul 2019 13:44:29 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0564206144==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 833906E3CE for ; Thu, 18 Jul 2019 13:44:29 +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 --===============0564206144== Content-Type: multipart/alternative; boundary="15634574692.6C69acAD.29545" Content-Transfer-Encoding: 7bit --15634574692.6C69acAD.29545 Date: Thu, 18 Jul 2019 13:44:29 +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=3D109955 --- Comment #56 from Sylvain BERTRAND --- Playing dota2 vulkan or GL? I guess it's vulkan: and there I don't know how vulkan deal with multiple W= SIs, and how dota2 selects the one it will use. The idea is to clearly identify the code paths which would be "buggy". (my custom distro is x11 native) That said, I don't know the status of wayland: did they reach the same "clu= ster f*ck" level that x11 is at? (irony, since wayland reason to exist is to be orders of magnitude less kludgy than x11) --=20 You are receiving this mail because: You are the assignee for the bug.= --15634574692.6C69acAD.29545 Date: Thu, 18 Jul 2019 13:44:29 +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

Comme= nt # 56 on bug 10995= 5 from Sylvain BERTRAND 
Playing dota2 vulkan or GL?

I guess it's vulkan: and there I don't know how vulkan deal with multiple W=
SIs,
and how dota2 selects the one it will use.

The idea is to clearly identify the code paths which would be "buggy&q=
uot;.

(my custom distro is x11 native)

That said, I don't know the status of wayland: did they reach the same &quo=
t;cluster
f*ck" level that x11 is at? (irony, since wayland reason to exist is t=
o be
orders of magnitude less kludgy than x11)

You are receiving this mail because:
  • You are the assignee for the bug.
= --15634574692.6C69acAD.29545-- --===============0564206144== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0564206144==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Fri, 19 Jul 2019 00:12:59 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2113071943==" 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 7F2F66E489 for ; Fri, 19 Jul 2019 00:12:59 +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 --===============2113071943== Content-Type: multipart/alternative; boundary="15634951795.cCB0a21bf.7666" Content-Transfer-Encoding: 7bit --15634951795.cCB0a21bf.7666 Date: Fri, 19 Jul 2019 00:12:59 +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=3D109955 --- Comment #57 from Hadet --- Created attachment 144821 --> https://bugs.freedesktop.org/attachment.cgi?id=3D144821&action=3Dedit Dmesg after crash I spoke too soon it's happening on Wayland now too just a lot less frequent= ly --=20 You are receiving this mail because: You are the assignee for the bug.= --15634951795.cCB0a21bf.7666 Date: Fri, 19 Jul 2019 00:12:59 +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

Comme= nt # 57 on bug 10995= 5 from = Hadet 
Created attachment 144821 =
[details]
Dmesg after crash

I spoke too soon it's happening on Wayland now too just a lot less frequent=
ly

You are receiving this mail because:
  • You are the assignee for the bug.
= --15634951795.cCB0a21bf.7666-- --===============2113071943== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============2113071943==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 22 Jul 2019 05:19:29 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0161489225==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 427C1898F1 for ; Mon, 22 Jul 2019 05:19:29 +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 --===============0161489225== Content-Type: multipart/alternative; boundary="15637727692.ce7aC19.15526" Content-Transfer-Encoding: 7bit --15637727692.ce7aC19.15526 Date: Mon, 22 Jul 2019 05:19:29 +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=3D109955 --- Comment #58 from Mauro Gaspari --- After a long time without crashes on Tumbleweed, I wanted to prepare a test setup for valve mesa built with ACO. So I installed Ubuntu Budgie 18.04 LTS with hardware enablement stack and I noticed the OS freezes are now back, e= ven on the RadeonVII.=20 What I noticed in the game behavior is this. This is a game running on crossover (wine) with DX11 and DXVK. I want to point out that I do alt-tab = out of games to do other things, so this might be a factor to consider. But aga= in, I do the same on my NVIDIA-GPU laptop and I never had a single freeze or fps drop. Not sure if point 2 and 3 are related, I just wanted to share my observatio= ns. 1. Game starts with excellent FPS. I can hear GPU fans spinning. 2. After a while, game loses a lot of FPS starts to become slow and sluggis= h, GPU seems to be no longer doing much and I can no longer hear the fans spinning. 3. After a while longer, the whole OS freezes as described in my first post. What I am going to do next: 1. Use the workaround of comment #47 and test for a few days. 2. Install Valve mesa-aco with ubuntu PPA and test (without workarounds) fo= r a few days. I will report back when I have more details on my tests. System info: OS: Ubuntu 18.04.2 LTS x86_64=20 Kernel: 5.0.0-21-generic Resolution: 3440x1440 CPU: AMD Ryzen 7 2700X (16) @ 3.700G=20 GPU: AMD Vega 20=20 Memory: 2650MiB / 64398MiB OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.0.2 --=20 You are receiving this mail because: You are the assignee for the bug.= --15637727692.ce7aC19.15526 Date: Mon, 22 Jul 2019 05:19:29 +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

Comme= nt # 58 on bug 10995= 5 from = Mauro Gaspari 
After a long time without crashes on Tumbleweed, I wanted to p=
repare a test
setup for valve mesa built with ACO. So I installed Ubuntu Budgie 18.04 LTS
with hardware enablement stack and I noticed the OS freezes are now back, e=
ven
on the RadeonVII.=20

What I noticed in the game behavior is this. This is a game running on
crossover (wine) with DX11 and DXVK. I want to point out that I do alt-tab =
out
of games to do other things, so this might be a factor to consider. But aga=
in,
I do the same on my NVIDIA-GPU laptop and I never had a single freeze or fps
drop.
Not sure if point 2 and 3 are related, I just wanted to share my observatio=
ns.

1. Game starts with excellent FPS. I can hear GPU fans spinning.
2. After a while, game loses a lot of FPS starts to become slow and sluggis=
h,
GPU seems to be no longer doing much and I can no longer hear the fans
spinning.
3. After a while longer, the whole OS freezes as described in my first post.


What I am going to do next:
1. Use the workaround of comment #=
47 and test for a few days.
2. Install Valve mesa-aco with ubuntu PPA and test (without workarounds) fo=
r a
few days.

I will report back when I have more details on my tests.

System info:
OS: Ubuntu 18.04.2 LTS x86_64=20
Kernel: 5.0.0-21-generic
Resolution: 3440x1440
CPU: AMD Ryzen 7 2700X (16) @ 3.700G=20
GPU: AMD Vega 20=20
Memory: 2650MiB / 64398MiB
OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.0.2

You are receiving this mail because:
  • You are the assignee for the bug.
= --15637727692.ce7aC19.15526-- --===============0161489225== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0161489225==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 23 Jul 2019 16:25:04 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1321679196==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id DFBD16E30E for ; Tue, 23 Jul 2019 16:25:04 +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 --===============1321679196== Content-Type: multipart/alternative; boundary="15638991047.dE9c.17712" Content-Transfer-Encoding: 7bit --15638991047.dE9c.17712 Date: Tue, 23 Jul 2019 16:25:04 +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=3D109955 --- Comment #59 from wedens13@yandex.ru --- I have similar issues with Sapphire Pulse Vega 56. Arch Linux Kernel versions: 4.19.60-1-lts, 5.2.1-1 mesa: 19.1.3-1, mesa with ACO (f9b38efdda166f2b79562525e72fe135c6b23d54) llvm: 8.0.0 I've also tried booting with integrated video and using DRI_PRIME=3D1 to of= fload to vega. It crashes similarly (after 5min of playing witcher 3 with dxvk 1.3.1): Jul 23 22:44:01 wedens-pc kernel: amdgpu 0000:03:00.0: [mmhub] VMC page fau= lt (src_id:0 ring:154 vmid:1 pasid:32771, for process pid 0 thread pid 0 ) Jul 23 22:44:01 wedens-pc kernel: amdgpu 0000:03:00.0: at address 0x0000800100a00000 from 18 Jul 23 22:44:01 wedens-pc kernel: amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00100134 Jul 23 22:44:11 wedens-pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=3D230, emitted seq=3D233 Jul 23 22:44:11 wedens-pc kernel: [drm] GPU recovery disabled. I'm going to try mesa master and manual power level workaround (when should= I use "reset to normal" command?). --=20 You are receiving this mail because: You are the assignee for the bug.= --15638991047.dE9c.17712 Date: Tue, 23 Jul 2019 16:25:04 +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

Comme= nt # 59 on bug 10995= 5 from wedens13@yande= x.ru 
I have similar issues with Sapphire Pulse Vega 56.
Arch Linux
Kernel versions: 4.19.60-1-lts, 5.2.1-1
mesa: 19.1.3-1, mesa with ACO (f9b38efdda166f2b79562525e72fe135c6b23d54)
llvm: 8.0.0

I've also tried booting with integrated video and using DRI_PRIME=3D1 to of=
fload
to vega. It crashes similarly (after 5min of playing witcher 3 with dxvk
1.3.1):

Jul 23 22:44:01 wedens-pc kernel: amdgpu 0000:03:00.0: [mmhub] VMC page fau=
lt
(src_id:0 ring:154 vmid:1 pasid:32771, for process  pid 0 thread  pid 0
                                  )
Jul 23 22:44:01 wedens-pc kernel: amdgpu 0000:03:00.0:   at address
0x0000800100a00000 from 18
Jul 23 22:44:01 wedens-pc kernel: amdgpu 0000:03:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x00100134
Jul 23 22:44:11 wedens-pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
ring sdma1 timeout, signaled seq=3D230, emitted seq=3D233
Jul 23 22:44:11 wedens-pc kernel: [drm] GPU recovery disabled.


I'm going to try mesa master and manual power level workaround (when should=
 I
use "reset to normal" command?).

You are receiving this mail because:
  • You are the assignee for the bug.
= --15638991047.dE9c.17712-- --===============1321679196== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1321679196==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 23 Jul 2019 16:30:05 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1393024627==" 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 052D96E2F5 for ; Tue, 23 Jul 2019 16:30:05 +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 --===============1393024627== Content-Type: multipart/alternative; boundary="15638994040.aD57bC.19380" Content-Transfer-Encoding: 7bit --15638994040.aD57bC.19380 Date: Tue, 23 Jul 2019 16:30:04 +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=3D109955 --- Comment #60 from wedens13@yandex.ru --- A couple of relevant log fragments with crashes: https://paste.ee/p/rtDEg --=20 You are receiving this mail because: You are the assignee for the bug.= --15638994040.aD57bC.19380 Date: Tue, 23 Jul 2019 16:30:04 +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

Comme= nt # 60 on bug 10995= 5 from wedens13@yande= x.ru 
A couple of relevant log fragments with crashes: https://paste.ee/p/rtDEg

You are receiving this mail because:
  • You are the assignee for the bug.
= --15638994040.aD57bC.19380-- --===============1393024627== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1393024627==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 23 Jul 2019 17:14:25 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0067157832==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 11EF089850 for ; Tue, 23 Jul 2019 17:14:25 +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 --===============0067157832== Content-Type: multipart/alternative; boundary="15639020650.B169D2EbA.25400" Content-Transfer-Encoding: 7bit --15639020650.B169D2EbA.25400 Date: Tue, 23 Jul 2019 17:14:24 +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=3D109955 --- Comment #61 from wedens13@yandex.ru --- I've tried starting witcher 3 after executing echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_level echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk and it still crashes immediately. log: https://paste.ee/p/thvXf --=20 You are receiving this mail because: You are the assignee for the bug.= --15639020650.B169D2EbA.25400 Date: Tue, 23 Jul 2019 17:14:25 +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

Comme= nt # 61 on bug 10995= 5 from wedens13@yande= x.ru 
I've tried starting witcher 3 after executing
echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_le=
vel
echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk

and it still crashes immediately.

log: https://paste.ee/p/thvXf

You are receiving this mail because:
  • You are the assignee for the bug.
= --15639020650.B169D2EbA.25400-- --===============0067157832== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0067157832==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: sylvain.bertrand@gmail.com Subject: Re: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 23 Jul 2019 20:17:42 +0000 Message-ID: <20190723201742.GA26033@freedom> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Received: from mail-wr1-x441.google.com (mail-wr1-x441.google.com [IPv6:2a00:1450:4864:20::441]) by gabe.freedesktop.org (Postfix) with ESMTPS id AC6CD6E3B2 for ; Tue, 23 Jul 2019 20:18:09 +0000 (UTC) Received: by mail-wr1-x441.google.com with SMTP id f9so44453476wre.12 for ; Tue, 23 Jul 2019 13:18:09 -0700 (PDT) Content-Disposition: inline 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: bugzilla-daemon@freedesktop.org Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org dW5zdGFibGUgcG93ZXIgc3VwcGx5IGxpbmVzIHRvIHRoZSBncHUgaWYgb3ZlcmhlYXRpbmcgaXMg ZXhjbHVkZWQ/Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f CmRyaS1kZXZlbCBtYWlsaW5nIGxpc3QKZHJpLWRldmVsQGxpc3RzLmZyZWVkZXNrdG9wLm9yZwpo dHRwczovL2xpc3RzLmZyZWVkZXNrdG9wLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RyaS1kZXZlbA== From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 23 Jul 2019 20:18:12 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2067617108==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 80C816E3CB for ; Tue, 23 Jul 2019 20:18:12 +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 --===============2067617108== Content-Type: multipart/alternative; boundary="15639130925.9BF9aE9.22733" Content-Transfer-Encoding: 7bit --15639130925.9BF9aE9.22733 Date: Tue, 23 Jul 2019 20:18:12 +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=3D109955 --- Comment #62 from Sylvain BERTRAND --- unstable power supply lines to the gpu if overheating is excluded? --=20 You are receiving this mail because: You are the assignee for the bug.= --15639130925.9BF9aE9.22733 Date: Tue, 23 Jul 2019 20:18:12 +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

Comme= nt # 62 on bug 10995= 5 from Sylvain BERTRAND 
unstable power supply lines to the gpu if overheating is exclu=
ded?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15639130925.9BF9aE9.22733-- --===============2067617108== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============2067617108==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 24 Jul 2019 04:14:21 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1233347344==" 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 D4FA2890AD for ; Wed, 24 Jul 2019 04:14:21 +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 --===============1233347344== Content-Type: multipart/alternative; boundary="15639416616.3fFd9.26948" Content-Transfer-Encoding: 7bit --15639416616.3fFd9.26948 Date: Wed, 24 Jul 2019 04:14:21 +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=3D109955 --- Comment #63 from Mauro Gaspari --- (In reply to Sylvain BERTRAND from comment #62) > unstable power supply lines to the gpu if overheating is excluded? I cannot speak for others. In my case,U would say no. I installed windows10= in a separate ssd, just to check there was no hardware issue of any kind.=20 On windows10 with latest amd drivers, I have no freezes or any other issue running same games. --=20 You are receiving this mail because: You are the assignee for the bug.= --15639416616.3fFd9.26948 Date: Wed, 24 Jul 2019 04:14:21 +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

Comme= nt # 63 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Sylvain BERTRAND from comment #62)
> unstable power supply lines to the gpu if overhe=
ating is excluded?

I cannot speak for others. In my case,U would say no. I installed windows10=
 in
a separate ssd, just to check there was no hardware issue of any kind.=20
On windows10 with latest amd drivers, I have no freezes or any other issue
running same games.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15639416616.3fFd9.26948-- --===============1233347344== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1233347344==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: sylvain.bertrand@gmail.com Subject: Re: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 24 Jul 2019 13:08:54 +0000 Message-ID: <20190724130854.GA555@freedom> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) by gabe.freedesktop.org (Postfix) with ESMTPS id 7DC3588E46 for ; Wed, 24 Jul 2019 13:09:21 +0000 (UTC) Received: by mail-wr1-x42e.google.com with SMTP id y4so46950328wrm.2 for ; Wed, 24 Jul 2019 06:09:21 -0700 (PDT) Content-Disposition: inline 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: bugzilla-daemon@freedesktop.org Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org PiBJIGNhbm5vdCBzcGVhayBmb3Igb3RoZXJzLiBJbiBteSBjYXNlLFUgd291bGQgc2F5IG5vLiBJ IGluc3RhbGxlZCB3aW5kb3dzMTAgaW4KPiBhIHNlcGFyYXRlIHNzZCwganVzdCB0byBjaGVjayB0 aGVyZSB3YXMgbm8gaGFyZHdhcmUgaXNzdWUgb2YgYW55IGtpbmQuIAo+IE9uIHdpbmRvd3MxMCB3 aXRoIGxhdGVzdCBhbWQgZHJpdmVycywgSSBoYXZlIG5vIGZyZWV6ZXMgb3IgYW55IG90aGVyIGlz c3VlCj4gcnVubmluZyBzYW1lIGdhbWVzLgoKTmF0aXZlIGdudS9saW51eCBnYW1lIG9yIGdvaW5n IHRocm91Z2ggd2luZS9keHZrPwpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fXwpkcmktZGV2ZWwgbWFpbGluZyBsaXN0CmRyaS1kZXZlbEBsaXN0cy5mcmVlZGVz a3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9k cmktZGV2ZWw= From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 24 Jul 2019 13:09:23 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0821271878==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id A42EE8932D for ; Wed, 24 Jul 2019 13:09:23 +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 --===============0821271878== Content-Type: multipart/alternative; boundary="15639737631.ecF80c2.8410" Content-Transfer-Encoding: 7bit --15639737631.ecF80c2.8410 Date: Wed, 24 Jul 2019 13:09:23 +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=3D109955 --- Comment #64 from Sylvain BERTRAND --- > I cannot speak for others. In my case,U would say no. I installed windows= 10 in > a separate ssd, just to check there was no hardware issue of any kind.=20 > On windows10 with latest amd drivers, I have no freezes or any other issue > running same games. Native gnu/linux game or going through wine/dxvk? --=20 You are receiving this mail because: You are the assignee for the bug.= --15639737631.ecF80c2.8410 Date: Wed, 24 Jul 2019 13:09:23 +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

Comme= nt # 64 on bug 10995= 5 from Sylvain BERTRAND 
> I cannot speak for others. In my ca=
se,U would say no. I installed windows10 in
> a separate ssd, just to check there was no hardware issue of any kind.=
=20
> On windows10 with latest amd drivers, I have no freezes or any other i=
ssue
> running same games.

Native gnu/linux game or going through wine/dxvk?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15639737631.ecF80c2.8410-- --===============0821271878== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0821271878==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 24 Jul 2019 14:27:33 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1549433865==" 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 53C936E5B3 for ; Wed, 24 Jul 2019 14:27:33 +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 --===============1549433865== Content-Type: multipart/alternative; boundary="15639784530.FD0ee95.22500" Content-Transfer-Encoding: 7bit --15639784530.FD0ee95.22500 Date: Wed, 24 Jul 2019 14:27:33 +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=3D109955 --- Comment #65 from wedens13@yandex.ru --- (In reply to Sylvain BERTRAND from comment #62) > unstable power supply lines to the gpu if overheating is excluded? It's not overheating in my case, but my PSU is pretty old (I'm waiting for components for my new build to arrive, including new PSU). I've lowered pow= er limit (to 80W) and I haven't had any crashes yet.=20 So, in my case the problem *might be* related to PSU. But I can't exclude (= nor confirm) possibility of driver problems with higher power states (until I h= ave a better PSU). I'll report back if I have any crashes with new PSU or lowered PL. --=20 You are receiving this mail because: You are the assignee for the bug.= --15639784530.FD0ee95.22500 Date: Wed, 24 Jul 2019 14:27:33 +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

Comme= nt # 65 on bug 10995= 5 from wedens13@yande= x.ru 
(In reply to Sylvain BERTRAND from comment #62)
> unstable power supply lines to the gpu if overhe=
ating is excluded?

It's not overheating in my case, but my PSU is pretty old (I'm waiting for
components for my new build to arrive, including new PSU). I've lowered pow=
er
limit (to 80W) and I haven't had any crashes yet.=20

So, in my case the problem *might be* related to PSU. But I can't exclude (=
nor
confirm) possibility of driver problems with higher power states (until I h=
ave
a better PSU).

I'll report back if I have any crashes with new PSU or lowered PL.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15639784530.FD0ee95.22500-- --===============1549433865== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1549433865==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 24 Jul 2019 14:41:33 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0030705746==" 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 382956E5BA for ; Wed, 24 Jul 2019 14:41:33 +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 --===============0030705746== Content-Type: multipart/alternative; boundary="15639792932.0211.24909" Content-Transfer-Encoding: 7bit --15639792932.0211.24909 Date: Wed, 24 Jul 2019 14:41:33 +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=3D109955 --- Comment #66 from Hadet --- I don't think it's faulty hardware in any of our cases to be perfectly hone= st, it's a bad instruction set, this didn't happen with older kernels or firmwa= re and the issue now is there are so few of us with Vega cards that we're real= ly on our own trying to troubleshoot this situatio. Since switching to wayland my crashing has been a lot less frequent, it'd s= ay once every couple days as opposed to once every few hours when gaming with Vulkan/DXVK --=20 You are receiving this mail because: You are the assignee for the bug.= --15639792932.0211.24909 Date: Wed, 24 Jul 2019 14:41:33 +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

Comme= nt # 66 on bug 10995= 5 from = Hadet 
I don't think it's faulty hardware in any of our cases to be p=
erfectly honest,
it's a bad instruction set, this didn't happen with older kernels or firmwa=
re
and the issue now is there are so few of us with Vega cards that we're real=
ly
on our own trying to troubleshoot this situatio.

Since switching to wayland my crashing has been a lot less frequent, it'd s=
ay
once every couple days as opposed to once every few hours when gaming with
Vulkan/DXVK

You are receiving this mail because:
  • You are the assignee for the bug.
= --15639792932.0211.24909-- --===============0030705746== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0030705746==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: sylvain.bertrand@gmail.com Subject: Re: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 24 Jul 2019 14:55:53 +0000 Message-ID: <20190724145553.GA786@freedom> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) by gabe.freedesktop.org (Postfix) with ESMTPS id 6AC4D6E5C2 for ; Wed, 24 Jul 2019 14:56:20 +0000 (UTC) Received: by mail-wm1-x32d.google.com with SMTP id v15so42153132wml.0 for ; Wed, 24 Jul 2019 07:56:20 -0700 (PDT) Content-Disposition: inline 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: bugzilla-daemon@freedesktop.org Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org PiAuLi4KPiBWdWxrYW4vRFhWSwoKVGhlIGJ1Z3MgbWF5IGJlIGluIHdpbmUvRFhWSyB0aGVuLiBZ b3Ugc2hvdWxkIHJlcG9ydCB0byBhIGJ1ZyB0byB0aGVtIGFuZCBsaW5rCnRoaXMgYnVnIHRvIHRo ZWlycy4KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJp LWRldmVsIG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBz Oi8vbGlzdHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 24 Jul 2019 14:56:22 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2053244918==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 9B3D96E5C4 for ; Wed, 24 Jul 2019 14:56:22 +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 --===============2053244918== Content-Type: multipart/alternative; boundary="15639801824.AaCF2.28449" Content-Transfer-Encoding: 7bit --15639801824.AaCF2.28449 Date: Wed, 24 Jul 2019 14:56:22 +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=3D109955 --- Comment #67 from Sylvain BERTRAND --- > ... > Vulkan/DXVK The bugs may be in wine/DXVK then. You should report to a bug to them and l= ink this bug to theirs. --=20 You are receiving this mail because: You are the assignee for the bug.= --15639801824.AaCF2.28449 Date: Wed, 24 Jul 2019 14:56:22 +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

Comme= nt # 67 on bug 10995= 5 from Sylvain BERTRAND 
> ...
> Vulkan/DXVK

The bugs may be in wine/DXVK then. You should report to a bug to them and l=
ink
this bug to theirs.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15639801824.AaCF2.28449-- --===============2053244918== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============2053244918==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 27 Jul 2019 11:28:28 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2044222279==" 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 6C9826EEA1 for ; Sat, 27 Jul 2019 11:28:28 +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 --===============2044222279== Content-Type: multipart/alternative; boundary="15642269082.b1daE7c77.14166" Content-Transfer-Encoding: 7bit --15642269082.b1daE7c77.14166 Date: Sat, 27 Jul 2019 11:28:28 +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=3D109955 --- Comment #68 from Mauro Gaspari --- (In reply to Sylvain BERTRAND from comment #67) > > ... > > Vulkan/DXVK >=20 > The bugs may be in wine/DXVK then. You should report to a bug to them and > link > this bug to theirs. If any of you opened bugs on other bug trackers, please post a link here so= we can all contribute to both. I did some test on my end and I can report the following: System info: OS: Ubuntu 18.04.2 LTS x86_64=20 Kernel: 5.0.0-21-generic Resolution: 3440x1440 CPU: AMD Ryzen 7 2700X (16) @ 3.700G=20 GPU: AMD Vega 20=20 Memory: 2650MiB / 64398MiB OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.0.2 1. Power profile set to manual did not help 2. Mesa-ACO from valve seem to have helped quite a bit. So far, no system freezes I installed Arch on another SSD and will try to reproduce the same tests: 1. Plain Arch - crash or not ? 2. Arch with forced power profile - crash or not ? 3- Arch with mesa-ACO - crash or not ? --=20 You are receiving this mail because: You are the assignee for the bug.= --15642269082.b1daE7c77.14166 Date: Sat, 27 Jul 2019 11:28:28 +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

Comme= nt # 68 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Sylvain BERTRAND from comment #67)
> > ...
> > Vulkan/DXVK
>=20
> The bugs may be in wine/DXVK then. You should report to a bug to them =
and
> link
> this bug to theirs.

If any of you opened bugs on other bug trackers, please post a link here so=
 we
can all contribute to both.

I did some test on my end and I can report the following:

System info:
OS: Ubuntu 18.04.2 LTS x86_64=20
Kernel: 5.0.0-21-generic
Resolution: 3440x1440
CPU: AMD Ryzen 7 2700X (16) @ 3.700G=20
GPU: AMD Vega 20=20
Memory: 2650MiB / 64398MiB
OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.0.2

1. Power profile set to manual did not help
2. Mesa-ACO from valve seem to have helped quite a bit. So far, no system
freezes

I installed Arch on another SSD and will try to reproduce the same tests:
1. Plain Arch - crash or not ?
2. Arch with forced power profile - crash or not ?
3- Arch with mesa-ACO - crash or not ?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15642269082.b1daE7c77.14166-- --===============2044222279== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============2044222279==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: sylvain.bertrand@gmail.com Subject: Re: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 27 Jul 2019 13:19:22 +0000 Message-ID: <20190727131922.GA370@freedom> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) by gabe.freedesktop.org (Postfix) with ESMTPS id 890536EEB1 for ; Sat, 27 Jul 2019 13:19:56 +0000 (UTC) Received: by mail-wm1-x330.google.com with SMTP id s15so28437849wmj.3 for ; Sat, 27 Jul 2019 06:19:56 -0700 (PDT) Content-Disposition: inline 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: bugzilla-daemon@freedesktop.org Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org RG9uJ3QgZm9yZ2V0IHRvIHByb3ZpZGUgdGhlIHNvZnR3YXJlIHN0YWNrIHVzZWQ6Cgp3aGljaCBz b2Z3YXJlIChnYW1lLCBjYWQuLi4pPyB3aW5lL2R4dms/IG5hdGl2ZT8KX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVsIG1haWxpbmcgbGlzdApk cmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlzdHMuZnJlZWRlc2t0b3Au b3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 27 Jul 2019 13:19:59 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1112618430==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 38D9E6EEBA for ; Sat, 27 Jul 2019 13:19:59 +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 --===============1112618430== Content-Type: multipart/alternative; boundary="15642335994.9Aff.388" Content-Transfer-Encoding: 7bit --15642335994.9Aff.388 Date: Sat, 27 Jul 2019 13:19:59 +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=3D109955 --- Comment #69 from Sylvain BERTRAND --- Don't forget to provide the software stack used: which sofware (game, cad...)? wine/dxvk? native? --=20 You are receiving this mail because: You are the assignee for the bug.= --15642335994.9Aff.388 Date: Sat, 27 Jul 2019 13:19:59 +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

Comme= nt # 69 on bug 10995= 5 from Sylvain BERTRAND 
Don't forget to provide the software stack used:

which sofware (game, cad...)? wine/dxvk? native?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15642335994.9Aff.388-- --===============1112618430== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1112618430==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 27 Jul 2019 17:32:53 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1901229575==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id C615D6EECC for ; Sat, 27 Jul 2019 17:32:53 +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 --===============1901229575== Content-Type: multipart/alternative; boundary="15642487733.DB069eE.15323" Content-Transfer-Encoding: 7bit --15642487733.DB069eE.15323 Date: Sat, 27 Jul 2019 17:32:53 +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=3D109955 --- Comment #70 from Mauro Gaspari --- (In reply to Sylvain BERTRAND from comment #69) > Don't forget to provide the software stack used: >=20 > which sofware (game, cad...)? wine/dxvk? native? Good point. Games being tested: Pillars of Eternity - Native Battletech - Native Eve Online - Wine+DXVK --=20 You are receiving this mail because: You are the assignee for the bug.= --15642487733.DB069eE.15323 Date: Sat, 27 Jul 2019 17:32:53 +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

Comme= nt # 70 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Sylvain BERTRAND from comment #69)
> Don't forget to provide the software stack used:
>=20
> which sofware (game, cad...)? wine/dxvk? native?

Good point. Games being tested:

Pillars of Eternity - Native
Battletech - Native
Eve Online - Wine+DXVK

You are receiving this mail because:
  • You are the assignee for the bug.
= --15642487733.DB069eE.15323-- --===============1901229575== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1901229575==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 28 Jul 2019 03:14:23 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1497014807==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 653DC89191 for ; Sun, 28 Jul 2019 03:14:23 +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 --===============1497014807== Content-Type: multipart/alternative; boundary="15642836634.aA07e21.6705" Content-Transfer-Encoding: 7bit --15642836634.aA07e21.6705 Date: Sun, 28 Jul 2019 03:14:23 +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=3D109955 --- Comment #71 from Yury Zhuravlev --- Can somebody try games without any fps limits? Like vblank_mode=3D0 and in-game limits. --=20 You are receiving this mail because: You are the assignee for the bug.= --15642836634.aA07e21.6705 Date: Sun, 28 Jul 2019 03:14:23 +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

Comme= nt # 71 on bug 10995= 5 from Yury Zhuravlev 
Can somebody try games without any fps limits?
Like vblank_mode=3D0 and in-game limits.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15642836634.aA07e21.6705-- --===============1497014807== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1497014807==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 03 Aug 2019 13:35:55 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0210398302==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 55A3F6E512 for ; Sat, 3 Aug 2019 13:35:55 +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 --===============0210398302== Content-Type: multipart/alternative; boundary="15648393552.c39C0F3Ed.28674" Content-Transfer-Encoding: 7bit --15648393552.c39C0F3Ed.28674 Date: Sat, 3 Aug 2019 13:35:55 +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=3D109955 --- Comment #72 from Mauro Gaspari --- After a few weeks without crashes on Ubuntu Budgie 18.04 LTS with valve mesa-aco, I moved to another distribution that does not have valve mesa-aco= to cross check. This is what I am using: OS: openSUSE Tumbleweed x86_64=20 Kernel: 5.2.2-1-default Resolution: 3440x1440 DE: Xfce WM: Xfwm4 CPU: AMD Ryzen 7 2700X (16) @ 3.700GHz GPU: AMD ATI Radeon VII Memory: 1644MiB / 64387MiB=20 OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.3 No kernel parameters configured, just out of the box openSUSE I had 3 of full OS freezes: 1. As I was playing Albion Online (Native) No full system freeze, I was abl= e to drop to tty, and notice this error: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! 2. As I closed down Albion Online (Native) and returned to desktop. Full Sy= stem Freeze 3. As I was doing regular desktop operations on XFCE. No 3d gaming going on. Please see below logs: DMESG after crash: ilvipero@MGDT-ROG:~> dmesg | grep amdgpu [ 5.758450] [drm] amdgpu kernel modesetting enabled. [ 5.758569] amdgpu 0000:0a:00.0: remove_conflicting_pci_framebuffers: ba= r 0: 0xe0000000 -> 0xefffffff [ 5.758570] amdgpu 0000:0a:00.0: remove_conflicting_pci_framebuffers: ba= r 2: 0xf0000000 -> 0xf01fffff [ 5.758571] amdgpu 0000:0a:00.0: remove_conflicting_pci_framebuffers: ba= r 5: 0xfcd00000 -> 0xfcd7ffff [ 5.758573] fb0: switching to amdgpudrmfb from EFI VGA [ 5.758646] amdgpu 0000:0a:00.0: vgaarb: deactivate vga console [ 5.758826] amdgpu 0000:0a:00.0: No more image in the PCI ROM [ 5.758870] amdgpu 0000:0a:00.0: VRAM: 16368M 0x0000008000000000 - 0x00000083FEFFFFFF (16368M used) [ 5.758871] amdgpu 0000:0a:00.0: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF [ 5.758872] amdgpu 0000:0a:00.0: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF [ 5.758936] [drm] amdgpu: 16368M of VRAM memory ready [ 5.758938] [drm] amdgpu: 16368M of GTT memory ready. [ 5.759204] amdgpu 0000:0a:00.0: Direct firmware load for amdgpu/vega20_ta.bin failed with error -2 [ 5.759205] amdgpu 0000:0a:00.0: psp v11.0: Failed to load firmware "amdgpu/vega20_ta.bin" [ 6.855053] fbcon: amdgpudrmfb (fb0) is primary device [ 6.913835] amdgpu 0000:0a:00.0: fb0: amdgpudrmfb frame buffer device [ 6.928054] amdgpu 0000:0a:00.0: ring gfx uses VM inv eng 0 on hub 0 [ 6.928055] amdgpu 0000:0a:00.0: ring comp_1.0.0 uses VM inv eng 1 on hu= b 0 [ 6.928056] amdgpu 0000:0a:00.0: ring comp_1.1.0 uses VM inv eng 4 on hu= b 0 [ 6.928056] amdgpu 0000:0a:00.0: ring comp_1.2.0 uses VM inv eng 5 on hu= b 0 [ 6.928057] amdgpu 0000:0a:00.0: ring comp_1.3.0 uses VM inv eng 6 on hu= b 0 [ 6.928058] amdgpu 0000:0a:00.0: ring comp_1.0.1 uses VM inv eng 7 on hu= b 0 [ 6.928059] amdgpu 0000:0a:00.0: ring comp_1.1.1 uses VM inv eng 8 on hu= b 0 [ 6.928059] amdgpu 0000:0a:00.0: ring comp_1.2.1 uses VM inv eng 9 on hu= b 0 [ 6.928060] amdgpu 0000:0a:00.0: ring comp_1.3.1 uses VM inv eng 10 on h= ub 0 [ 6.928060] amdgpu 0000:0a:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hu= b 0 [ 6.928061] amdgpu 0000:0a:00.0: ring sdma0 uses VM inv eng 0 on hub 1 [ 6.928062] amdgpu 0000:0a:00.0: ring page0 uses VM inv eng 1 on hub 1 [ 6.928063] amdgpu 0000:0a:00.0: ring sdma1 uses VM inv eng 4 on hub 1 [ 6.928063] amdgpu 0000:0a:00.0: ring page1 uses VM inv eng 5 on hub 1 [ 6.928064] amdgpu 0000:0a:00.0: ring uvd_0 uses VM inv eng 6 on hub 1 [ 6.928064] amdgpu 0000:0a:00.0: ring uvd_enc_0.0 uses VM inv eng 7 on h= ub 1 [ 6.928065] amdgpu 0000:0a:00.0: ring uvd_enc_0.1 uses VM inv eng 8 on h= ub 1 [ 6.928066] amdgpu 0000:0a:00.0: ring uvd_1 uses VM inv eng 9 on hub 1 [ 6.928066] amdgpu 0000:0a:00.0: ring uvd_enc_1.0 uses VM inv eng 10 on = hub 1 [ 6.928067] amdgpu 0000:0a:00.0: ring uvd_enc_1.1 uses VM inv eng 11 on = hub 1 [ 6.928067] amdgpu 0000:0a:00.0: ring vce0 uses VM inv eng 12 on hub 1 [ 6.928068] amdgpu 0000:0a:00.0: ring vce1 uses VM inv eng 13 on hub 1 [ 6.928068] amdgpu 0000:0a:00.0: ring vce2 uses VM inv eng 14 on hub 1 [ 7.609167] [drm] Initialized amdgpu 3.32.0 20150101 for 0000:0a:00.0 on minor 0 system logs: 2019-08-03T18:51:21.779695+08:00 MGDT-ROG kernel: [11817.727681] pcieport 0000:00:03.1: AER: Multiple Corrected error received: 0000:00:00.0 2019-08-03T18:51:21.779730+08:00 MGDT-ROG kernel: [11817.771355] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=3DCorrected, type=3DData Link L= ayer, (Transmitter ID) 2019-08-03T18:51:21.779735+08:00 MGDT-ROG kernel: [11817.771358] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=3D00003100/000060= 00 2019-08-03T18:51:21.779737+08:00 MGDT-ROG kernel: [11817.771361] pcieport 0000:00:03.1: AER: [ 8] Rollover=20=20=20=20=20=20=20=20=20=20=20=20=20= =20 2019-08-03T18:51:21.779738+08:00 MGDT-ROG kernel: [11817.771371] pcieport 0000:00:03.1: AER: [12] Timeout=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20 2019-08-03T18:51:26.721833+08:00 MGDT-ROG sudo: pam_unix(sudo:session): ses= sion closed for user root 2019-08-03T18:51:31.983837+08:00 MGDT-ROG kernel: [11827.971739] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=3D2324984, emitted seq=3D2324986 2019-08-03T18:51:31.983851+08:00 MGDT-ROG kernel: [11827.971800] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process X p= id 2132 thread X:cs0 pid 2139 2019-08-03T18:51:31.983853+08:00 MGDT-ROG kernel: [11827.971804] amdgpu 0000:0a:00.0: GPU reset begin! 2019-08-03T18:51:32.751834+08:00 MGDT-ROG kernel: [11828.741066] amdgpu: [powerplay] Failed to send message 0x47, response 0xffffffff 2019-08-03T18:51:32.751846+08:00 MGDT-ROG kernel: [11828.741077] amdgpu: [powerplay] Failed to send message 0x28, response 0xffffffff 2019-08-03T18:51:32.751849+08:00 MGDT-ROG kernel: [11828.741078] amdgpu: [powerplay] [SetUclkToHightestDpmLevel] Set hard min uclk failed! 2019-08-03T18:51:32.751850+08:00 MGDT-ROG kernel: [11828.741090] amdgpu: [powerplay] Failed to send message 0x28, response 0xffffffff 2019-08-03T18:51:32.751852+08:00 MGDT-ROG kernel: [11828.741091] amdgpu: [powerplay] Attempt to set Hard Min for DCEFCLK Failed! 2019-08-03T18:51:32.751854+08:00 MGDT-ROG kernel: [11828.741102] amdgpu: [powerplay] Failed to send message 0x28, response 0xffffffff 2019-08-03T18:51:32.751855+08:00 MGDT-ROG kernel: [11828.741102] amdgpu: [powerplay] [SetHardMinFreq] Set hard min uclk failed! 2019-08-03T18:51:32.751856+08:00 MGDT-ROG kernel: [11828.741113] amdgpu: [powerplay] Failed to send message 0x26, response 0xffffffff 2019-08-03T18:51:32.751858+08:00 MGDT-ROG kernel: [11828.741114] amdgpu: [powerplay] Failed to set soft min gfxclk ! 2019-08-03T18:51:32.751859+08:00 MGDT-ROG kernel: [11828.741114] amdgpu: [powerplay] Failed to upload DPM Bootup Levels! 2019-08-03T18:51:32.787843+08:00 MGDT-ROG kernel: [11828.775671] [drm] REG_= WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:951 2019-08-03T18:51:32.787852+08:00 MGDT-ROG kernel: [11828.775672] ----------= --[ cut here ]------------ 2019-08-03T18:51:32.787853+08:00 MGDT-ROG kernel: [11828.775778] WARNING: C= PU: 1 PID: 10195 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:329 generic_reg_wait.cold+0x31/0x53 [amdgpu] 2019-08-03T18:51:32.787855+08:00 MGDT-ROG kernel: [11828.775779] Modules li= nked in: tun fuse af_packet ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables bpfilter uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_usb_audio videobuf2_common snd_usbmidi_= lib videodev snd_rawmidi snd_seq_device media joydev scsi_transport_iscsi msr nls_iso8859_1 nls_cp437 vfat fat edac_mce_amd kvm_amd kvm irqbypass snd_hda_codec_realtek crct10dif_pclmul snd_hda_codec_generic crc32_pclmul ledtrig_audio snd_hda_codec_hdmi ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep aesni_intel eeepc_wmi asus_wmi aes_x86= _64 sparse_keymap snd_pcm crypto_simd rfkill cryptd video glue_helper wmi_bmof mxm_wmi igb snd_timer sp5100_tco snd ptp pcspkr i2c_piix4 pps_core dca k10t= emp ccp soundcore gpio_amdpt gpio_generic pcc_cpufreq button acpi_cpufreq btrfs libcrc32c xor hid_generic usbhid amdgpu raid6_pq amd_iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fo= ps xhci_pci drm 2019-08-03T18:51:32.787858+08:00 MGDT-ROG kernel: [11828.775807] crc32c_in= tel xhci_hcd usbcore sr_mod cdrom wmi pinctrl_amd l2tp_ppp l2tp_netlink l2tp_co= re ip6_udp_tunnel udp_tunnel pppox ppp_generic slhc sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs 2019-08-03T18:51:32.787860+08:00 MGDT-ROG kernel: [11828.775817] CPU: 1 PID: 10195 Comm: kworker/1:0 Not tainted 5.2.3-1-default #1 openSUSE Tumbleweed (unreleased) 2019-08-03T18:51:32.787861+08:00 MGDT-ROG kernel: [11828.775818] Hardware n= ame: System manufacturer System Product Name/ROG STRIX X470-F GAMING, BIOS 5007 06/17/2019 2019-08-03T18:51:32.787862+08:00 MGDT-ROG kernel: [11828.775822] Workqueue: events drm_sched_job_timedout [gpu_sched] 2019-08-03T18:51:32.787863+08:00 MGDT-ROG kernel: [11828.775897] RIP: 0010:generic_reg_wait.cold+0x31/0x53 [amdgpu] 2019-08-03T18:51:32.787864+08:00 MGDT-ROG kernel: [11828.775899] Code: 4c 2= 4 18 44 89 fa 89 ee 48 c7 c7 68 7c 75 c0 e8 e9 71 84 f4 83 7b 20 01 0f 84 2b 1b = fe ff 48 c7 c7 d8 7b 75 c0 e8 d3 71 84 f4 <0f> 0b e9 18 1b fe ff 48 c7 c7 d8 7= b 75 c0 89 54 24 04 e8 bc 71 84 2019-08-03T18:51:32.787866+08:00 MGDT-ROG kernel: [11828.775901] RSP: 0018:ffffab7acdeb77e8 EFLAGS: 00010282 2019-08-03T18:51:32.787867+08:00 MGDT-ROG kernel: [11828.775902] RAX: 0000000000000024 RBX: ffff960e92c3c880 RCX: 0000000000000006 2019-08-03T18:51:32.787868+08:00 MGDT-ROG kernel: [11828.775903] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff960e9e659a10 2019-08-03T18:51:32.787869+08:00 MGDT-ROG kernel: [11828.775903] RBP: 000000000000000a R08: 00000000000004da R09: 0000000000000001 2019-08-03T18:51:32.787870+08:00 MGDT-ROG kernel: [11828.775904] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000004ee2 2019-08-03T18:51:32.787871+08:00 MGDT-ROG kernel: [11828.775905] R13: 0000000000000bb9 R14: 0000000000000000 R15: 0000000000000bb8 2019-08-03T18:51:32.787872+08:00 MGDT-ROG kernel: [11828.775906] FS:=20 0000000000000000(0000) GS:ffff960e9e640000(0000) knlGS:0000000000000000 2019-08-03T18:51:32.787874+08:00 MGDT-ROG kernel: [11828.775907] CS: 0010 = DS: 0000 ES: 0000 CR0: 0000000080050033 2019-08-03T18:51:32.787874+08:00 MGDT-ROG kernel: [11828.775907] CR2: 000055d4170da000 CR3: 0000000f03cd6000 CR4: 00000000003406e0 2019-08-03T18:51:32.787875+08:00 MGDT-ROG kernel: [11828.775908] Call Trace: 2019-08-03T18:51:32.787876+08:00 MGDT-ROG kernel: [11828.775982]=20 dce110_stream_encoder_dp_blank+0xda/0x120 [amdgpu] 2019-08-03T18:51:32.787877+08:00 MGDT-ROG kernel: [11828.776049]=20 core_link_disable_stream+0x32/0x260 [amdgpu] 2019-08-03T18:51:32.787878+08:00 MGDT-ROG kernel: [11828.776054] ? printk+0x48/0x4a 2019-08-03T18:51:32.787879+08:00 MGDT-ROG kernel: [11828.776119]=20 dce110_reset_hw_ctx_wrap+0xc1/0x1e0 [amdgpu] 2019-08-03T18:51:32.787881+08:00 MGDT-ROG kernel: [11828.776192] ? vega20_dpm_force_dpm_level.cold+0x5b/0x90 [amdgpu] 2019-08-03T18:51:32.787882+08:00 MGDT-ROG kernel: [11828.776256]=20 dce110_apply_ctx_to_hw+0x3a/0x470 [amdgpu] 2019-08-03T18:51:32.787883+08:00 MGDT-ROG kernel: [11828.776318] ? hwmgr_handle_task+0x66/0xc0 [amdgpu] 2019-08-03T18:51:32.787884+08:00 MGDT-ROG kernel: [11828.776322] ? mutex_lock+0xe/0x30 2019-08-03T18:51:32.787885+08:00 MGDT-ROG kernel: [11828.776385] ? pp_dpm_dispatch_tasks+0x45/0x60 [amdgpu] 2019-08-03T18:51:32.787886+08:00 MGDT-ROG kernel: [11828.776450] ? dm_pp_apply_display_requirements+0x1a1/0x1c0 [amdgpu] 2019-08-03T18:51:32.787887+08:00 MGDT-ROG kernel: [11828.776513]=20 dc_commit_state_no_check+0x200/0x530 [amdgpu] 2019-08-03T18:51:32.787888+08:00 MGDT-ROG kernel: [11828.776516] ? get_page_from_freelist+0x289/0x380 2019-08-03T18:51:32.787889+08:00 MGDT-ROG kernel: [11828.776579]=20 dc_commit_state+0x8f/0xb0 [amdgpu] 2019-08-03T18:51:32.787889+08:00 MGDT-ROG kernel: [11828.776644]=20 amdgpu_dm_atomic_commit_tail+0x3a6/0xd30 [amdgpu] 2019-08-03T18:51:32.787890+08:00 MGDT-ROG kernel: [11828.776709] ? bw_calcs+0x8ac/0x1440 [amdgpu] 2019-08-03T18:51:32.787892+08:00 MGDT-ROG kernel: [11828.776711] ? __ww_mutex_lock.isra.0+0x2a/0x780 2019-08-03T18:51:32.787893+08:00 MGDT-ROG kernel: [11828.776714] ? _raw_spin_unlock_irqrestore+0x24/0x40 2019-08-03T18:51:32.787893+08:00 MGDT-ROG kernel: [11828.776717] ? __wake_up_common_lock+0x7c/0xa0 2019-08-03T18:51:32.787894+08:00 MGDT-ROG kernel: [11828.776719] ? wait_for_completion_timeout+0xf3/0x110 2019-08-03T18:51:32.787895+08:00 MGDT-ROG kernel: [11828.776720] ? wait_for_completion_interruptible+0x10b/0x150 2019-08-03T18:51:32.787896+08:00 MGDT-ROG kernel: [11828.776728] ? commit_tail+0x3c/0x70 [drm_kms_helper] 2019-08-03T18:51:32.787897+08:00 MGDT-ROG kernel: [11828.776735]=20 commit_tail+0x3c/0x70 [drm_kms_helper] 2019-08-03T18:51:32.787898+08:00 MGDT-ROG kernel: [11828.776742]=20 drm_atomic_helper_commit+0x108/0x110 [drm_kms_helper] 2019-08-03T18:51:32.787899+08:00 MGDT-ROG kernel: [11828.776749]=20 drm_atomic_helper_disable_all+0x144/0x160 [drm_kms_helper] 2019-08-03T18:51:32.787900+08:00 MGDT-ROG kernel: [11828.776756]=20 drm_atomic_helper_suspend+0x4c/0xe0 [drm_kms_helper] 2019-08-03T18:51:32.787901+08:00 MGDT-ROG kernel: [11828.776820]=20 dm_suspend+0x20/0x60 [amdgpu] 2019-08-03T18:51:32.787902+08:00 MGDT-ROG kernel: [11828.776861]=20 amdgpu_device_ip_suspend_phase1+0x8b/0xc0 [amdgpu] 2019-08-03T18:51:32.787903+08:00 MGDT-ROG kernel: [11828.776903]=20 amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu] 2019-08-03T18:51:32.787904+08:00 MGDT-ROG kernel: [11828.776975]=20 amdgpu_device_pre_asic_reset+0x1f4/0x209 [amdgpu] 2019-08-03T18:51:32.787905+08:00 MGDT-ROG kernel: [11828.777047]=20 amdgpu_device_gpu_recover+0x67/0x765 [amdgpu] 2019-08-03T18:51:32.787906+08:00 MGDT-ROG kernel: [11828.777106]=20 amdgpu_job_timedout+0xf7/0x120 [amdgpu] 2019-08-03T18:51:32.787906+08:00 MGDT-ROG kernel: [11828.777110]=20 drm_sched_job_timedout+0x3a/0x70 [gpu_sched] 2019-08-03T18:51:32.787907+08:00 MGDT-ROG kernel: [11828.777113]=20 process_one_work+0x1df/0x3c0 2019-08-03T18:51:32.787908+08:00 MGDT-ROG kernel: [11828.777115]=20 worker_thread+0x4d/0x400 2019-08-03T18:51:32.787909+08:00 MGDT-ROG kernel: [11828.777117]=20 kthread+0xf9/0x130 2019-08-03T18:51:32.787910+08:00 MGDT-ROG kernel: [11828.777119] ? process_one_work+0x3c0/0x3c0 2019-08-03T18:51:32.787911+08:00 MGDT-ROG kernel: [11828.777120] ? kthread_park+0x80/0x80 2019-08-03T18:51:32.787912+08:00 MGDT-ROG kernel: [11828.777122]=20 ret_from_fork+0x27/0x50 2019-08-03T18:51:32.787913+08:00 MGDT-ROG kernel: [11828.777125] ---[ end t= race 9aaf1f62ae398b4b ]--- 2019-08-03T18:51:37.791882+08:00 MGDT-ROG kernel: [11833.780084] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5s= ecs aborting 2019-08-03T18:51:37.791896+08:00 MGDT-ROG kernel: [11833.780129] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing B0B0 (len 2971, WS 4, PS 0) @ 0xB963 2019-08-03T18:51:37.791898+08:00 MGDT-ROG kernel: [11833.780172] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing AFB0 (len 255, WS 4, PS 0) @ 0xB089 2019-08-03T18:51:37.791899+08:00 MGDT-ROG kernel: [11833.780240] [drm:dce110_link_encoder_disable_output [amdgpu]] *ERROR* dce110_link_encoder_disable_output: Failed to execute VBIOS command table! 2019-08-03T18:51:37.791901+08:00 MGDT-ROG kernel: [11833.780240] ----------= --[ cut here ]------------ 2019-08-03T18:51:37.791902+08:00 MGDT-ROG kernel: [11833.780328] WARNING: C= PU: 1 PID: 10195 at drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dce_link_encoder.c:1096 dce110_link_encoder_disable_output+0x13d/0x150 [amdgpu] 2019-08-03T18:51:37.791903+08:00 MGDT-ROG kernel: [11833.780329] Modules li= nked in: tun fuse af_packet ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables bpfilter uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_usb_audio videobuf2_common snd_usbmidi_= lib videodev snd_rawmidi snd_seq_device media joydev scsi_transport_iscsi msr nls_iso8859_1 nls_cp437 vfat fat edac_mce_amd kvm_amd kvm irqbypass snd_hda_codec_realtek crct10dif_pclmul snd_hda_codec_generic crc32_pclmul ledtrig_audio snd_hda_codec_hdmi ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep aesni_intel eeepc_wmi asus_wmi aes_x86= _64 sparse_keymap snd_pcm crypto_simd rfkill cryptd video glue_helper wmi_bmof mxm_wmi igb snd_timer sp5100_tco snd ptp pcspkr i2c_piix4 pps_core dca k10t= emp ccp soundcore gpio_amdpt gpio_generic pcc_cpufreq button acpi_cpufreq btrfs libcrc32c xor hid_generic usbhid amdgpu raid6_pq amd_iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fo= ps xhci_pci drm 2019-08-03T18:51:37.791905+08:00 MGDT-ROG kernel: [11833.780356] crc32c_in= tel xhci_hcd usbcore sr_mod cdrom wmi pinctrl_amd l2tp_ppp l2tp_netlink l2tp_co= re ip6_udp_tunnel udp_tunnel pppox ppp_generic slhc sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs 2019-08-03T18:51:37.791907+08:00 MGDT-ROG kernel: [11833.780365] CPU: 1 PID: 10195 Comm: kworker/1:0 Tainted: G W 5.2.3-1-default #1 open= SUSE Tumbleweed (unreleased) 2019-08-03T18:51:37.791908+08:00 MGDT-ROG kernel: [11833.780366] Hardware n= ame: System manufacturer System Product Name/ROG STRIX X470-F GAMING, BIOS 5007 06/17/2019 2019-08-03T18:51:37.791910+08:00 MGDT-ROG kernel: [11833.780370] Workqueue: events drm_sched_job_timedout [gpu_sched] 2019-08-03T18:51:37.791911+08:00 MGDT-ROG kernel: [11833.780435] RIP: 0010:dce110_link_encoder_disable_output+0x13d/0x150 [amdgpu] 2019-08-03T18:51:37.791912+08:00 MGDT-ROG kernel: [11833.780437] Code: ff f= f 48 83 c4 38 5b 5d 41 5c c3 48 c7 c6 c0 c8 6f c0 48 c7 c7 d8 d9 74 c0 e8 cf bb = de ff 48 c7 c7 70 d9 74 c0 e8 61 13 8c f4 <0f> 0b eb d4 66 66 2e 0f 1f 84 00 0= 0 00 00 00 0f 1f 40 00 0f 1f 44 2019-08-03T18:51:37.791913+08:00 MGDT-ROG kernel: [11833.780438] RSP: 0018:ffffab7acdeb77f8 EFLAGS: 00010282 2019-08-03T18:51:37.791914+08:00 MGDT-ROG kernel: [11833.780439] RAX: 0000000000000024 RBX: ffff960e96034a80 RCX: 0000000000000006 2019-08-03T18:51:37.791915+08:00 MGDT-ROG kernel: [11833.780440] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff960e9e659a10 2019-08-03T18:51:37.791917+08:00 MGDT-ROG kernel: [11833.780441] RBP: 0000000000000020 R08: 0000000000000518 R09: 0000000000000001 2019-08-03T18:51:37.791918+08:00 MGDT-ROG kernel: [11833.780441] R10: 0000000000000000 R11: 0000000000000001 R12: ffffab7acdeb77fc 2019-08-03T18:51:37.791919+08:00 MGDT-ROG kernel: [11833.780442] R13: ffff95ffc13c1000 R14: 0000000000000000 R15: ffff9601c92c8188 2019-08-03T18:51:37.791920+08:00 MGDT-ROG kernel: [11833.780443] FS:=20 0000000000000000(0000) GS:ffff960e9e640000(0000) knlGS:0000000000000000 2019-08-03T18:51:37.791921+08:00 MGDT-ROG kernel: [11833.780444] CS: 0010 = DS: 0000 ES: 0000 CR0: 0000000080050033 2019-08-03T18:51:37.791922+08:00 MGDT-ROG kernel: [11833.780445] CR2: 000055d4170da000 CR3: 0000000f03cd6000 CR4: 00000000003406e0 2019-08-03T18:51:37.791923+08:00 MGDT-ROG kernel: [11833.780446] Call Trace: 2019-08-03T18:51:37.791924+08:00 MGDT-ROG kernel: [11833.780512]=20 dp_disable_link_phy+0x73/0x110 [amdgpu] 2019-08-03T18:51:37.791925+08:00 MGDT-ROG kernel: [11833.780576]=20 core_link_disable_stream+0xb6/0x260 [amdgpu] 2019-08-03T18:51:37.791926+08:00 MGDT-ROG kernel: [11833.780580] ? printk+0x48/0x4a 2019-08-03T18:51:37.791927+08:00 MGDT-ROG kernel: [11833.780642]=20 dce110_reset_hw_ctx_wrap+0xc1/0x1e0 [amdgpu] 2019-08-03T18:51:37.791928+08:00 MGDT-ROG kernel: [11833.780716] ? vega20_dpm_force_dpm_level.cold+0x5b/0x90 [amdgpu] 2019-08-03T18:51:37.791929+08:00 MGDT-ROG kernel: [11833.780779]=20 dce110_apply_ctx_to_hw+0x3a/0x470 [amdgpu] 2019-08-03T18:51:37.791930+08:00 MGDT-ROG kernel: [11833.780840] ? hwmgr_handle_task+0x66/0xc0 [amdgpu] 2019-08-03T18:51:37.791931+08:00 MGDT-ROG kernel: [11833.780843] ? mutex_lock+0xe/0x30 2019-08-03T18:51:37.791933+08:00 MGDT-ROG kernel: [11833.780905] ? pp_dpm_dispatch_tasks+0x45/0x60 [amdgpu] 2019-08-03T18:51:37.791934+08:00 MGDT-ROG kernel: [11833.780969] ? dm_pp_apply_display_requirements+0x1a1/0x1c0 [amdgpu] 2019-08-03T18:51:37.791935+08:00 MGDT-ROG kernel: [11833.781032]=20 dc_commit_state_no_check+0x200/0x530 [amdgpu] 2019-08-03T18:51:37.791936+08:00 MGDT-ROG kernel: [11833.781036] ? get_page_from_freelist+0x289/0x380 2019-08-03T18:51:37.791937+08:00 MGDT-ROG kernel: [11833.781098]=20 dc_commit_state+0x8f/0xb0 [amdgpu] 2019-08-03T18:51:37.791938+08:00 MGDT-ROG kernel: [11833.781162]=20 amdgpu_dm_atomic_commit_tail+0x3a6/0xd30 [amdgpu] 2019-08-03T18:51:37.791939+08:00 MGDT-ROG kernel: [11833.781227] ? bw_calcs+0x8ac/0x1440 [amdgpu] 2019-08-03T18:51:37.791940+08:00 MGDT-ROG kernel: [11833.781229] ? __ww_mutex_lock.isra.0+0x2a/0x780 2019-08-03T18:51:37.791941+08:00 MGDT-ROG kernel: [11833.781231] ? _raw_spin_unlock_irqrestore+0x24/0x40 2019-08-03T18:51:37.791942+08:00 MGDT-ROG kernel: [11833.781234] ? __wake_up_common_lock+0x7c/0xa0 2019-08-03T18:51:37.791943+08:00 MGDT-ROG kernel: [11833.781236] ? wait_for_completion_timeout+0xf3/0x110 2019-08-03T18:51:37.791944+08:00 MGDT-ROG kernel: [11833.781237] ? wait_for_completion_interruptible+0x10b/0x150 2019-08-03T18:51:37.791945+08:00 MGDT-ROG kernel: [11833.781245] ? commit_tail+0x3c/0x70 [drm_kms_helper] 2019-08-03T18:51:37.791946+08:00 MGDT-ROG kernel: [11833.781251]=20 commit_tail+0x3c/0x70 [drm_kms_helper] 2019-08-03T18:51:37.791947+08:00 MGDT-ROG kernel: [11833.781258]=20 drm_atomic_helper_commit+0x108/0x110 [drm_kms_helper] 2019-08-03T18:51:37.791948+08:00 MGDT-ROG kernel: [11833.781265]=20 drm_atomic_helper_disable_all+0x144/0x160 [drm_kms_helper] 2019-08-03T18:51:37.791949+08:00 MGDT-ROG kernel: [11833.781272]=20 drm_atomic_helper_suspend+0x4c/0xe0 [drm_kms_helper] 2019-08-03T18:51:37.791950+08:00 MGDT-ROG kernel: [11833.781335]=20 dm_suspend+0x20/0x60 [amdgpu] 2019-08-03T18:51:37.791951+08:00 MGDT-ROG kernel: [11833.781377]=20 amdgpu_device_ip_suspend_phase1+0x8b/0xc0 [amdgpu] 2019-08-03T18:51:37.791952+08:00 MGDT-ROG kernel: [11833.781418]=20 amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu] 2019-08-03T18:51:37.791953+08:00 MGDT-ROG kernel: [11833.781490]=20 amdgpu_device_pre_asic_reset+0x1f4/0x209 [amdgpu] 2019-08-03T18:51:37.791954+08:00 MGDT-ROG kernel: [11833.781561]=20 amdgpu_device_gpu_recover+0x67/0x765 [amdgpu] 2019-08-03T18:51:37.791955+08:00 MGDT-ROG kernel: [11833.781620]=20 amdgpu_job_timedout+0xf7/0x120 [amdgpu] 2019-08-03T18:51:37.791956+08:00 MGDT-ROG kernel: [11833.781624]=20 drm_sched_job_timedout+0x3a/0x70 [gpu_sched] 2019-08-03T18:51:37.791957+08:00 MGDT-ROG kernel: [11833.781627]=20 process_one_work+0x1df/0x3c0 2019-08-03T18:51:37.791958+08:00 MGDT-ROG kernel: [11833.781629]=20 worker_thread+0x4d/0x400 2019-08-03T18:51:37.791959+08:00 MGDT-ROG kernel: [11833.781631]=20 kthread+0xf9/0x130 2019-08-03T18:51:37.791960+08:00 MGDT-ROG kernel: [11833.781633] ? process_one_work+0x3c0/0x3c0 2019-08-03T18:51:37.791961+08:00 MGDT-ROG kernel: [11833.781634] ? kthread_park+0x80/0x80 2019-08-03T18:51:37.791962+08:00 MGDT-ROG kernel: [11833.781636]=20 ret_from_fork+0x27/0x50 2019-08-03T18:51:37.791963+08:00 MGDT-ROG kernel: [11833.781639] ---[ end t= race 9aaf1f62ae398b4c ]--- 2019-08-03T18:51:42.796019+08:00 MGDT-ROG kernel: [11838.784083] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5s= ecs aborting 2019-08-03T18:51:42.796034+08:00 MGDT-ROG kernel: [11838.784127] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing A048 (len 62, WS 0, PS 0) @ 0xA064 2019-08-03T18:51:42.796035+08:00 MGDT-ROG kernel: [11838.784208] amdgpu: [powerplay] Failed to send message 0x28, response 0xffffffff 2019-08-03T18:51:42.796036+08:00 MGDT-ROG kernel: [11838.784219] amdgpu: [powerplay] Failed to send message 0x28, response 0xffffffff 2019-08-03T18:51:42.796038+08:00 MGDT-ROG kernel: [11838.784233] amdgpu: [powerplay] Failed to send message 0x47, response 0xffffffff 2019-08-03T18:51:42.796039+08:00 MGDT-ROG kernel: [11838.784245] amdgpu: [powerplay] Failed to send message 0x28, response 0xffffffff 2019-08-03T18:51:42.796040+08:00 MGDT-ROG kernel: [11838.784245] amdgpu: [powerplay] [SetUclkToHightestDpmLevel] Set hard min uclk failed! 2019-08-03T18:51:42.796041+08:00 MGDT-ROG kernel: [11838.784258] amdgpu: [powerplay] Failed to send message 0x28, response 0xffffffff 2019-08-03T18:51:42.796042+08:00 MGDT-ROG kernel: [11838.784258] amdgpu: [powerplay] Attempt to set Hard Min for DCEFCLK Failed! 2019-08-03T18:51:42.796044+08:00 MGDT-ROG kernel: [11838.784269] amdgpu: [powerplay] Failed to send message 0x28, response 0xffffffff 2019-08-03T18:51:42.796045+08:00 MGDT-ROG kernel: [11838.784270] amdgpu: [powerplay] [SetHardMinFreq] Set hard min uclk failed! 2019-08-03T18:51:42.796046+08:00 MGDT-ROG kernel: [11838.784281] amdgpu: [powerplay] Failed to send message 0x26, response 0xffffffff 2019-08-03T18:51:42.796047+08:00 MGDT-ROG kernel: [11838.784282] amdgpu: [powerplay] Failed to set soft min gfxclk ! 2019-08-03T18:51:42.796048+08:00 MGDT-ROG kernel: [11838.784282] amdgpu: [powerplay] Failed to upload DPM Bootup Levels! 2019-08-03T18:51:43.656061+08:00 MGDT-ROG kernel: [11839.645436] amdgpu: [powerplay] Failed to send message 0x26, response 0xffffffff 2019-08-03T18:51:43.656078+08:00 MGDT-ROG kernel: [11839.645438] amdgpu: [powerplay] Failed to set soft min gfxclk ! 2019-08-03T18:51:43.656080+08:00 MGDT-ROG kernel: [11839.645438] amdgpu: [powerplay] Failed to upload DPM Bootup Levels! 2019-08-03T18:51:43.656081+08:00 MGDT-ROG kernel: [11839.645449] amdgpu: [powerplay] Failed to send message 0x7, response 0xffffffff 2019-08-03T18:51:43.656082+08:00 MGDT-ROG kernel: [11839.645450] amdgpu: [powerplay] [DisableAllSMUFeatures] Failed to disable all smu features! 2019-08-03T18:51:43.656083+08:00 MGDT-ROG kernel: [11839.645450] amdgpu: [powerplay] [DisableDpmTasks] Failed to disable all smu features! 2019-08-03T18:51:43.656084+08:00 MGDT-ROG kernel: [11839.645451] amdgpu: [powerplay] [PowerOffAsic] Failed to disable DPM! 2019-08-03T18:51:43.656086+08:00 MGDT-ROG kernel: [11839.645497] [drm:amdgpu_device_ip_suspend_phase2 [amdgpu]] *ERROR* suspend of IP block failed -5 2019-08-03T18:51:43.911990+08:00 MGDT-ROG kernel: [11839.902893] amdgpu 0000:0a:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) 2019-08-03T18:51:43.912001+08:00 MGDT-ROG kernel: [11839.902947] [drm:gfx_v9_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed 2019-08-03T18:51:44.167806+08:00 MGDT-ROG kernel: [11840.159797] [drm] Time= out wait for RLC serdes 0,0 2019-08-03T18:51:44.191826+08:00 MGDT-ROG kernel: [11840.180793] amdgpu 0000:0a:00.0: GPU mode1 reset 2019-08-03T18:51:44.451982+08:00 MGDT-ROG kernel: [11840.442308] [drm] psp = is not working correctly before mode1 reset! 2019-08-03T18:51:44.451993+08:00 MGDT-ROG kernel: [11840.442310] amdgpu 0000:0a:00.0: GPU mode1 reset failed 2019-08-03T18:51:44.719056+08:00 MGDT-ROG kernel: [11840.710967] [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* ASIC reset failed with err= or, -22 for drm dev, 0000:0a:00.0 2019-08-03T18:51:44.719066+08:00 MGDT-ROG kernel: [11840.711014] amdgpu 0000:0a:00.0: GPU reset(1) failed 2019-08-03T18:51:44.719068+08:00 MGDT-ROG kernel: [11840.711033] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719068+08:00 MGDT-ROG kernel: [11840.711038] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719070+08:00 MGDT-ROG kernel: [11840.711040] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719071+08:00 MGDT-ROG kernel: [11840.711043] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719072+08:00 MGDT-ROG kernel: [11840.711045] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719073+08:00 MGDT-ROG kernel: [11840.711049] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719075+08:00 MGDT-ROG kernel: [11840.711051] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719076+08:00 MGDT-ROG kernel: [11840.711053] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719077+08:00 MGDT-ROG kernel: [11840.711057] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719078+08:00 MGDT-ROG kernel: [11840.711059] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719079+08:00 MGDT-ROG kernel: [11840.711061] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719080+08:00 MGDT-ROG kernel: [11840.711064] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719081+08:00 MGDT-ROG kernel: [11840.711066] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719082+08:00 MGDT-ROG kernel: [11840.711068] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719083+08:00 MGDT-ROG kernel: [11840.711072] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719084+08:00 MGDT-ROG kernel: [11840.711075] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719085+08:00 MGDT-ROG kernel: [11840.711077] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719086+08:00 MGDT-ROG kernel: [11840.711080] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719087+08:00 MGDT-ROG kernel: [11840.711083] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719088+08:00 MGDT-ROG kernel: [11840.711085] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719089+08:00 MGDT-ROG kernel: [11840.711087] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719090+08:00 MGDT-ROG kernel: [11840.711090] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719091+08:00 MGDT-ROG kernel: [11840.711092] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719092+08:00 MGDT-ROG kernel: [11840.711094] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719093+08:00 MGDT-ROG kernel: [11840.711096] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719094+08:00 MGDT-ROG kernel: [11840.711097] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719095+08:00 MGDT-ROG kernel: [11840.711100] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719096+08:00 MGDT-ROG kernel: [11840.711102] amdgpu 0000:0a:00.0: GPU reset end with ret =3D -22 2019-08-03T18:51:44.719097+08:00 MGDT-ROG kernel: [11840.711102] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719098+08:00 MGDT-ROG kernel: [11840.711104] [drm] Skip scheduling IBs! 2019-08-03T18:51:44.719099+08:00 MGDT-ROG kernel: [11840.711106] [drm] Skip scheduling IBs! 2019-08-03T18:51:54.767980+08:00 MGDT-ROG kernel: [11850.756186] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=3D2324986, emitted seq=3D2324986 2019-08-03T18:51:54.767994+08:00 MGDT-ROG kernel: [11850.756247] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process X p= id 2132 thread X:cs0 pid 2139 2019-08-03T18:51:54.767996+08:00 MGDT-ROG kernel: [11850.756251] amdgpu 0000:0a:00.0: GPU reset begin! --=20 You are receiving this mail because: You are the assignee for the bug.= --15648393552.c39C0F3Ed.28674 Date: Sat, 3 Aug 2019 13:35:55 +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

Comme= nt # 72 on bug 10995= 5 from = Mauro Gaspari 
After a few weeks without crashes on Ubuntu Budgie 18.04 LTS w=
ith valve
mesa-aco, I moved to another distribution that does not have valve mesa-aco=
 to
cross check.

This is what I am using:
OS: openSUSE Tumbleweed x86_64=20
Kernel: 5.2.2-1-default
Resolution: 3440x1440
DE: Xfce
WM: Xfwm4
CPU: AMD Ryzen 7 2700X (16) @ 3.700GHz
GPU: AMD ATI Radeon VII
Memory: 1644MiB / 64387MiB=20
OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.3
No kernel parameters configured, just out of the box openSUSE

I had 3 of full OS freezes:

1. As I was playing Albion Online (Native) No full system freeze, I was abl=
e to
drop to tty, and notice this error: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR*
Failed to initialize parser -125!

2. As I closed down Albion Online (Native) and returned to desktop. Full Sy=
stem
Freeze

3. As I was doing regular desktop operations on XFCE. No 3d gaming going on.
Please see below logs:

DMESG after crash:

ilvipero@MGDT-ROG:~> dmesg | grep amdgpu
[    5.758450] [drm] amdgpu kernel modesetting enabled.
[    5.758569] amdgpu 0000:0a:00.0: remove_conflicting_pci_framebuffers: ba=
r 0:
0xe0000000 -> 0xefffffff
[    5.758570] amdgpu 0000:0a:00.0: remove_conflicting_pci_framebuffers: ba=
r 2:
0xf0000000 -> 0xf01fffff
[    5.758571] amdgpu 0000:0a:00.0: remove_conflicting_pci_framebuffers: ba=
r 5:
0xfcd00000 -> 0xfcd7ffff
[    5.758573] fb0: switching to amdgpudrmfb from EFI VGA
[    5.758646] amdgpu 0000:0a:00.0: vgaarb: deactivate vga console
[    5.758826] amdgpu 0000:0a:00.0: No more image in the PCI ROM
[    5.758870] amdgpu 0000:0a:00.0: VRAM: 16368M 0x0000008000000000 -
0x00000083FEFFFFFF (16368M used)
[    5.758871] amdgpu 0000:0a:00.0: GART: 512M 0x0000000000000000 -
0x000000001FFFFFFF
[    5.758872] amdgpu 0000:0a:00.0: AGP: 267894784M 0x0000008400000000 -
0x0000FFFFFFFFFFFF
[    5.758936] [drm] amdgpu: 16368M of VRAM memory ready
[    5.758938] [drm] amdgpu: 16368M of GTT memory ready.
[    5.759204] amdgpu 0000:0a:00.0: Direct firmware load for
amdgpu/vega20_ta.bin failed with error -2
[    5.759205] amdgpu 0000:0a:00.0: psp v11.0: Failed to load firmware
"amdgpu/vega20_ta.bin"
[    6.855053] fbcon: amdgpudrmfb (fb0) is primary device
[    6.913835] amdgpu 0000:0a:00.0: fb0: amdgpudrmfb frame buffer device
[    6.928054] amdgpu 0000:0a:00.0: ring gfx uses VM inv eng 0 on hub 0
[    6.928055] amdgpu 0000:0a:00.0: ring comp_1.0.0 uses VM inv eng 1 on hu=
b 0
[    6.928056] amdgpu 0000:0a:00.0: ring comp_1.1.0 uses VM inv eng 4 on hu=
b 0
[    6.928056] amdgpu 0000:0a:00.0: ring comp_1.2.0 uses VM inv eng 5 on hu=
b 0
[    6.928057] amdgpu 0000:0a:00.0: ring comp_1.3.0 uses VM inv eng 6 on hu=
b 0
[    6.928058] amdgpu 0000:0a:00.0: ring comp_1.0.1 uses VM inv eng 7 on hu=
b 0
[    6.928059] amdgpu 0000:0a:00.0: ring comp_1.1.1 uses VM inv eng 8 on hu=
b 0
[    6.928059] amdgpu 0000:0a:00.0: ring comp_1.2.1 uses VM inv eng 9 on hu=
b 0
[    6.928060] amdgpu 0000:0a:00.0: ring comp_1.3.1 uses VM inv eng 10 on h=
ub 0
[    6.928060] amdgpu 0000:0a:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hu=
b 0
[    6.928061] amdgpu 0000:0a:00.0: ring sdma0 uses VM inv eng 0 on hub 1
[    6.928062] amdgpu 0000:0a:00.0: ring page0 uses VM inv eng 1 on hub 1
[    6.928063] amdgpu 0000:0a:00.0: ring sdma1 uses VM inv eng 4 on hub 1
[    6.928063] amdgpu 0000:0a:00.0: ring page1 uses VM inv eng 5 on hub 1
[    6.928064] amdgpu 0000:0a:00.0: ring uvd_0 uses VM inv eng 6 on hub 1
[    6.928064] amdgpu 0000:0a:00.0: ring uvd_enc_0.0 uses VM inv eng 7 on h=
ub 1
[    6.928065] amdgpu 0000:0a:00.0: ring uvd_enc_0.1 uses VM inv eng 8 on h=
ub 1
[    6.928066] amdgpu 0000:0a:00.0: ring uvd_1 uses VM inv eng 9 on hub 1
[    6.928066] amdgpu 0000:0a:00.0: ring uvd_enc_1.0 uses VM inv eng 10 on =
hub
1
[    6.928067] amdgpu 0000:0a:00.0: ring uvd_enc_1.1 uses VM inv eng 11 on =
hub
1
[    6.928067] amdgpu 0000:0a:00.0: ring vce0 uses VM inv eng 12 on hub 1
[    6.928068] amdgpu 0000:0a:00.0: ring vce1 uses VM inv eng 13 on hub 1
[    6.928068] amdgpu 0000:0a:00.0: ring vce2 uses VM inv eng 14 on hub 1
[    7.609167] [drm] Initialized amdgpu 3.32.0 20150101 for 0000:0a:00.0 on
minor 0

system logs:

2019-08-03T18:51:21.779695+08:00 MGDT-ROG kernel: [11817.727681] pcieport
0000:00:03.1: AER: Multiple Corrected error received: 0000:00:00.0
2019-08-03T18:51:21.779730+08:00 MGDT-ROG kernel: [11817.771355] pcieport
0000:00:03.1: AER: PCIe Bus Error: severity=3DCorrected, type=3DData Link L=
ayer,
(Transmitter ID)
2019-08-03T18:51:21.779735+08:00 MGDT-ROG kernel: [11817.771358] pcieport
0000:00:03.1: AER:   device [1022:1453] error status/mask=3D00003100/000060=
00
2019-08-03T18:51:21.779737+08:00 MGDT-ROG kernel: [11817.771361] pcieport
0000:00:03.1: AER:    [ 8] Rollover=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20
2019-08-03T18:51:21.779738+08:00 MGDT-ROG kernel: [11817.771371] pcieport
0000:00:03.1: AER:    [12] Timeout=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20
2019-08-03T18:51:26.721833+08:00 MGDT-ROG sudo: pam_unix(sudo:session): ses=
sion
closed for user root
2019-08-03T18:51:31.983837+08:00 MGDT-ROG kernel: [11827.971739]
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled
seq=3D2324984, emitted seq=3D2324986
2019-08-03T18:51:31.983851+08:00 MGDT-ROG kernel: [11827.971800]
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process X p=
id
2132 thread X:cs0 pid 2139
2019-08-03T18:51:31.983853+08:00 MGDT-ROG kernel: [11827.971804] amdgpu
0000:0a:00.0: GPU reset begin!
2019-08-03T18:51:32.751834+08:00 MGDT-ROG kernel: [11828.741066] amdgpu:
[powerplay] Failed to send message 0x47, response 0xffffffff
2019-08-03T18:51:32.751846+08:00 MGDT-ROG kernel: [11828.741077] amdgpu:
[powerplay] Failed to send message 0x28, response 0xffffffff
2019-08-03T18:51:32.751849+08:00 MGDT-ROG kernel: [11828.741078] amdgpu:
[powerplay] [SetUclkToHightestDpmLevel] Set hard min uclk failed!
2019-08-03T18:51:32.751850+08:00 MGDT-ROG kernel: [11828.741090] amdgpu:
[powerplay] Failed to send message 0x28, response 0xffffffff
2019-08-03T18:51:32.751852+08:00 MGDT-ROG kernel: [11828.741091] amdgpu:
[powerplay] Attempt to set Hard Min for DCEFCLK Failed!
2019-08-03T18:51:32.751854+08:00 MGDT-ROG kernel: [11828.741102] amdgpu:
[powerplay] Failed to send message 0x28, response 0xffffffff
2019-08-03T18:51:32.751855+08:00 MGDT-ROG kernel: [11828.741102] amdgpu:
[powerplay] [SetHardMinFreq] Set hard min uclk failed!
2019-08-03T18:51:32.751856+08:00 MGDT-ROG kernel: [11828.741113] amdgpu:
[powerplay] Failed to send message 0x26, response 0xffffffff
2019-08-03T18:51:32.751858+08:00 MGDT-ROG kernel: [11828.741114] amdgpu:
[powerplay] Failed to set soft min gfxclk !
2019-08-03T18:51:32.751859+08:00 MGDT-ROG kernel: [11828.741114] amdgpu:
[powerplay] Failed to upload DPM Bootup Levels!
2019-08-03T18:51:32.787843+08:00 MGDT-ROG kernel: [11828.775671] [drm] REG_=
WAIT
timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:951
2019-08-03T18:51:32.787852+08:00 MGDT-ROG kernel: [11828.775672] ----------=
--[
cut here ]------------
2019-08-03T18:51:32.787853+08:00 MGDT-ROG kernel: [11828.775778] WARNING: C=
PU:
1 PID: 10195 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:329
generic_reg_wait.cold+0x31/0x53 [amdgpu]
2019-08-03T18:51:32.787855+08:00 MGDT-ROG kernel: [11828.775779] Modules li=
nked
in: tun fuse af_packet ebtable_filter ebtables ip6table_filter ip6_tables
iptable_filter ip_tables x_tables bpfilter uvcvideo videobuf2_vmalloc
videobuf2_memops videobuf2_v4l2 snd_usb_audio videobuf2_common snd_usbmidi_=
lib
videodev snd_rawmidi snd_seq_device media joydev scsi_transport_iscsi msr
nls_iso8859_1 nls_cp437 vfat fat edac_mce_amd kvm_amd kvm irqbypass
snd_hda_codec_realtek crct10dif_pclmul snd_hda_codec_generic crc32_pclmul
ledtrig_audio snd_hda_codec_hdmi ghash_clmulni_intel snd_hda_intel
snd_hda_codec snd_hda_core snd_hwdep aesni_intel eeepc_wmi asus_wmi aes_x86=
_64
sparse_keymap snd_pcm crypto_simd rfkill cryptd video glue_helper wmi_bmof
mxm_wmi igb snd_timer sp5100_tco snd ptp pcspkr i2c_piix4 pps_core dca k10t=
emp
ccp soundcore gpio_amdpt gpio_generic pcc_cpufreq button acpi_cpufreq btrfs
libcrc32c xor hid_generic usbhid amdgpu raid6_pq amd_iommu_v2 gpu_sched
i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fo=
ps
xhci_pci drm
2019-08-03T18:51:32.787858+08:00 MGDT-ROG kernel: [11828.775807]  crc32c_in=
tel
xhci_hcd usbcore sr_mod cdrom wmi pinctrl_amd l2tp_ppp l2tp_netlink l2tp_co=
re
ip6_udp_tunnel udp_tunnel pppox ppp_generic slhc sg dm_multipath dm_mod
scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs
2019-08-03T18:51:32.787860+08:00 MGDT-ROG kernel: [11828.775817] CPU: 1 PID:
10195 Comm: kworker/1:0 Not tainted 5.2.3-1-default #1 openSUSE Tumbleweed
(unreleased)
2019-08-03T18:51:32.787861+08:00 MGDT-ROG kernel: [11828.775818] Hardware n=
ame:
System manufacturer System Product Name/ROG STRIX X470-F GAMING, BIOS 5007
06/17/2019
2019-08-03T18:51:32.787862+08:00 MGDT-ROG kernel: [11828.775822] Workqueue:
events drm_sched_job_timedout [gpu_sched]
2019-08-03T18:51:32.787863+08:00 MGDT-ROG kernel: [11828.775897] RIP:
0010:generic_reg_wait.cold+0x31/0x53 [amdgpu]
2019-08-03T18:51:32.787864+08:00 MGDT-ROG kernel: [11828.775899] Code: 4c 2=
4 18
44 89 fa 89 ee 48 c7 c7 68 7c 75 c0 e8 e9 71 84 f4 83 7b 20 01 0f 84 2b 1b =
fe
ff 48 c7 c7 d8 7b 75 c0 e8 d3 71 84 f4 <0f> 0b e9 18 1b fe ff 48 c7 c=
7 d8 7b 75
c0 89 54 24 04 e8 bc 71 84
2019-08-03T18:51:32.787866+08:00 MGDT-ROG kernel: [11828.775901] RSP:
0018:ffffab7acdeb77e8 EFLAGS: 00010282
2019-08-03T18:51:32.787867+08:00 MGDT-ROG kernel: [11828.775902] RAX:
0000000000000024 RBX: ffff960e92c3c880 RCX: 0000000000000006
2019-08-03T18:51:32.787868+08:00 MGDT-ROG kernel: [11828.775903] RDX:
0000000000000007 RSI: 0000000000000096 RDI: ffff960e9e659a10
2019-08-03T18:51:32.787869+08:00 MGDT-ROG kernel: [11828.775903] RBP:
000000000000000a R08: 00000000000004da R09: 0000000000000001
2019-08-03T18:51:32.787870+08:00 MGDT-ROG kernel: [11828.775904] R10:
0000000000000000 R11: 0000000000000001 R12: 0000000000004ee2
2019-08-03T18:51:32.787871+08:00 MGDT-ROG kernel: [11828.775905] R13:
0000000000000bb9 R14: 0000000000000000 R15: 0000000000000bb8
2019-08-03T18:51:32.787872+08:00 MGDT-ROG kernel: [11828.775906] FS:=20
0000000000000000(0000) GS:ffff960e9e640000(0000) knlGS:0000000000000000
2019-08-03T18:51:32.787874+08:00 MGDT-ROG kernel: [11828.775907] CS:  0010 =
DS:
0000 ES: 0000 CR0: 0000000080050033
2019-08-03T18:51:32.787874+08:00 MGDT-ROG kernel: [11828.775907] CR2:
000055d4170da000 CR3: 0000000f03cd6000 CR4: 00000000003406e0
2019-08-03T18:51:32.787875+08:00 MGDT-ROG kernel: [11828.775908] Call Trace:
2019-08-03T18:51:32.787876+08:00 MGDT-ROG kernel: [11828.775982]=20
dce110_stream_encoder_dp_blank+0xda/0x120 [amdgpu]
2019-08-03T18:51:32.787877+08:00 MGDT-ROG kernel: [11828.776049]=20
core_link_disable_stream+0x32/0x260 [amdgpu]
2019-08-03T18:51:32.787878+08:00 MGDT-ROG kernel: [11828.776054]  ?
printk+0x48/0x4a
2019-08-03T18:51:32.787879+08:00 MGDT-ROG kernel: [11828.776119]=20
dce110_reset_hw_ctx_wrap+0xc1/0x1e0 [amdgpu]
2019-08-03T18:51:32.787881+08:00 MGDT-ROG kernel: [11828.776192]  ?
vega20_dpm_force_dpm_level.cold+0x5b/0x90 [amdgpu]
2019-08-03T18:51:32.787882+08:00 MGDT-ROG kernel: [11828.776256]=20
dce110_apply_ctx_to_hw+0x3a/0x470 [amdgpu]
2019-08-03T18:51:32.787883+08:00 MGDT-ROG kernel: [11828.776318]  ?
hwmgr_handle_task+0x66/0xc0 [amdgpu]
2019-08-03T18:51:32.787884+08:00 MGDT-ROG kernel: [11828.776322]  ?
mutex_lock+0xe/0x30
2019-08-03T18:51:32.787885+08:00 MGDT-ROG kernel: [11828.776385]  ?
pp_dpm_dispatch_tasks+0x45/0x60 [amdgpu]
2019-08-03T18:51:32.787886+08:00 MGDT-ROG kernel: [11828.776450]  ?
dm_pp_apply_display_requirements+0x1a1/0x1c0 [amdgpu]
2019-08-03T18:51:32.787887+08:00 MGDT-ROG kernel: [11828.776513]=20
dc_commit_state_no_check+0x200/0x530 [amdgpu]
2019-08-03T18:51:32.787888+08:00 MGDT-ROG kernel: [11828.776516]  ?
get_page_from_freelist+0x289/0x380
2019-08-03T18:51:32.787889+08:00 MGDT-ROG kernel: [11828.776579]=20
dc_commit_state+0x8f/0xb0 [amdgpu]
2019-08-03T18:51:32.787889+08:00 MGDT-ROG kernel: [11828.776644]=20
amdgpu_dm_atomic_commit_tail+0x3a6/0xd30 [amdgpu]
2019-08-03T18:51:32.787890+08:00 MGDT-ROG kernel: [11828.776709]  ?
bw_calcs+0x8ac/0x1440 [amdgpu]
2019-08-03T18:51:32.787892+08:00 MGDT-ROG kernel: [11828.776711]  ?
__ww_mutex_lock.isra.0+0x2a/0x780
2019-08-03T18:51:32.787893+08:00 MGDT-ROG kernel: [11828.776714]  ?
_raw_spin_unlock_irqrestore+0x24/0x40
2019-08-03T18:51:32.787893+08:00 MGDT-ROG kernel: [11828.776717]  ?
__wake_up_common_lock+0x7c/0xa0
2019-08-03T18:51:32.787894+08:00 MGDT-ROG kernel: [11828.776719]  ?
wait_for_completion_timeout+0xf3/0x110
2019-08-03T18:51:32.787895+08:00 MGDT-ROG kernel: [11828.776720]  ?
wait_for_completion_interruptible+0x10b/0x150
2019-08-03T18:51:32.787896+08:00 MGDT-ROG kernel: [11828.776728]  ?
commit_tail+0x3c/0x70 [drm_kms_helper]
2019-08-03T18:51:32.787897+08:00 MGDT-ROG kernel: [11828.776735]=20
commit_tail+0x3c/0x70 [drm_kms_helper]
2019-08-03T18:51:32.787898+08:00 MGDT-ROG kernel: [11828.776742]=20
drm_atomic_helper_commit+0x108/0x110 [drm_kms_helper]
2019-08-03T18:51:32.787899+08:00 MGDT-ROG kernel: [11828.776749]=20
drm_atomic_helper_disable_all+0x144/0x160 [drm_kms_helper]
2019-08-03T18:51:32.787900+08:00 MGDT-ROG kernel: [11828.776756]=20
drm_atomic_helper_suspend+0x4c/0xe0 [drm_kms_helper]
2019-08-03T18:51:32.787901+08:00 MGDT-ROG kernel: [11828.776820]=20
dm_suspend+0x20/0x60 [amdgpu]
2019-08-03T18:51:32.787902+08:00 MGDT-ROG kernel: [11828.776861]=20
amdgpu_device_ip_suspend_phase1+0x8b/0xc0 [amdgpu]
2019-08-03T18:51:32.787903+08:00 MGDT-ROG kernel: [11828.776903]=20
amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu]
2019-08-03T18:51:32.787904+08:00 MGDT-ROG kernel: [11828.776975]=20
amdgpu_device_pre_asic_reset+0x1f4/0x209 [amdgpu]
2019-08-03T18:51:32.787905+08:00 MGDT-ROG kernel: [11828.777047]=20
amdgpu_device_gpu_recover+0x67/0x765 [amdgpu]
2019-08-03T18:51:32.787906+08:00 MGDT-ROG kernel: [11828.777106]=20
amdgpu_job_timedout+0xf7/0x120 [amdgpu]
2019-08-03T18:51:32.787906+08:00 MGDT-ROG kernel: [11828.777110]=20
drm_sched_job_timedout+0x3a/0x70 [gpu_sched]
2019-08-03T18:51:32.787907+08:00 MGDT-ROG kernel: [11828.777113]=20
process_one_work+0x1df/0x3c0
2019-08-03T18:51:32.787908+08:00 MGDT-ROG kernel: [11828.777115]=20
worker_thread+0x4d/0x400
2019-08-03T18:51:32.787909+08:00 MGDT-ROG kernel: [11828.777117]=20
kthread+0xf9/0x130
2019-08-03T18:51:32.787910+08:00 MGDT-ROG kernel: [11828.777119]  ?
process_one_work+0x3c0/0x3c0
2019-08-03T18:51:32.787911+08:00 MGDT-ROG kernel: [11828.777120]  ?
kthread_park+0x80/0x80
2019-08-03T18:51:32.787912+08:00 MGDT-ROG kernel: [11828.777122]=20
ret_from_fork+0x27/0x50
2019-08-03T18:51:32.787913+08:00 MGDT-ROG kernel: [11828.777125] ---[ end t=
race
9aaf1f62ae398b4b ]---
2019-08-03T18:51:37.791882+08:00 MGDT-ROG kernel: [11833.780084]
[drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5s=
ecs
aborting
2019-08-03T18:51:37.791896+08:00 MGDT-ROG kernel: [11833.780129]
[drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck
executing B0B0 (len 2971, WS 4, PS 0) @ 0xB963
2019-08-03T18:51:37.791898+08:00 MGDT-ROG kernel: [11833.780172]
[drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck
executing AFB0 (len 255, WS 4, PS 0) @ 0xB089
2019-08-03T18:51:37.791899+08:00 MGDT-ROG kernel: [11833.780240]
[drm:dce110_link_encoder_disable_output [amdgpu]] *ERROR*
dce110_link_encoder_disable_output: Failed to execute VBIOS command table!
2019-08-03T18:51:37.791901+08:00 MGDT-ROG kernel: [11833.780240] ----------=
--[
cut here ]------------
2019-08-03T18:51:37.791902+08:00 MGDT-ROG kernel: [11833.780328] WARNING: C=
PU:
1 PID: 10195 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dce_link_encoder.c:1096
dce110_link_encoder_disable_output+0x13d/0x150 [amdgpu]
2019-08-03T18:51:37.791903+08:00 MGDT-ROG kernel: [11833.780329] Modules li=
nked
in: tun fuse af_packet ebtable_filter ebtables ip6table_filter ip6_tables
iptable_filter ip_tables x_tables bpfilter uvcvideo videobuf2_vmalloc
videobuf2_memops videobuf2_v4l2 snd_usb_audio videobuf2_common snd_usbmidi_=
lib
videodev snd_rawmidi snd_seq_device media joydev scsi_transport_iscsi msr
nls_iso8859_1 nls_cp437 vfat fat edac_mce_amd kvm_amd kvm irqbypass
snd_hda_codec_realtek crct10dif_pclmul snd_hda_codec_generic crc32_pclmul
ledtrig_audio snd_hda_codec_hdmi ghash_clmulni_intel snd_hda_intel
snd_hda_codec snd_hda_core snd_hwdep aesni_intel eeepc_wmi asus_wmi aes_x86=
_64
sparse_keymap snd_pcm crypto_simd rfkill cryptd video glue_helper wmi_bmof
mxm_wmi igb snd_timer sp5100_tco snd ptp pcspkr i2c_piix4 pps_core dca k10t=
emp
ccp soundcore gpio_amdpt gpio_generic pcc_cpufreq button acpi_cpufreq btrfs
libcrc32c xor hid_generic usbhid amdgpu raid6_pq amd_iommu_v2 gpu_sched
i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fo=
ps
xhci_pci drm
2019-08-03T18:51:37.791905+08:00 MGDT-ROG kernel: [11833.780356]  crc32c_in=
tel
xhci_hcd usbcore sr_mod cdrom wmi pinctrl_amd l2tp_ppp l2tp_netlink l2tp_co=
re
ip6_udp_tunnel udp_tunnel pppox ppp_generic slhc sg dm_multipath dm_mod
scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs
2019-08-03T18:51:37.791907+08:00 MGDT-ROG kernel: [11833.780365] CPU: 1 PID:
10195 Comm: kworker/1:0 Tainted: G        W         5.2.3-1-default #1 open=
SUSE
Tumbleweed (unreleased)
2019-08-03T18:51:37.791908+08:00 MGDT-ROG kernel: [11833.780366] Hardware n=
ame:
System manufacturer System Product Name/ROG STRIX X470-F GAMING, BIOS 5007
06/17/2019
2019-08-03T18:51:37.791910+08:00 MGDT-ROG kernel: [11833.780370] Workqueue:
events drm_sched_job_timedout [gpu_sched]
2019-08-03T18:51:37.791911+08:00 MGDT-ROG kernel: [11833.780435] RIP:
0010:dce110_link_encoder_disable_output+0x13d/0x150 [amdgpu]
2019-08-03T18:51:37.791912+08:00 MGDT-ROG kernel: [11833.780437] Code: ff f=
f 48
83 c4 38 5b 5d 41 5c c3 48 c7 c6 c0 c8 6f c0 48 c7 c7 d8 d9 74 c0 e8 cf bb =
de
ff 48 c7 c7 70 d9 74 c0 e8 61 13 8c f4 <0f> 0b eb d4 66 66 2e 0f 1f 8=
4 00 00 00
00 00 0f 1f 40 00 0f 1f 44
2019-08-03T18:51:37.791913+08:00 MGDT-ROG kernel: [11833.780438] RSP:
0018:ffffab7acdeb77f8 EFLAGS: 00010282
2019-08-03T18:51:37.791914+08:00 MGDT-ROG kernel: [11833.780439] RAX:
0000000000000024 RBX: ffff960e96034a80 RCX: 0000000000000006
2019-08-03T18:51:37.791915+08:00 MGDT-ROG kernel: [11833.780440] RDX:
0000000000000007 RSI: 0000000000000096 RDI: ffff960e9e659a10
2019-08-03T18:51:37.791917+08:00 MGDT-ROG kernel: [11833.780441] RBP:
0000000000000020 R08: 0000000000000518 R09: 0000000000000001
2019-08-03T18:51:37.791918+08:00 MGDT-ROG kernel: [11833.780441] R10:
0000000000000000 R11: 0000000000000001 R12: ffffab7acdeb77fc
2019-08-03T18:51:37.791919+08:00 MGDT-ROG kernel: [11833.780442] R13:
ffff95ffc13c1000 R14: 0000000000000000 R15: ffff9601c92c8188
2019-08-03T18:51:37.791920+08:00 MGDT-ROG kernel: [11833.780443] FS:=20
0000000000000000(0000) GS:ffff960e9e640000(0000) knlGS:0000000000000000
2019-08-03T18:51:37.791921+08:00 MGDT-ROG kernel: [11833.780444] CS:  0010 =
DS:
0000 ES: 0000 CR0: 0000000080050033
2019-08-03T18:51:37.791922+08:00 MGDT-ROG kernel: [11833.780445] CR2:
000055d4170da000 CR3: 0000000f03cd6000 CR4: 00000000003406e0
2019-08-03T18:51:37.791923+08:00 MGDT-ROG kernel: [11833.780446] Call Trace:
2019-08-03T18:51:37.791924+08:00 MGDT-ROG kernel: [11833.780512]=20
dp_disable_link_phy+0x73/0x110 [amdgpu]
2019-08-03T18:51:37.791925+08:00 MGDT-ROG kernel: [11833.780576]=20
core_link_disable_stream+0xb6/0x260 [amdgpu]
2019-08-03T18:51:37.791926+08:00 MGDT-ROG kernel: [11833.780580]  ?
printk+0x48/0x4a
2019-08-03T18:51:37.791927+08:00 MGDT-ROG kernel: [11833.780642]=20
dce110_reset_hw_ctx_wrap+0xc1/0x1e0 [amdgpu]
2019-08-03T18:51:37.791928+08:00 MGDT-ROG kernel: [11833.780716]  ?
vega20_dpm_force_dpm_level.cold+0x5b/0x90 [amdgpu]
2019-08-03T18:51:37.791929+08:00 MGDT-ROG kernel: [11833.780779]=20
dce110_apply_ctx_to_hw+0x3a/0x470 [amdgpu]
2019-08-03T18:51:37.791930+08:00 MGDT-ROG kernel: [11833.780840]  ?
hwmgr_handle_task+0x66/0xc0 [amdgpu]
2019-08-03T18:51:37.791931+08:00 MGDT-ROG kernel: [11833.780843]  ?
mutex_lock+0xe/0x30
2019-08-03T18:51:37.791933+08:00 MGDT-ROG kernel: [11833.780905]  ?
pp_dpm_dispatch_tasks+0x45/0x60 [amdgpu]
2019-08-03T18:51:37.791934+08:00 MGDT-ROG kernel: [11833.780969]  ?
dm_pp_apply_display_requirements+0x1a1/0x1c0 [amdgpu]
2019-08-03T18:51:37.791935+08:00 MGDT-ROG kernel: [11833.781032]=20
dc_commit_state_no_check+0x200/0x530 [amdgpu]
2019-08-03T18:51:37.791936+08:00 MGDT-ROG kernel: [11833.781036]  ?
get_page_from_freelist+0x289/0x380
2019-08-03T18:51:37.791937+08:00 MGDT-ROG kernel: [11833.781098]=20
dc_commit_state+0x8f/0xb0 [amdgpu]
2019-08-03T18:51:37.791938+08:00 MGDT-ROG kernel: [11833.781162]=20
amdgpu_dm_atomic_commit_tail+0x3a6/0xd30 [amdgpu]
2019-08-03T18:51:37.791939+08:00 MGDT-ROG kernel: [11833.781227]  ?
bw_calcs+0x8ac/0x1440 [amdgpu]
2019-08-03T18:51:37.791940+08:00 MGDT-ROG kernel: [11833.781229]  ?
__ww_mutex_lock.isra.0+0x2a/0x780
2019-08-03T18:51:37.791941+08:00 MGDT-ROG kernel: [11833.781231]  ?
_raw_spin_unlock_irqrestore+0x24/0x40
2019-08-03T18:51:37.791942+08:00 MGDT-ROG kernel: [11833.781234]  ?
__wake_up_common_lock+0x7c/0xa0
2019-08-03T18:51:37.791943+08:00 MGDT-ROG kernel: [11833.781236]  ?
wait_for_completion_timeout+0xf3/0x110
2019-08-03T18:51:37.791944+08:00 MGDT-ROG kernel: [11833.781237]  ?
wait_for_completion_interruptible+0x10b/0x150
2019-08-03T18:51:37.791945+08:00 MGDT-ROG kernel: [11833.781245]  ?
commit_tail+0x3c/0x70 [drm_kms_helper]
2019-08-03T18:51:37.791946+08:00 MGDT-ROG kernel: [11833.781251]=20
commit_tail+0x3c/0x70 [drm_kms_helper]
2019-08-03T18:51:37.791947+08:00 MGDT-ROG kernel: [11833.781258]=20
drm_atomic_helper_commit+0x108/0x110 [drm_kms_helper]
2019-08-03T18:51:37.791948+08:00 MGDT-ROG kernel: [11833.781265]=20
drm_atomic_helper_disable_all+0x144/0x160 [drm_kms_helper]
2019-08-03T18:51:37.791949+08:00 MGDT-ROG kernel: [11833.781272]=20
drm_atomic_helper_suspend+0x4c/0xe0 [drm_kms_helper]
2019-08-03T18:51:37.791950+08:00 MGDT-ROG kernel: [11833.781335]=20
dm_suspend+0x20/0x60 [amdgpu]
2019-08-03T18:51:37.791951+08:00 MGDT-ROG kernel: [11833.781377]=20
amdgpu_device_ip_suspend_phase1+0x8b/0xc0 [amdgpu]
2019-08-03T18:51:37.791952+08:00 MGDT-ROG kernel: [11833.781418]=20
amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu]
2019-08-03T18:51:37.791953+08:00 MGDT-ROG kernel: [11833.781490]=20
amdgpu_device_pre_asic_reset+0x1f4/0x209 [amdgpu]
2019-08-03T18:51:37.791954+08:00 MGDT-ROG kernel: [11833.781561]=20
amdgpu_device_gpu_recover+0x67/0x765 [amdgpu]
2019-08-03T18:51:37.791955+08:00 MGDT-ROG kernel: [11833.781620]=20
amdgpu_job_timedout+0xf7/0x120 [amdgpu]
2019-08-03T18:51:37.791956+08:00 MGDT-ROG kernel: [11833.781624]=20
drm_sched_job_timedout+0x3a/0x70 [gpu_sched]
2019-08-03T18:51:37.791957+08:00 MGDT-ROG kernel: [11833.781627]=20
process_one_work+0x1df/0x3c0
2019-08-03T18:51:37.791958+08:00 MGDT-ROG kernel: [11833.781629]=20
worker_thread+0x4d/0x400
2019-08-03T18:51:37.791959+08:00 MGDT-ROG kernel: [11833.781631]=20
kthread+0xf9/0x130
2019-08-03T18:51:37.791960+08:00 MGDT-ROG kernel: [11833.781633]  ?
process_one_work+0x3c0/0x3c0
2019-08-03T18:51:37.791961+08:00 MGDT-ROG kernel: [11833.781634]  ?
kthread_park+0x80/0x80
2019-08-03T18:51:37.791962+08:00 MGDT-ROG kernel: [11833.781636]=20
ret_from_fork+0x27/0x50
2019-08-03T18:51:37.791963+08:00 MGDT-ROG kernel: [11833.781639] ---[ end t=
race
9aaf1f62ae398b4c ]---
2019-08-03T18:51:42.796019+08:00 MGDT-ROG kernel: [11838.784083]
[drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5s=
ecs
aborting
2019-08-03T18:51:42.796034+08:00 MGDT-ROG kernel: [11838.784127]
[drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck
executing A048 (len 62, WS 0, PS 0) @ 0xA064
2019-08-03T18:51:42.796035+08:00 MGDT-ROG kernel: [11838.784208] amdgpu:
[powerplay] Failed to send message 0x28, response 0xffffffff
2019-08-03T18:51:42.796036+08:00 MGDT-ROG kernel: [11838.784219] amdgpu:
[powerplay] Failed to send message 0x28, response 0xffffffff
2019-08-03T18:51:42.796038+08:00 MGDT-ROG kernel: [11838.784233] amdgpu:
[powerplay] Failed to send message 0x47, response 0xffffffff
2019-08-03T18:51:42.796039+08:00 MGDT-ROG kernel: [11838.784245] amdgpu:
[powerplay] Failed to send message 0x28, response 0xffffffff
2019-08-03T18:51:42.796040+08:00 MGDT-ROG kernel: [11838.784245] amdgpu:
[powerplay] [SetUclkToHightestDpmLevel] Set hard min uclk failed!
2019-08-03T18:51:42.796041+08:00 MGDT-ROG kernel: [11838.784258] amdgpu:
[powerplay] Failed to send message 0x28, response 0xffffffff
2019-08-03T18:51:42.796042+08:00 MGDT-ROG kernel: [11838.784258] amdgpu:
[powerplay] Attempt to set Hard Min for DCEFCLK Failed!
2019-08-03T18:51:42.796044+08:00 MGDT-ROG kernel: [11838.784269] amdgpu:
[powerplay] Failed to send message 0x28, response 0xffffffff
2019-08-03T18:51:42.796045+08:00 MGDT-ROG kernel: [11838.784270] amdgpu:
[powerplay] [SetHardMinFreq] Set hard min uclk failed!
2019-08-03T18:51:42.796046+08:00 MGDT-ROG kernel: [11838.784281] amdgpu:
[powerplay] Failed to send message 0x26, response 0xffffffff
2019-08-03T18:51:42.796047+08:00 MGDT-ROG kernel: [11838.784282] amdgpu:
[powerplay] Failed to set soft min gfxclk !
2019-08-03T18:51:42.796048+08:00 MGDT-ROG kernel: [11838.784282] amdgpu:
[powerplay] Failed to upload DPM Bootup Levels!
2019-08-03T18:51:43.656061+08:00 MGDT-ROG kernel: [11839.645436] amdgpu:
[powerplay] Failed to send message 0x26, response 0xffffffff
2019-08-03T18:51:43.656078+08:00 MGDT-ROG kernel: [11839.645438] amdgpu:
[powerplay] Failed to set soft min gfxclk !
2019-08-03T18:51:43.656080+08:00 MGDT-ROG kernel: [11839.645438] amdgpu:
[powerplay] Failed to upload DPM Bootup Levels!
2019-08-03T18:51:43.656081+08:00 MGDT-ROG kernel: [11839.645449] amdgpu:
[powerplay] Failed to send message 0x7, response 0xffffffff
2019-08-03T18:51:43.656082+08:00 MGDT-ROG kernel: [11839.645450] amdgpu:
[powerplay] [DisableAllSMUFeatures] Failed to disable all smu features!
2019-08-03T18:51:43.656083+08:00 MGDT-ROG kernel: [11839.645450] amdgpu:
[powerplay] [DisableDpmTasks] Failed to disable all smu features!
2019-08-03T18:51:43.656084+08:00 MGDT-ROG kernel: [11839.645451] amdgpu:
[powerplay] [PowerOffAsic] Failed to disable DPM!
2019-08-03T18:51:43.656086+08:00 MGDT-ROG kernel: [11839.645497]
[drm:amdgpu_device_ip_suspend_phase2 [amdgpu]] *ERROR* suspend of IP block
<powerplay> failed -5
2019-08-03T18:51:43.911990+08:00 MGDT-ROG kernel: [11839.902893] amdgpu
0000:0a:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0
test failed (-110)
2019-08-03T18:51:43.912001+08:00 MGDT-ROG kernel: [11839.902947]
[drm:gfx_v9_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed
2019-08-03T18:51:44.167806+08:00 MGDT-ROG kernel: [11840.159797] [drm] Time=
out
wait for RLC serdes 0,0
2019-08-03T18:51:44.191826+08:00 MGDT-ROG kernel: [11840.180793] amdgpu
0000:0a:00.0: GPU mode1 reset
2019-08-03T18:51:44.451982+08:00 MGDT-ROG kernel: [11840.442308] [drm] psp =
is
not working correctly before mode1 reset!
2019-08-03T18:51:44.451993+08:00 MGDT-ROG kernel: [11840.442310] amdgpu
0000:0a:00.0: GPU mode1 reset failed
2019-08-03T18:51:44.719056+08:00 MGDT-ROG kernel: [11840.710967]
[drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* ASIC reset failed with err=
or,
-22 for drm dev, 0000:0a:00.0
2019-08-03T18:51:44.719066+08:00 MGDT-ROG kernel: [11840.711014] amdgpu
0000:0a:00.0: GPU reset(1) failed
2019-08-03T18:51:44.719068+08:00 MGDT-ROG kernel: [11840.711033] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719068+08:00 MGDT-ROG kernel: [11840.711038] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719070+08:00 MGDT-ROG kernel: [11840.711040] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719071+08:00 MGDT-ROG kernel: [11840.711043] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719072+08:00 MGDT-ROG kernel: [11840.711045] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719073+08:00 MGDT-ROG kernel: [11840.711049] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719075+08:00 MGDT-ROG kernel: [11840.711051] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719076+08:00 MGDT-ROG kernel: [11840.711053] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719077+08:00 MGDT-ROG kernel: [11840.711057] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719078+08:00 MGDT-ROG kernel: [11840.711059] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719079+08:00 MGDT-ROG kernel: [11840.711061] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719080+08:00 MGDT-ROG kernel: [11840.711064] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719081+08:00 MGDT-ROG kernel: [11840.711066] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719082+08:00 MGDT-ROG kernel: [11840.711068] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719083+08:00 MGDT-ROG kernel: [11840.711072] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719084+08:00 MGDT-ROG kernel: [11840.711075] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719085+08:00 MGDT-ROG kernel: [11840.711077] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719086+08:00 MGDT-ROG kernel: [11840.711080] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719087+08:00 MGDT-ROG kernel: [11840.711083] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719088+08:00 MGDT-ROG kernel: [11840.711085] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719089+08:00 MGDT-ROG kernel: [11840.711087] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719090+08:00 MGDT-ROG kernel: [11840.711090] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719091+08:00 MGDT-ROG kernel: [11840.711092] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719092+08:00 MGDT-ROG kernel: [11840.711094] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719093+08:00 MGDT-ROG kernel: [11840.711096] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719094+08:00 MGDT-ROG kernel: [11840.711097] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719095+08:00 MGDT-ROG kernel: [11840.711100] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719096+08:00 MGDT-ROG kernel: [11840.711102] amdgpu
0000:0a:00.0: GPU reset end with ret =3D -22
2019-08-03T18:51:44.719097+08:00 MGDT-ROG kernel: [11840.711102] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719098+08:00 MGDT-ROG kernel: [11840.711104] [drm] Skip
scheduling IBs!
2019-08-03T18:51:44.719099+08:00 MGDT-ROG kernel: [11840.711106] [drm] Skip
scheduling IBs!
2019-08-03T18:51:54.767980+08:00 MGDT-ROG kernel: [11850.756186]
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled
seq=3D2324986, emitted seq=3D2324986
2019-08-03T18:51:54.767994+08:00 MGDT-ROG kernel: [11850.756247]
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process X p=
id
2132 thread X:cs0 pid 2139
2019-08-03T18:51:54.767996+08:00 MGDT-ROG kernel: [11850.756251] amdgpu
0000:0a:00.0: GPU reset begin!

You are receiving this mail because:
  • You are the assignee for the bug.
= --15648393552.c39C0F3Ed.28674-- --===============0210398302== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0210398302==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 03 Aug 2019 16:54:17 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0430358991==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 605336E0CC for ; Sat, 3 Aug 2019 16:54:17 +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 --===============0430358991== Content-Type: multipart/alternative; boundary="15648512574.b9DD.29337" Content-Transfer-Encoding: 7bit --15648512574.b9DD.29337 Date: Sat, 3 Aug 2019 16:54:17 +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=3D109955 --- Comment #73 from Sylvain BERTRAND --- On Sat, Aug 03, 2019 at 01:35:55PM +0000, bugzilla-daemon@freedesktop.org wrote: > [ 5.759204] amdgpu 0000:0a:00.0: Direct firmware load for > amdgpu/vega20_ta.bin failed with error -2 > [ 5.759205] amdgpu 0000:0a:00.0: psp v11.0: Failed to load firmware > "amdgpu/vega20_ta.bin" Did you get the latest and "greatest" amdgpu firmware package? --=20 You are receiving this mail because: You are the assignee for the bug.= --15648512574.b9DD.29337 Date: Sat, 3 Aug 2019 16:54:17 +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

Comme= nt # 73 on bug 10995= 5 from Sylvain BERTRAND 
On Sat, Aug 03, 2019 at 01:35:55PM +0000, bugzilla-daemon@freedesktop.org
wrote:
> [    5.759204] amdgpu 0000:0a:00.0: Direct firmw=
are load for
> amdgpu/vega20_ta.bin failed with error -2
> [    5.759205] amdgpu 0000:0a:00.0: psp v11.0: Failed to load firmware
> "amdgpu/vega20_ta.bin"

Did you get the latest and "greatest" amdgpu firmware package?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15648512574.b9DD.29337-- --===============0430358991== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0430358991==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 03 Aug 2019 17:43:01 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0144541758==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 3D00A6E2CF for ; Sat, 3 Aug 2019 17:43:01 +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 --===============0144541758== Content-Type: multipart/alternative; boundary="15648541813.e0cEE2e.5243" Content-Transfer-Encoding: 7bit --15648541813.e0cEE2e.5243 Date: Sat, 3 Aug 2019 17:43:01 +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=3D109955 --- Comment #74 from Mauro Gaspari --- (In reply to Sylvain BERTRAND from comment #73) > On Sat, Aug 03, 2019 at 01:35:55PM +0000, bugzilla-daemon@freedesktop.org > wrote: > > [ 5.759204] amdgpu 0000:0a:00.0: Direct firmware load for > > amdgpu/vega20_ta.bin failed with error -2 > > [ 5.759205] amdgpu 0000:0a:00.0: psp v11.0: Failed to load firmware > > "amdgpu/vega20_ta.bin" >=20 > Did you get the latest and "greatest" amdgpu firmware package? This is a fresh install I made to test this issue, so for now I only instal= led the packages per openSUSE wiki: https://en.opensuse.org/SDB:AMDGPU I have done a snapper btrfs snapshot therefore if there is anything you wan= t me to test, I am ready. --=20 You are receiving this mail because: You are the assignee for the bug.= --15648541813.e0cEE2e.5243 Date: Sat, 3 Aug 2019 17:43:01 +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

Comme= nt # 74 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Sylvain BERTRAND from comment #73)
> On Sat, Aug 03, 2019 at 01:35:55PM +0000, bugzilla-daemon@freede=
sktop.org
> wrote:
> > [    5.759204] amdgpu 0000:0a:00.0: Direct firmware load for
> > amdgpu/vega20_ta.bin failed with error -2
> > [    5.759205] amdgpu 0000:0a:00.0: psp v11.0: Failed to load fir=
mware
> > "amdgpu/vega20_ta.bin"
>=20
> Did you get the latest and "greatest" amdgpu firmware packag=
e?

This is a fresh install I made to test this issue, so for now I only instal=
led
the packages per openSUSE wiki: https://en.opensuse.org/SDB:AMDGPU

I have done a snapper btrfs snapshot therefore if there is anything you wan=
t me
to test, I am ready.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15648541813.e0cEE2e.5243-- --===============0144541758== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0144541758==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 03 Aug 2019 18:46:19 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0311358388==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 41FF76E16D for ; Sat, 3 Aug 2019 18:46:19 +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 --===============0311358388== Content-Type: multipart/alternative; boundary="15648579791.d3ECf39.17536" Content-Transfer-Encoding: 7bit --15648579791.d3ECf39.17536 Date: Sat, 3 Aug 2019 18:46:19 +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=3D109955 --- Comment #75 from Sylvain BERTRAND --- On Sat, Aug 03, 2019 at 05:43:01PM +0000, bugzilla-daemon@freedesktop.org wrote: > > > [ 5.759204] amdgpu 0000:0a:00.0: Direct firmware load for > > > amdgpu/vega20_ta.bin failed with error -2 > > > [ 5.759205] amdgpu 0000:0a:00.0: psp v11.0: Failed to load firmware > > > "amdgpu/vega20_ta.bin" It seems you have a corrupted/old/missing vega20_ta.bin firmware file. It looks like outdated distro files. --=20 You are receiving this mail because: You are the assignee for the bug.= --15648579791.d3ECf39.17536 Date: Sat, 3 Aug 2019 18:46:19 +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

Comme= nt # 75 on bug 10995= 5 from Sylvain BERTRAND 
On Sat, Aug 03, 2019 at 05:43:01PM +0000, bugzilla-daemon@freedesktop.org
wrote:
> > > [    5.759204] amdgpu 0000:0a:00.0: Di=
rect firmware load for
> > > amdgpu/vega20_ta.bin failed with error -2
> > > [    5.759205] amdgpu 0000:0a:00.0: psp v11.0: Failed to loa=
d firmware
> > > "amdgpu/vega20_ta.bin"

It seems you have a corrupted/old/missing vega20_ta.bin firmware file.
It looks like outdated distro files.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15648579791.d3ECf39.17536-- --===============0311358388== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0311358388==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 04 Aug 2019 05:05:52 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1830816441==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 315CC6E1D8 for ; Sun, 4 Aug 2019 05:05:52 +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 --===============1830816441== Content-Type: multipart/alternative; boundary="15648951522.021e.13847" Content-Transfer-Encoding: 7bit --15648951522.021e.13847 Date: Sun, 4 Aug 2019 05:05:52 +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=3D109955 --- Comment #76 from Mauro Gaspari --- (In reply to Sylvain BERTRAND from comment #75) > On Sat, Aug 03, 2019 at 05:43:01PM +0000, bugzilla-daemon@freedesktop.org > wrote: > > > > [ 5.759204] amdgpu 0000:0a:00.0: Direct firmware load for > > > > amdgpu/vega20_ta.bin failed with error -2 > > > > [ 5.759205] amdgpu 0000:0a:00.0: psp v11.0: Failed to load firmw= are > > > > "amdgpu/vega20_ta.bin" >=20 > It seems you have a corrupted/old/missing vega20_ta.bin firmware file. > It looks like outdated distro files. Hello, I did some quick search online and it seems a common problem for many users amdgpu. And looking around on other reports they seem to be dismissed as warnings and not mandatory. I am not an expert and I do not want to dismis= s it here, just report what I see. By the way, Interesting to see that even my ubuntu budgie LTS with valve mesa-aco and different kernel, has the same warning. [ 5.435346] [drm] amdgpu kernel modesetting enabled. [ 5.435500] fb0: switching to amdgpudrmfb from EFI VGA [ 5.735058] amdgpu 0000:0a:00.0: No more image in the PCI ROM [ 5.735102] amdgpu 0000:0a:00.0: VRAM: 16368M 0x0000008000000000 - 0x00000083FEFFFFFF (16368M used) [ 5.735103] amdgpu 0000:0a:00.0: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF [ 5.735104] amdgpu 0000:0a:00.0: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF [ 5.735185] [drm] amdgpu: 16368M of VRAM memory ready [ 5.735186] [drm] amdgpu: 16368M of GTT memory ready. [ 5.739656] amdgpu 0000:0a:00.0: Direct firmware load for amdgpu/vega20_ta.bin failed with error -2 [ 5.739659] amdgpu 0000:0a:00.0: psp v11.0: Failed to load firmware "amdgpu/vega20_ta.bin" [ 6.354308] fbcon: amdgpudrmfb (fb0) is primary device [ 6.354490] amdgpu 0000:0a:00.0: fb0: amdgpudrmfb frame buffer device [ 6.384079] amdgpu 0000:0a:00.0: ring gfx uses VM inv eng 0 on hub 0 [ 6.384080] amdgpu 0000:0a:00.0: ring comp_1.0.0 uses VM inv eng 1 on hu= b 0 [ 6.384081] amdgpu 0000:0a:00.0: ring comp_1.1.0 uses VM inv eng 4 on hu= b 0 [ 6.384082] amdgpu 0000:0a:00.0: ring comp_1.2.0 uses VM inv eng 5 on hu= b 0 [ 6.384083] amdgpu 0000:0a:00.0: ring comp_1.3.0 uses VM inv eng 6 on hu= b 0 [ 6.384084] amdgpu 0000:0a:00.0: ring comp_1.0.1 uses VM inv eng 7 on hu= b 0 [ 6.384084] amdgpu 0000:0a:00.0: ring comp_1.1.1 uses VM inv eng 8 on hu= b 0 [ 6.384085] amdgpu 0000:0a:00.0: ring comp_1.2.1 uses VM inv eng 9 on hu= b 0 [ 6.384086] amdgpu 0000:0a:00.0: ring comp_1.3.1 uses VM inv eng 10 on h= ub 0 [ 6.384087] amdgpu 0000:0a:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hu= b 0 [ 6.384088] amdgpu 0000:0a:00.0: ring sdma0 uses VM inv eng 0 on hub 1 [ 6.384089] amdgpu 0000:0a:00.0: ring page0 uses VM inv eng 1 on hub 1 [ 6.384089] amdgpu 0000:0a:00.0: ring sdma1 uses VM inv eng 4 on hub 1 [ 6.384090] amdgpu 0000:0a:00.0: ring page1 uses VM inv eng 5 on hub 1 [ 6.384090] amdgpu 0000:0a:00.0: ring uvd_0 uses VM inv eng 6 on hub 1 [ 6.384091] amdgpu 0000:0a:00.0: ring uvd_enc_0.0 uses VM inv eng 7 on h= ub 1 [ 6.384092] amdgpu 0000:0a:00.0: ring uvd_enc_0.1 uses VM inv eng 8 on h= ub 1 [ 6.384092] amdgpu 0000:0a:00.0: ring uvd_1 uses VM inv eng 9 on hub 1 [ 6.384093] amdgpu 0000:0a:00.0: ring uvd_enc_1.0 uses VM inv eng 10 on = hub 1 [ 6.384094] amdgpu 0000:0a:00.0: ring uvd_enc_1.1 uses VM inv eng 11 on = hub 1 [ 6.384094] amdgpu 0000:0a:00.0: ring vce0 uses VM inv eng 12 on hub 1 [ 6.384095] amdgpu 0000:0a:00.0: ring vce1 uses VM inv eng 13 on hub 1 [ 6.384096] amdgpu 0000:0a:00.0: ring vce2 uses VM inv eng 14 on hub 1 [ 7.067068] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:0a:00.0 on minor 0 --=20 You are receiving this mail because: You are the assignee for the bug.= --15648951522.021e.13847 Date: Sun, 4 Aug 2019 05:05:52 +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

Comme= nt # 76 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Sylvain BERTRAND from comment #75)
> On Sat, Aug 03, 2019 at 05:43:01PM +0000, bugzilla-daemon@freede=
sktop.org
> wrote:
> > > > [    5.759204] amdgpu 0000:0a:00.0: Direct firmware loa=
d for
> > > > amdgpu/vega20_ta.bin failed with error -2
> > > > [    5.759205] amdgpu 0000:0a:00.0: psp v11.0: Failed t=
o load firmware
> > > > "amdgpu/vega20_ta.bin"
>=20
> It seems you have a corrupted/old/missing vega20_ta.bin firmware file.
> It looks like outdated distro files.

Hello,
I did some quick search online and it seems a common problem for many users
amdgpu. And looking around on other reports they seem to be dismissed as
warnings and not mandatory. I am not an expert and I do not  want to dismis=
s it
here, just report what I see.

By the way, Interesting to see that even my ubuntu budgie LTS with valve
mesa-aco and different kernel, has the same warning.

[    5.435346] [drm] amdgpu kernel modesetting enabled.
[    5.435500] fb0: switching to amdgpudrmfb from EFI VGA
[    5.735058] amdgpu 0000:0a:00.0: No more image in the PCI ROM
[    5.735102] amdgpu 0000:0a:00.0: VRAM: 16368M 0x0000008000000000 -
0x00000083FEFFFFFF (16368M used)
[    5.735103] amdgpu 0000:0a:00.0: GART: 512M 0x0000000000000000 -
0x000000001FFFFFFF
[    5.735104] amdgpu 0000:0a:00.0: AGP: 267894784M 0x0000008400000000 -
0x0000FFFFFFFFFFFF
[    5.735185] [drm] amdgpu: 16368M of VRAM memory ready
[    5.735186] [drm] amdgpu: 16368M of GTT memory ready.
[    5.739656] amdgpu 0000:0a:00.0: Direct firmware load for
amdgpu/vega20_ta.bin failed with error -2
[    5.739659] amdgpu 0000:0a:00.0: psp v11.0: Failed to load firmware
"amdgpu/vega20_ta.bin"
[    6.354308] fbcon: amdgpudrmfb (fb0) is primary device
[    6.354490] amdgpu 0000:0a:00.0: fb0: amdgpudrmfb frame buffer device
[    6.384079] amdgpu 0000:0a:00.0: ring gfx uses VM inv eng 0 on hub 0
[    6.384080] amdgpu 0000:0a:00.0: ring comp_1.0.0 uses VM inv eng 1 on hu=
b 0
[    6.384081] amdgpu 0000:0a:00.0: ring comp_1.1.0 uses VM inv eng 4 on hu=
b 0
[    6.384082] amdgpu 0000:0a:00.0: ring comp_1.2.0 uses VM inv eng 5 on hu=
b 0
[    6.384083] amdgpu 0000:0a:00.0: ring comp_1.3.0 uses VM inv eng 6 on hu=
b 0
[    6.384084] amdgpu 0000:0a:00.0: ring comp_1.0.1 uses VM inv eng 7 on hu=
b 0
[    6.384084] amdgpu 0000:0a:00.0: ring comp_1.1.1 uses VM inv eng 8 on hu=
b 0
[    6.384085] amdgpu 0000:0a:00.0: ring comp_1.2.1 uses VM inv eng 9 on hu=
b 0
[    6.384086] amdgpu 0000:0a:00.0: ring comp_1.3.1 uses VM inv eng 10 on h=
ub 0
[    6.384087] amdgpu 0000:0a:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hu=
b 0
[    6.384088] amdgpu 0000:0a:00.0: ring sdma0 uses VM inv eng 0 on hub 1
[    6.384089] amdgpu 0000:0a:00.0: ring page0 uses VM inv eng 1 on hub 1
[    6.384089] amdgpu 0000:0a:00.0: ring sdma1 uses VM inv eng 4 on hub 1
[    6.384090] amdgpu 0000:0a:00.0: ring page1 uses VM inv eng 5 on hub 1
[    6.384090] amdgpu 0000:0a:00.0: ring uvd_0 uses VM inv eng 6 on hub 1
[    6.384091] amdgpu 0000:0a:00.0: ring uvd_enc_0.0 uses VM inv eng 7 on h=
ub 1
[    6.384092] amdgpu 0000:0a:00.0: ring uvd_enc_0.1 uses VM inv eng 8 on h=
ub 1
[    6.384092] amdgpu 0000:0a:00.0: ring uvd_1 uses VM inv eng 9 on hub 1
[    6.384093] amdgpu 0000:0a:00.0: ring uvd_enc_1.0 uses VM inv eng 10 on =
hub
1
[    6.384094] amdgpu 0000:0a:00.0: ring uvd_enc_1.1 uses VM inv eng 11 on =
hub
1
[    6.384094] amdgpu 0000:0a:00.0: ring vce0 uses VM inv eng 12 on hub 1
[    6.384095] amdgpu 0000:0a:00.0: ring vce1 uses VM inv eng 13 on hub 1
[    6.384096] amdgpu 0000:0a:00.0: ring vce2 uses VM inv eng 14 on hub 1
[    7.067068] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:0a:00.0 on
minor 0

You are receiving this mail because:
  • You are the assignee for the bug.
= --15648951522.021e.13847-- --===============1830816441== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1830816441==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 04 Aug 2019 14:18:56 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1568592800==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 3569F89DFD for ; Sun, 4 Aug 2019 14:18:56 +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 --===============1568592800== Content-Type: multipart/alternative; boundary="15649283362.727AE.3103" Content-Transfer-Encoding: 7bit --15649283362.727AE.3103 Date: Sun, 4 Aug 2019 14:18:56 +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=3D109955 --- Comment #77 from Sylvain BERTRAND --- On Sun, Aug 04, 2019 at 05:05:52AM +0000, bugzilla-daemon@freedesktop.org wrote: > By the way, Interesting to see that even my ubuntu budgie LTS with valve > mesa-aco and different kernel, has the same warning. > [ 5.739656] amdgpu 0000:0a:00.0: Direct firmware load for > amdgpu/vega20_ta.bin failed with error -2 > [ 5.739659] amdgpu 0000:0a:00.0: psp v11.0: Failed to load firmware > "amdgpu/vega20_ta.bin" I don't know of an AMD GPU part able to run without properly loaded firmwar= e. That would have to be confirmed by official AMD devs which are the sole ppl with that knowledge. In the very probable case that the firmware _must_ be loaded for proper gpu operations, you have to tell the maintainers of the distros you use to upda= te their linux/amdgpu firmware package. --=20 You are receiving this mail because: You are the assignee for the bug.= --15649283362.727AE.3103 Date: Sun, 4 Aug 2019 14:18:56 +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

Comme= nt # 77 on bug 10995= 5 from Sylvain BERTRAND 
On Sun, Aug 04, 2019 at 05:05:52AM +0000, bugzilla-daemon@freedesktop.org
wrote:
> By the way, Interesting to see that even my ubun=
tu budgie LTS with valve
> mesa-aco and different kernel, has the same warning.
> [    5.739656] amdgpu 0000:0a:00.0: Direct firmware load for
> amdgpu/vega20_ta.bin failed with error -2
> [    5.739659] amdgpu 0000:0a:00.0: psp v11.0: Failed to load firmware
> "amdgpu/vega20_ta.bin"

I don't know of an AMD GPU part able to run without properly loaded firmwar=
e.

That would have to be confirmed by official AMD devs which are the sole ppl
with that knowledge.

In the very probable case that the firmware _must_ be loaded for proper gpu
operations, you have to tell the maintainers of the distros you use to upda=
te
their linux/amdgpu firmware package.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15649283362.727AE.3103-- --===============1568592800== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1568592800==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 04 Aug 2019 16:17:41 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0896237778==" 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 8090489D67 for ; Sun, 4 Aug 2019 16:17:41 +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 --===============0896237778== Content-Type: multipart/alternative; boundary="15649354610.cA2Dfe.24365" Content-Transfer-Encoding: 7bit --15649354610.cA2Dfe.24365 Date: Sun, 4 Aug 2019 16:17:41 +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=3D109955 --- Comment #78 from Mauro Gaspari --- (In reply to Sylvain BERTRAND from comment #77) > On Sun, Aug 04, 2019 at 05:05:52AM +0000, bugzilla-daemon@freedesktop.org > wrote: > > By the way, Interesting to see that even my ubuntu budgie LTS with valve > > mesa-aco and different kernel, has the same warning. > > [ 5.739656] amdgpu 0000:0a:00.0: Direct firmware load for > > amdgpu/vega20_ta.bin failed with error -2 > > [ 5.739659] amdgpu 0000:0a:00.0: psp v11.0: Failed to load firmware > > "amdgpu/vega20_ta.bin" >=20 > I don't know of an AMD GPU part able to run without properly loaded firmw= are. >=20 > That would have to be confirmed by official AMD devs which are the sole p= pl > with that knowledge. >=20 > In the very probable case that the firmware _must_ be loaded for proper g= pu > operations, you have to tell the maintainers of the distros you use to up= date > their linux/amdgpu firmware package. I believe so, and yes it makes total sense that you need the correct firmwa= re for a piece of hardware to work properly.=20 I will open bugs for openSUSE and ubuntu, and ask the questions, point to t= his bug tracker. Let's see what comes out. I will report back as I hear from distribution maintainers.=20 I am using a RadeonVII at the moment. Is there anyone with a Vega64 or Vega= 56 that can do the same tests and let me know if they see same issue? I am hap= py to include those cards in my same bug reports if someone can confirm. --=20 You are receiving this mail because: You are the assignee for the bug.= --15649354610.cA2Dfe.24365 Date: Sun, 4 Aug 2019 16:17:41 +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

Comme= nt # 78 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Sylvain BERTRAND from comment #77)
> On Sun, Aug 04, 2019 at 05:05:52AM +0000, bugzilla-daemon@freede=
sktop.org
> wrote:
> > By the way, Interesting to see that even my ubuntu budgie LTS wit=
h valve
> > mesa-aco and different kernel, has the same warning.
> > [    5.739656] amdgpu 0000:0a:00.0: Direct firmware load for
> > amdgpu/vega20_ta.bin failed with error -2
> > [    5.739659] amdgpu 0000:0a:00.0: psp v11.0: Failed to load fir=
mware
> > "amdgpu/vega20_ta.bin"
>=20
> I don't know of an AMD GPU part able to run without properly loaded fi=
rmware.
>=20
> That would have to be confirmed by official AMD devs which are the sol=
e ppl
> with that knowledge.
>=20
> In the very probable case that the firmware _must_ be loaded for prope=
r gpu
> operations, you have to tell the maintainers of the distros you use to=
 update
> their linux/amdgpu firmware package.

I believe so, and yes it makes total sense that you need the correct firmwa=
re
for a piece of hardware to work properly.=20
I will open bugs for openSUSE and ubuntu, and ask the questions, point to t=
his
bug tracker. Let's see what comes out. I will report back as I hear from
distribution maintainers.=20

I am using a RadeonVII at the moment. Is there anyone with a Vega64 or Vega=
56
that can do the same tests and let me know if they see same issue? I am hap=
py
to include those cards in my same bug reports if someone can confirm.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15649354610.cA2Dfe.24365-- --===============0896237778== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0896237778==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 05 Aug 2019 05:54:44 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0286163062==" 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 8EF0489DB4 for ; Mon, 5 Aug 2019 05:54:44 +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 --===============0286163062== Content-Type: multipart/alternative; boundary="15649844846.ED9070.26124" Content-Transfer-Encoding: 7bit --15649844846.ED9070.26124 Date: Mon, 5 Aug 2019 05:54:44 +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=3D109955 --- Comment #79 from Alex Deucher --- the ta bin is optional. It's only used for server cards with xgmi and ras features. Consumer cards don't support those features and don't use it. --=20 You are receiving this mail because: You are the assignee for the bug.= --15649844846.ED9070.26124 Date: Mon, 5 Aug 2019 05:54:44 +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

Comme= nt # 79 on bug 10995= 5 from Alex Deucher 
the ta bin is optional.  It's only used for server cards with =
xgmi and ras
features.  Consumer cards don't support those features and don't use it.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15649844846.ED9070.26124-- --===============0286163062== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0286163062==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 05 Aug 2019 06:16:32 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1610398535==" 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 84CE26E02F for ; Mon, 5 Aug 2019 06:16:32 +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 --===============1610398535== Content-Type: multipart/alternative; boundary="15649857924.4D3a86664.30430" Content-Transfer-Encoding: 7bit --15649857924.4D3a86664.30430 Date: Mon, 5 Aug 2019 06:16:32 +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=3D109955 --- Comment #80 from Mauro Gaspari --- (In reply to Alex Deucher from comment #79) > the ta bin is optional. It's only used for server cards with xgmi and ras > features. Consumer cards don't support those features and don't use it. Alex, Thank you for confirming this. Good to know. Regarding the logs and dmesg I posted above, in comment #72, do you see anything useful? Is there any other specific tests I can do to help pinpoint the issue? --=20 You are receiving this mail because: You are the assignee for the bug.= --15649857924.4D3a86664.30430 Date: Mon, 5 Aug 2019 06:16:32 +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

Comme= nt # 80 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Alex Deucher from comment #79)
> the ta bin is optional.  It's only used for serv=
er cards with xgmi and ras
> features.  Consumer cards don't support those features and don't use i=
t.

Alex,
Thank you for confirming this. Good to know.
Regarding the logs and dmesg I posted above, in comment #72, do you see
anything useful? Is there any other specific tests I can do to help pinpoint
the issue?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15649857924.4D3a86664.30430-- --===============1610398535== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1610398535==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 07 Aug 2019 09:53:53 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0493414150==" 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 E94526E6A9 for ; Wed, 7 Aug 2019 09:53:53 +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 --===============0493414150== Content-Type: multipart/alternative; boundary="15651716334.65cF0.18646" Content-Transfer-Encoding: 7bit --15651716334.65cF0.18646 Date: Wed, 7 Aug 2019 09:53:53 +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=3D109955 --- Comment #81 from Pierre-Eric Pelloux-Prayer --- Can anyone provide a apitrace/renderdoc capture that can reliably reproduce= the crash/freeze? --=20 You are receiving this mail because: You are the assignee for the bug.= --15651716334.65cF0.18646 Date: Wed, 7 Aug 2019 09:53:53 +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

Comme= nt # 81 on bug 10995= 5 from Pierre= -Eric Pelloux-Prayer 
Can anyone provide a apitrace/renderdoc capture that can relia=
bly reproduce the
crash/freeze?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15651716334.65cF0.18646-- --===============0493414150== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0493414150==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 11 Aug 2019 09:31:41 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0361975128==" 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 67D2E6E31C for ; Sun, 11 Aug 2019 09:31:41 +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 --===============0361975128== Content-Type: multipart/alternative; boundary="15655159010.507eBC5.3171" Content-Transfer-Encoding: 7bit --15655159010.507eBC5.3171 Date: Sun, 11 Aug 2019 09:31:41 +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=3D109955 --- Comment #82 from Mauro Gaspari --- (In reply to Pierre-Eric Pelloux-Prayer from comment #81) > Can anyone provide a apitrace/renderdoc capture that can reliably reprodu= ce > the crash/freeze? Hello, Sadly my freezes are hard to reproduce. Sometimes I can play for a d= ay with no freeze, sometimes it freezes in 10 minutes, one hour, and so on. I had another freeze today: OS: openSUSE Tumbleweed x86_64=20 Kernel: 5.2.5-1-default Resolution: 3440x1440 DE: Xfce WM: Xfwm4 CPU: AMD Ryzen 7 2700X (16) @ 3.700GHz GPU: AMD ATI Radeon VII Memory: 3791MiB / 64387MiB=20 OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.3 Game: EVE Online: Wine+DXVK. (Crossover 18.5.0) vsync off frame limiter off Problem description: Afer rougly 1 hour of gameplay, desktop Frozen for a f= ew seconds but managed to recover. Game did not recover and I killed the proce= ss.=20 DMESG: [20612.721860] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D12880412, emitted seq=3D12880414 [20612.721921] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati= on: process exefile.exe pid 1980 thread exefile.ex:cs0 pid 2057 [20612.721925] amdgpu 0000:0a:00.0: GPU reset begin! [20613.526448] amdgpu 0000:0a:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) [20613.526502] [drm:gfx_v9_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed [20613.547524] amdgpu 0000:0a:00.0: GPU mode1 reset [20614.055810] [drm] psp mode1 reset succeed=20 [20614.128815] amdgpu 0000:0a:00.0: GPU reset succeeded, trying to resume [20614.128943] [drm] PCIE GART of 512M enabled (table at 0x0000008000300000= ). [20614.129304] [drm] PSP is resuming... [20614.192202] [drm] reserve 0x400000 from 0x8000c00000 for PSP TMR SIZE [20614.649220] [drm] UVD and UVD ENC initialized successfully. [20614.748872] [drm] VCE initialized successfully. [20615.271942] [drm] Fence fallback timer expired on ring gfx [20615.783826] [drm] Fence fallback timer expired on ring comp_1.0.0 [20616.616023] [drm] Fence fallback timer expired on ring uvd_1 [20617.127844] [drm] Fence fallback timer expired on ring uvd_enc_1.0 [20617.639836] [drm] Fence fallback timer expired on ring uvd_enc_1.1 [20617.739606] [drm] recover vram bo from shadow start [20617.742231] [drm] recover vram bo from shadow done [20617.742233] [drm] Skip scheduling IBs! [20617.742234] [drm] Skip scheduling IBs! [20617.742259] amdgpu 0000:0a:00.0: GPU reset(2) succeeded! [20617.742289] [drm] Skip scheduling IBs! [20617.742309] [drm] Skip scheduling IBs! [20617.742314] [drm] Skip scheduling IBs! [20617.742316] [drm] Skip scheduling IBs! [20617.742318] [drm] Skip scheduling IBs! [20617.742320] [drm] Skip scheduling IBs! [20617.743840] [drm] Skip scheduling IBs! [20617.744006] [drm] Skip scheduling IBs! [20617.744180] [drm] Skip scheduling IBs! [20617.744450] [drm] Skip scheduling IBs! System Logs: 2019-08-11T17:13:10.377029+08:00 MGDT-ROG kernel: [20612.721860] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D12880412, emitted seq=3D12880414 2019-08-11T17:13:10.377046+08:00 MGDT-ROG kernel: [20612.721921] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process exefile.exe pid 1980 thread exefile.ex:cs0 pid 2057 2019-08-11T17:13:10.377047+08:00 MGDT-ROG kernel: [20612.721925] amdgpu 0000:0a:00.0: GPU reset begin! 2019-08-11T17:13:11.182763+08:00 MGDT-ROG kernel: [20613.526448] amdgpu 0000:0a:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) 2019-08-11T17:13:11.182776+08:00 MGDT-ROG kernel: [20613.526502] [drm:gfx_v9_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed 2019-08-11T17:13:11.202766+08:00 MGDT-ROG kernel: [20613.547524] amdgpu 0000:0a:00.0: GPU mode1 reset 2019-08-11T17:13:11.714757+08:00 MGDT-ROG kernel: [20614.055810] [drm] psp mode1 reset succeed=20 2019-08-11T17:13:11.786740+08:00 MGDT-ROG kernel: [20614.128815] amdgpu 0000:0a:00.0: GPU reset succeeded, trying to resume 2019-08-11T17:13:11.786749+08:00 MGDT-ROG kernel: [20614.128943] [drm] PCIE GART of 512M enabled (table at 0x0000008000300000). 2019-08-11T17:13:11.786751+08:00 MGDT-ROG kernel: [20614.129304] [drm] PSP = is resuming... 2019-08-11T17:13:11.850739+08:00 MGDT-ROG kernel: [20614.192202] [drm] rese= rve 0x400000 from 0x8000c00000 for PSP TMR SIZE 2019-08-11T17:13:12.306756+08:00 MGDT-ROG kernel: [20614.649220] [drm] UVD = and UVD ENC initialized successfully. 2019-08-11T17:13:12.406756+08:00 MGDT-ROG kernel: [20614.748872] [drm] VCE initialized successfully. 2019-08-11T17:13:12.926899+08:00 MGDT-ROG kernel: [20615.271942] [drm] Fence fallback timer expired on ring gfx 2019-08-11T17:13:13.438783+08:00 MGDT-ROG kernel: [20615.783826] [drm] Fence fallback timer expired on ring comp_1.0.0 2019-08-11T17:13:14.274773+08:00 MGDT-ROG kernel: [20616.616023] [drm] Fence fallback timer expired on ring uvd_1 2019-08-11T17:13:14.671435+08:00 MGDT-ROG tracker-store[4801]: OK 2019-08-11T17:13:14.672970+08:00 MGDT-ROG systemd[2481]: tracker-store.serv= ice: Succeeded. 2019-08-11T17:13:14.782896+08:00 MGDT-ROG kernel: [20617.127844] [drm] Fence fallback timer expired on ring uvd_enc_1.0 2019-08-11T17:13:15.294768+08:00 MGDT-ROG kernel: [20617.639836] [drm] Fence fallback timer expired on ring uvd_enc_1.1 2019-08-11T17:13:15.394759+08:00 MGDT-ROG kernel: [20617.739606] [drm] reco= ver vram bo from shadow start 2019-08-11T17:13:15.397215+08:00 MGDT-ROG kernel: [20617.742231] [drm] reco= ver vram bo from shadow done 2019-08-11T17:13:15.397227+08:00 MGDT-ROG kernel: [20617.742233] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.397228+08:00 MGDT-ROG kernel: [20617.742234] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.397231+08:00 MGDT-ROG kernel: [20617.742259] amdgpu 0000:0a:00.0: GPU reset(2) succeeded! 2019-08-11T17:13:15.397233+08:00 MGDT-ROG kernel: [20617.742289] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.397235+08:00 MGDT-ROG kernel: [20617.742309] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.397242+08:00 MGDT-ROG kernel: [20617.742314] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.397262+08:00 MGDT-ROG kernel: [20617.742316] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.397265+08:00 MGDT-ROG kernel: [20617.742318] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.397268+08:00 MGDT-ROG kernel: [20617.742320] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.402744+08:00 MGDT-ROG kernel: [20617.743840] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.402753+08:00 MGDT-ROG kernel: [20617.744006] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.402755+08:00 MGDT-ROG kernel: [20617.744180] [drm] Skip scheduling IBs! 2019-08-11T17:13:15.402757+08:00 MGDT-ROG kernel: [20617.744450] [drm] Skip scheduling IBs! --=20 You are receiving this mail because: You are the assignee for the bug.= --15655159010.507eBC5.3171 Date: Sun, 11 Aug 2019 09:31:41 +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

Comme= nt # 82 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Pierre-Eric Pelloux-Prayer from comment #81)
> Can anyone provide a apitrace/renderdoc capture =
that can reliably reproduce
> the crash/freeze?

Hello, Sadly my freezes are hard to reproduce. Sometimes I can play for a d=
ay
with no freeze, sometimes it freezes in 10 minutes, one hour, and so on.

I had another freeze today:

OS: openSUSE Tumbleweed x86_64=20
Kernel: 5.2.5-1-default
Resolution: 3440x1440
DE: Xfce
WM: Xfwm4
CPU: AMD Ryzen 7 2700X (16) @ 3.700GHz
GPU: AMD ATI Radeon VII
Memory: 3791MiB / 64387MiB=20
OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.3

Game: EVE Online: Wine+DXVK. (Crossover 18.5.0) vsync off frame limiter off
Problem description: Afer rougly 1 hour of gameplay, desktop Frozen for a f=
ew
seconds but managed to recover. Game did not recover and I killed the proce=
ss.=20

DMESG:

[20612.721860] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=3D12880412, emitted seq=3D12880414
[20612.721921] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati=
on:
process exefile.exe pid 1980 thread exefile.ex:cs0 pid 2057
[20612.721925] amdgpu 0000:0a:00.0: GPU reset begin!
[20613.526448] amdgpu 0000:0a:00.0: [drm:amdgpu_ring_test_helper [amdgpu]]
*ERROR* ring kiq_2.1.0 test failed (-110)
[20613.526502] [drm:gfx_v9_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed
[20613.547524] amdgpu 0000:0a:00.0: GPU mode1 reset
[20614.055810] [drm] psp mode1 reset succeed=20
[20614.128815] amdgpu 0000:0a:00.0: GPU reset succeeded, trying to resume
[20614.128943] [drm] PCIE GART of 512M enabled (table at 0x0000008000300000=
).
[20614.129304] [drm] PSP is resuming...
[20614.192202] [drm] reserve 0x400000 from 0x8000c00000 for PSP TMR SIZE
[20614.649220] [drm] UVD and UVD ENC initialized successfully.
[20614.748872] [drm] VCE initialized successfully.
[20615.271942] [drm] Fence fallback timer expired on ring gfx
[20615.783826] [drm] Fence fallback timer expired on ring comp_1.0.0
[20616.616023] [drm] Fence fallback timer expired on ring uvd_1
[20617.127844] [drm] Fence fallback timer expired on ring uvd_enc_1.0
[20617.639836] [drm] Fence fallback timer expired on ring uvd_enc_1.1
[20617.739606] [drm] recover vram bo from shadow start
[20617.742231] [drm] recover vram bo from shadow done
[20617.742233] [drm] Skip scheduling IBs!
[20617.742234] [drm] Skip scheduling IBs!
[20617.742259] amdgpu 0000:0a:00.0: GPU reset(2) succeeded!
[20617.742289] [drm] Skip scheduling IBs!
[20617.742309] [drm] Skip scheduling IBs!
[20617.742314] [drm] Skip scheduling IBs!
[20617.742316] [drm] Skip scheduling IBs!
[20617.742318] [drm] Skip scheduling IBs!
[20617.742320] [drm] Skip scheduling IBs!
[20617.743840] [drm] Skip scheduling IBs!
[20617.744006] [drm] Skip scheduling IBs!
[20617.744180] [drm] Skip scheduling IBs!
[20617.744450] [drm] Skip scheduling IBs!

System Logs:

2019-08-11T17:13:10.377029+08:00 MGDT-ROG kernel: [20612.721860]
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled
seq=3D12880412, emitted seq=3D12880414
2019-08-11T17:13:10.377046+08:00 MGDT-ROG kernel: [20612.721921]
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process
exefile.exe pid 1980 thread exefile.ex:cs0 pid 2057
2019-08-11T17:13:10.377047+08:00 MGDT-ROG kernel: [20612.721925] amdgpu
0000:0a:00.0: GPU reset begin!
2019-08-11T17:13:11.182763+08:00 MGDT-ROG kernel: [20613.526448] amdgpu
0000:0a:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0
test failed (-110)
2019-08-11T17:13:11.182776+08:00 MGDT-ROG kernel: [20613.526502]
[drm:gfx_v9_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed
2019-08-11T17:13:11.202766+08:00 MGDT-ROG kernel: [20613.547524] amdgpu
0000:0a:00.0: GPU mode1 reset
2019-08-11T17:13:11.714757+08:00 MGDT-ROG kernel: [20614.055810] [drm] psp
mode1 reset succeed=20
2019-08-11T17:13:11.786740+08:00 MGDT-ROG kernel: [20614.128815] amdgpu
0000:0a:00.0: GPU reset succeeded, trying to resume
2019-08-11T17:13:11.786749+08:00 MGDT-ROG kernel: [20614.128943] [drm] PCIE
GART of 512M enabled (table at 0x0000008000300000).
2019-08-11T17:13:11.786751+08:00 MGDT-ROG kernel: [20614.129304] [drm] PSP =
is
resuming...
2019-08-11T17:13:11.850739+08:00 MGDT-ROG kernel: [20614.192202] [drm] rese=
rve
0x400000 from 0x8000c00000 for PSP TMR SIZE
2019-08-11T17:13:12.306756+08:00 MGDT-ROG kernel: [20614.649220] [drm] UVD =
and
UVD ENC initialized successfully.
2019-08-11T17:13:12.406756+08:00 MGDT-ROG kernel: [20614.748872] [drm] VCE
initialized successfully.
2019-08-11T17:13:12.926899+08:00 MGDT-ROG kernel: [20615.271942] [drm] Fence
fallback timer expired on ring gfx
2019-08-11T17:13:13.438783+08:00 MGDT-ROG kernel: [20615.783826] [drm] Fence
fallback timer expired on ring comp_1.0.0
2019-08-11T17:13:14.274773+08:00 MGDT-ROG kernel: [20616.616023] [drm] Fence
fallback timer expired on ring uvd_1
2019-08-11T17:13:14.671435+08:00 MGDT-ROG tracker-store[4801]: OK
2019-08-11T17:13:14.672970+08:00 MGDT-ROG systemd[2481]: tracker-store.serv=
ice:
Succeeded.
2019-08-11T17:13:14.782896+08:00 MGDT-ROG kernel: [20617.127844] [drm] Fence
fallback timer expired on ring uvd_enc_1.0
2019-08-11T17:13:15.294768+08:00 MGDT-ROG kernel: [20617.639836] [drm] Fence
fallback timer expired on ring uvd_enc_1.1
2019-08-11T17:13:15.394759+08:00 MGDT-ROG kernel: [20617.739606] [drm] reco=
ver
vram bo from shadow start
2019-08-11T17:13:15.397215+08:00 MGDT-ROG kernel: [20617.742231] [drm] reco=
ver
vram bo from shadow done
2019-08-11T17:13:15.397227+08:00 MGDT-ROG kernel: [20617.742233] [drm] Skip
scheduling IBs!
2019-08-11T17:13:15.397228+08:00 MGDT-ROG kernel: [20617.742234] [drm] Skip
scheduling IBs!
2019-08-11T17:13:15.397231+08:00 MGDT-ROG kernel: [20617.742259] amdgpu
0000:0a:00.0: GPU reset(2) succeeded!
2019-08-11T17:13:15.397233+08:00 MGDT-ROG kernel: [20617.742289] [drm] Skip
scheduling IBs!
2019-08-11T17:13:15.397235+08:00 MGDT-ROG kernel: [20617.742309] [drm] Skip
scheduling IBs!
2019-08-11T17:13:15.397242+08:00 MGDT-ROG kernel: [20617.742314] [drm] Skip
scheduling IBs!
2019-08-11T17:13:15.397262+08:00 MGDT-ROG kernel: [20617.742316] [drm] Skip
scheduling IBs!
2019-08-11T17:13:15.397265+08:00 MGDT-ROG kernel: [20617.742318] [drm] Skip
scheduling IBs!
2019-08-11T17:13:15.397268+08:00 MGDT-ROG kernel: [20617.742320] [drm] Skip
scheduling IBs!
2019-08-11T17:13:15.402744+08:00 MGDT-ROG kernel: [20617.743840] [drm] Skip
scheduling IBs!
2019-08-11T17:13:15.402753+08:00 MGDT-ROG kernel: [20617.744006] [drm] Skip
scheduling IBs!
2019-08-11T17:13:15.402755+08:00 MGDT-ROG kernel: [20617.744180] [drm] Skip
scheduling IBs!
2019-08-11T17:13:15.402757+08:00 MGDT-ROG kernel: [20617.744450] [drm] Skip
scheduling IBs!

You are receiving this mail because:
  • You are the assignee for the bug.
= --15655159010.507eBC5.3171-- --===============0361975128== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0361975128==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 12 Aug 2019 02:50:02 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0817748795==" 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 64AEE6E41F for ; Mon, 12 Aug 2019 02:50:02 +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 --===============0817748795== Content-Type: multipart/alternative; boundary="15655782021.f54AD9F02.15288" Content-Transfer-Encoding: 7bit --15655782021.f54AD9F02.15288 Date: Mon, 12 Aug 2019 02:50:02 +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=3D109955 --- Comment #83 from J. Andrew Lanz-O'Brien --- Can confirm that this bug is still present as of August 11, 2019 on kernel 5.2.8 with mesa 19.1.4. Borderlands 2 hard locked my system about 5 times tonight. Manually setting the power profile didn't help either, ie these two commands: echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_level echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk --=20 You are receiving this mail because: You are the assignee for the bug.= --15655782021.f54AD9F02.15288 Date: Mon, 12 Aug 2019 02:50:02 +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

Comme= nt # 83 on bug 10995= 5 from J. Andrew Lanz-O'Brien 
Can confirm that this bug is still present as of August 11, 20=
19 on kernel
5.2.8 with mesa 19.1.4. Borderlands 2 hard locked my system about 5 times
tonight. Manually setting the power profile didn't help either, ie these two
commands:

echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_le=
vel
echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk

You are receiving this mail because:
  • You are the assignee for the bug.
= --15655782021.f54AD9F02.15288-- --===============0817748795== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0817748795==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 12 Aug 2019 08:16:49 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1188417365==" 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 E166D6E4AA for ; Mon, 12 Aug 2019 08:16:48 +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 --===============1188417365== Content-Type: multipart/alternative; boundary="15655978081.Acd1CEBC.5896" Content-Transfer-Encoding: 7bit --15655978081.Acd1CEBC.5896 Date: Mon, 12 Aug 2019 08:16:48 +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=3D109955 --- Comment #84 from Pierre-Eric Pelloux-Prayer --- (In reply to Mauro Gaspari from comment #82) > (In reply to Pierre-Eric Pelloux-Prayer from comment #81) > > Can anyone provide a apitrace/renderdoc capture that can reliably repro= duce > > the crash/freeze? >=20 > Hello, Sadly my freezes are hard to reproduce. Sometimes I can play for a > day with no freeze, sometimes it freezes in 10 minutes, one hour, and so = on. >=20 Ok. This patch https://patchwork.freedesktop.org/series/64792/ might help: it w= on't fix any issue, but when a timeout is detected it should allow the soft reco= very of the GPU. Other things worth trying: setting AMD_DEBUG environment variables. I'd suggest: AMD_DEBUG=3Dzerovram,nodma,nodpbb There are others (see mesa/src/gallium/drivers/radeonsi/si_pipe.c) to try if these don't help. --=20 You are receiving this mail because: You are the assignee for the bug.= --15655978081.Acd1CEBC.5896 Date: Mon, 12 Aug 2019 08:16:48 +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

Comme= nt # 84 on bug 10995= 5 from Pierre= -Eric Pelloux-Prayer 
(In reply to Mauro Gaspari from comment #82)
> (In reply to Pierre-Eric Pelloux-Prayer from comment #81)
> > Can anyone provide a apitrace/renderdoc capture that can reliably=
 reproduce
> > the crash/freeze?
>=20
> Hello, Sadly my freezes are hard to reproduce. Sometimes I can play fo=
r a
> day with no freeze, sometimes it freezes in 10 minutes, one hour, and =
so on.
> 

Ok.

This patch http=
s://patchwork.freedesktop.org/series/64792/ might help: it won't
fix any issue, but when a timeout is detected it should allow the soft reco=
very
of the GPU.

Other things worth trying: setting AMD_DEBUG environment variables. I'd
suggest:

   AMD_DEBUG=3Dzerovram,nodma,nodpbb

There are others (see mesa/src/gallium/drivers/radeonsi/si_pipe.c) to try if
these don't help.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15655978081.Acd1CEBC.5896-- --===============1188417365== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1188417365==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 12 Aug 2019 14:10:11 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1977090980==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 0CD686E52E for ; Mon, 12 Aug 2019 14:10:11 +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 --===============1977090980== Content-Type: multipart/alternative; boundary="15656190110.d8bBDAAb1.31843" Content-Transfer-Encoding: 7bit --15656190110.d8bBDAAb1.31843 Date: Mon, 12 Aug 2019 14:10:10 +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=3D109955 --- Comment #85 from Mauro Gaspari --- (In reply to Pierre-Eric Pelloux-Prayer from comment #84) > (In reply to Mauro Gaspari from comment #82) > > (In reply to Pierre-Eric Pelloux-Prayer from comment #81) > > > Can anyone provide a apitrace/renderdoc capture that can reliably rep= roduce > > > the crash/freeze? > >=20 > > Hello, Sadly my freezes are hard to reproduce. Sometimes I can play for= a > > day with no freeze, sometimes it freezes in 10 minutes, one hour, and s= o on. > >=20 >=20 > Ok. >=20 > This patch https://patchwork.freedesktop.org/series/64792/ might help: it > won't fix any issue, but when a timeout is detected it should allow the s= oft > recovery of the GPU. >=20 > Other things worth trying: setting AMD_DEBUG environment variables. I'd > suggest: >=20 > AMD_DEBUG=3Dzerovram,nodma,nodpbb >=20 > There are others (see mesa/src/gallium/drivers/radeonsi/si_pipe.c) to try= if > these don't help. Thank you. I will first try to reintroduce the kernel parameters I previously used. Do= you think those can help at all? CPU rcu_nocbs=3D0-15 (adjust to the number of cores of your cpu) idle=3Dnomwait processor.max_cstate=3D5 pcie_aspm=3Doff=20 GPU amdgpu.dc=3D1 amdgpu.vm_update_mode=3D0 amdgpu.dpm=3D-1 amdgpu.ppfeaturemask=3D0xffffffff amdgpu.vm_fault_stop=3D2 amdgpu.vm_debug=3D1 amdgpu.gpu_recovery=3D0 --=20 You are receiving this mail because: You are the assignee for the bug.= --15656190110.d8bBDAAb1.31843 Date: Mon, 12 Aug 2019 14:10:11 +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

Comme= nt # 85 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Pierre-Eric Pelloux-Prayer from comment #84)
> (In reply to Mauro Gaspari from comment #82)
> > (In reply to Pierre-Eric Pelloux-Prayer from comment #81)
> > > Can anyone provide a apitrace/renderdoc capture that can rel=
iably reproduce
> > > the crash/freeze?
> >=20
> > Hello, Sadly my freezes are hard to reproduce. Sometimes I can pl=
ay for a
> > day with no freeze, sometimes it freezes in 10 minutes, one hour,=
 and so on.
> >=20
>=20
> Ok.
>=20
> This patch https://patchwork.freedesktop.org/series/64792/ might help: it
> won't fix any issue, but when a timeout is detected it should allow th=
e soft
> recovery of the GPU.
>=20
> Other things worth trying: setting AMD_DEBUG environment variables. I'd
> suggest:
>=20
>    AMD_DEBUG=3Dzerovram,nodma,nodpbb
>=20
> There are others (see mesa/src/gallium/drivers/radeonsi/si_pipe.c) to =
try if
> these don't help.

Thank you.

I will first try to reintroduce the kernel parameters I previously used. Do=
 you
think those can help at all?

CPU
rcu_nocbs=3D0-15 (adjust to the number of cores of your cpu)
idle=3Dnomwait
processor.max_cstate=3D5
pcie_aspm=3Doff=20

GPU
amdgpu.dc=3D1
amdgpu.vm_update_mode=3D0
amdgpu.dpm=3D-1
amdgpu.ppfeaturemask=3D0xffffffff
amdgpu.vm_fault_stop=3D2
amdgpu.vm_debug=3D1
amdgpu.gpu_recovery=3D0

You are receiving this mail because:
  • You are the assignee for the bug.
= --15656190110.d8bBDAAb1.31843-- --===============1977090980== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1977090980==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 13 Aug 2019 15:59:27 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0814248364==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id C20F36E1BC for ; Tue, 13 Aug 2019 15:59:27 +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 --===============0814248364== Content-Type: multipart/alternative; boundary="15657119674.07c7f92Ac.30654" Content-Transfer-Encoding: 7bit --15657119674.07c7f92Ac.30654 Date: Tue, 13 Aug 2019 15:59:27 +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=3D109955 --- Comment #86 from Pierre-Eric Pelloux-Prayer --- (In reply to Mauro Gaspari from comment #85) > I will first try to reintroduce the kernel parameters I previously used. > Do you think those can help at all? > [...] > GPU > amdgpu.dc=3D1 Not needed: dc will be automatically enabled on recent GPU > amdgpu.vm_update_mode=3D0 Shouldn't be needed since it should be the default value.=20 > amdgpu.dpm=3D-1 Not needed: this is the default value > amdgpu.ppfeaturemask=3D0xffffffff The only difference with the default value is that you're enabling Overdriv= e. I'd suggest to keep the default parameter here. > amdgpu.vm_fault_stop=3D2 I think this one isn't helpful (it's a debugging tool) > amdgpu.vm_debug=3D1 This one can help. > amdgpu.gpu_recovery=3D0 No opinion on this one :) --=20 You are receiving this mail because: You are the assignee for the bug.= --15657119674.07c7f92Ac.30654 Date: Tue, 13 Aug 2019 15:59:27 +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

Comme= nt # 86 on bug 10995= 5 from Pierre= -Eric Pelloux-Prayer 
(In reply to Mauro Gaspari from comment #85)
> I will first try to reintroduce the kernel param=
eters I previously used.
> Do you think those can help at all?
> [...]
> GPU
> amdgpu.dc=3D1

Not needed: dc will be automatically enabled on recent GPU

> amdgpu.vm_update_mode=3D0

Shouldn't be needed since it should be the default value.=20

> amdgpu.dpm=3D-1

Not needed: this is the default value

> amdgpu.ppfeaturemask=3D0xffffffff

The only difference with the default value is that you're enabling Overdriv=
e.
I'd suggest to keep the default parameter here.

> amdgpu.vm_fault_stop=3D2

I think this one isn't helpful (it's a debugging tool)

> amdgpu.vm_debug=3D1

This one can help.

> amdgpu.gpu_recovery=3D0

No opinion on this one :)

You are receiving this mail because:
  • You are the assignee for the bug.
= --15657119674.07c7f92Ac.30654-- --===============0814248364== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0814248364==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 13 Aug 2019 16:19:27 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2075271404==" 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 AF2DF6E1C4 for ; Tue, 13 Aug 2019 16:19:27 +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 --===============2075271404== Content-Type: multipart/alternative; boundary="15657131671.C0dA4d.2538" Content-Transfer-Encoding: 7bit --15657131671.C0dA4d.2538 Date: Tue, 13 Aug 2019 16:19:27 +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=3D109955 --- Comment #87 from Mauro Gaspari --- (In reply to Pierre-Eric Pelloux-Prayer from comment #86) > (In reply to Mauro Gaspari from comment #85) > > I will first try to reintroduce the kernel parameters I previously used. > > Do you think those can help at all? > > [...] > > GPU > > amdgpu.dc=3D1 >=20 > Not needed: dc will be automatically enabled on recent GPU >=20 > > amdgpu.vm_update_mode=3D0 >=20 > Shouldn't be needed since it should be the default value.=20 >=20 > > amdgpu.dpm=3D-1 >=20 > Not needed: this is the default value >=20 > > amdgpu.ppfeaturemask=3D0xffffffff >=20 > The only difference with the default value is that you're enabling Overdr= ive. > I'd suggest to keep the default parameter here. >=20 > > amdgpu.vm_fault_stop=3D2 >=20 > I think this one isn't helpful (it's a debugging tool) >=20 > > amdgpu.vm_debug=3D1 >=20 > This one can help. >=20 > > amdgpu.gpu_recovery=3D0 >=20 > No opinion on this one :) Thank you! I am currently testing on ubuntu budgie with valve-released Mesa-ACO and so far, I am having no freezes nor crashes. Couple of days without incidents. = But as I posted previously, it is all a bit random so I think I will need to use this for at least a week.=20 I will report back soon with my findings. --=20 You are receiving this mail because: You are the assignee for the bug.= --15657131671.C0dA4d.2538 Date: Tue, 13 Aug 2019 16:19:27 +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

Comme= nt # 87 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Pierre-Eric Pelloux-Prayer from comment #86)
> (In reply to Mauro Gaspari from comment #85)
> > I will first try to reintroduce the kernel parameters I previousl=
y used.
> > Do you think those can help at all?
> > [...]
> > GPU
> > amdgpu.dc=3D1
>=20
> Not needed: dc will be automatically enabled on recent GPU
>=20
> > amdgpu.vm_update_mode=3D0
>=20
> Shouldn't be needed since it should be the default value.=20
>=20
> > amdgpu.dpm=3D-1
>=20
> Not needed: this is the default value
>=20
> > amdgpu.ppfeaturemask=3D0xffffffff
>=20
> The only difference with the default value is that you're enabling Ove=
rdrive.
> I'd suggest to keep the default parameter here.
>=20
> > amdgpu.vm_fault_stop=3D2
>=20
> I think this one isn't helpful (it's a debugging tool)
>=20
> > amdgpu.vm_debug=3D1
>=20
> This one can help.
>=20
> > amdgpu.gpu_recovery=3D0
>=20
> No opinion on this one :)

Thank you!

I am currently testing on ubuntu budgie with valve-released Mesa-ACO and so
far, I am having no freezes nor crashes. Couple of days without incidents. =
But
as I posted previously, it is all a bit random so I think I will need to use
this for at least a week.=20

I will report back soon with my findings.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15657131671.C0dA4d.2538-- --===============2075271404== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============2075271404==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Fri, 30 Aug 2019 19:01:52 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1942802388==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 100FF6E3C7 for ; Fri, 30 Aug 2019 19:01:53 +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 --===============1942802388== Content-Type: multipart/alternative; boundary="15671917130.be2FF1Cf.2902" Content-Transfer-Encoding: 7bit --15671917130.be2FF1Cf.2902 Date: Fri, 30 Aug 2019 19:01:53 +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=3D109955 --- Comment #88 from Sam --- I have recently started to get even more frequent freezes even on Vulkan no= w on kernel 5.2.10 The workaround of the power profile still works (for me) and is the only wa= y to avoid them: # echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_lev= el # echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk --=20 You are receiving this mail because: You are the assignee for the bug.= --15671917130.be2FF1Cf.2902 Date: Fri, 30 Aug 2019 19:01:53 +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

Comme= nt # 88 on bug 10995= 5 from = Sam 
I have recently started to get even more frequent freezes even=
 on Vulkan now on
kernel 5.2.10

The workaround of the power profile still works (for me) and is the only wa=
y to
avoid them:

# echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_=
level
# echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk

You are receiving this mail because:
  • You are the assignee for the bug.
= --15671917130.be2FF1Cf.2902-- --===============1942802388== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1942802388==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 31 Aug 2019 01:00:23 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1684763052==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id A73956E136 for ; Sat, 31 Aug 2019 01:00:23 +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 --===============1684763052== Content-Type: multipart/alternative; boundary="15672132231.34F7.309" Content-Transfer-Encoding: 7bit --15672132231.34F7.309 Date: Sat, 31 Aug 2019 01:00:23 +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=3D109955 --- Comment #89 from Jaap Buurman --- Freezes are getting way more frequent for me as well :( --=20 You are receiving this mail because: You are the assignee for the bug.= --15672132231.34F7.309 Date: Sat, 31 Aug 2019 01:00:23 +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

Comme= nt # 89 on bug 10995= 5 from Jaap Buurman 
Freezes are getting way more frequent for me as well :(

You are receiving this mail because:
  • You are the assignee for the bug.
= --15672132231.34F7.309-- --===============1684763052== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1684763052==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 31 Aug 2019 05:21:20 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0069115281==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id E5B206E175 for ; Sat, 31 Aug 2019 05:21:20 +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 --===============0069115281== Content-Type: multipart/alternative; boundary="15672288800.17E689f.12221" Content-Transfer-Encoding: 7bit --15672288800.17E689f.12221 Date: Sat, 31 Aug 2019 05:21:20 +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=3D109955 --- Comment #90 from Mauro Gaspari --- @Sam and @Jaap Buurman Can you please help and post system info regarding your crash? I hope that = with more detailed reports, we can get better help. Example: OS Info can be taken from neofetch: System info: OS: openSUSE Tumbleweed Kernel: 5.2.10-1-default Resolution: 3440x1440 CPU: AMD Ryzen 7 2700X (16) @ 3.700GHz GPU: AMD ATI Radeon VII=20 Memory: 6308MiB / 64387MiB=20 Mesa info can be taken from this command: glxinfo | grep "OpenGL version"=20 OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.5 Game being played: Eve Online Native or Wine or Wine+DXVK: Wine+DXVK Directx11 Crash type: Game crash? Full System freeze? System freeze but still can dro= p to tty? DMESG output after the crash: sudo dmesg | grep amdgpu systemd logs output after the crash (If your system did not freeze and you = can get it before reboot): sudo journalctl -b | grep amdgpu systemd logs output after the crash (If your system froze and you get logs after reboot): sudo journalctl -b -1 | grep amdgpu If your distribution does not use persistent systemd logs you can change it according to your distribution. Example for openSUSE: https://www.suse.com/documentation/sles-12/book_sle_admin/data/journalctl_p= ersistent.html --=20 You are receiving this mail because: You are the assignee for the bug.= --15672288800.17E689f.12221 Date: Sat, 31 Aug 2019 05:21:20 +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

Comme= nt # 90 on bug 10995= 5 from = Mauro Gaspari 
@Sam and @Jaap Buurman

Can you please help and post system info regarding your crash? I hope that =
with
more detailed reports, we can get better help.

Example:

OS Info can be taken from neofetch:
System info:
OS: openSUSE Tumbleweed
Kernel: 5.2.10-1-default
Resolution: 3440x1440
CPU: AMD Ryzen 7 2700X (16) @ 3.700GHz
GPU: AMD ATI Radeon VII=20
Memory: 6308MiB / 64387MiB=20


Mesa info can be taken from this command:
glxinfo | grep "OpenGL version"=20
OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.5


Game being played: Eve Online
Native or Wine or Wine+DXVK: Wine+DXVK Directx11


Crash type: Game crash? Full System freeze? System freeze but still can dro=
p to
tty?



DMESG output after the crash:
sudo dmesg | grep amdgpu



systemd logs output after the crash (If your system did not freeze and you =
can
get it before reboot):
sudo journalctl -b | grep amdgpu


systemd logs output after the crash (If your system froze and you get logs
after reboot):
sudo journalctl -b -1 | grep amdgpu

If your distribution does not use persistent systemd logs you can change it
according to your distribution. Example for openSUSE:
https://www.suse.com/documentation/sles-12/book_=
sle_admin/data/journalctl_persistent.html

You are receiving this mail because:
  • You are the assignee for the bug.
= --15672288800.17E689f.12221-- --===============0069115281== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0069115281==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 31 Aug 2019 22:38:24 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0533948176==" 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 396F46E161 for ; Sat, 31 Aug 2019 22:38:27 +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 --===============0533948176== Content-Type: multipart/alternative; boundary="15672911070.CCb6A.760" Content-Transfer-Encoding: 7bit --15672911070.CCb6A.760 Date: Sat, 31 Aug 2019 22:38:27 +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=3D109955 --- Comment #91 from Wilko Bartels --- how big are your swap partitions guys? just toying around here :-) --=20 You are receiving this mail because: You are the assignee for the bug.= --15672911070.CCb6A.760 Date: Sat, 31 Aug 2019 22:38:27 +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

Comme= nt # 91 on bug 10995= 5 from = Wilko Bartels 
how big are your swap partitions guys? just toying around here=
 :-)

You are receiving this mail because:
  • You are the assignee for the bug.
= --15672911070.CCb6A.760-- --===============0533948176== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0533948176==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 01 Sep 2019 22:49:57 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2048614528==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id A37D289151 for ; Sun, 1 Sep 2019 22:49:57 +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 --===============2048614528== Content-Type: multipart/alternative; boundary="15673781974.d99aDDaf.16765" Content-Transfer-Encoding: 7bit --15673781974.d99aDDaf.16765 Date: Sun, 1 Sep 2019 22:49:57 +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=3D109955 --- Comment #92 from Jaap Buurman --- (In reply to Mauro Gaspari from comment #90) > @Sam and @Jaap Buurman >=20 > Can you please help and post system info regarding your crash? I hope that > with more detailed reports, we can get better help. OS: Arch Linux x86_64=20 `+oooo: Host: AB350-Gaming 3=20 `+oooooo: Kernel: 5.2.11-arch1-1-ARCH=20 -+oooooo+: Uptime: 1 min=20 `/:-:++oooo+: Packages: 1229 (pacman)=20 `/++++/+++++++: Shell: bash 5.0.9=20 `/++++++++++++++: Terminal: /dev/pts/0=20 `/+++ooooooooooooo/` CPU: AMD Ryzen 7 1800X (16) @ 3.60= 0GHz=20 ./ooosssso++osssssso+` GPU: AMD ATI Radeon RX Vega 56/64= =20 .oossssso-````/ossssss+` Memory: 1178MiB / 48304MiB=20 > Mesa info can be taken from this command: > glxinfo | grep "OpenGL version"=20 [jaap@Jaap-Desktop ~]$ glxinfo | grep "OpenGL version" OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.3.0-devel (git-db73bde35c) I am running this version because I was trying out the mesa-aco from the AU= R. I experienced the same crashes with the regular mesa drivers from Arch's offi= cial repositories. > Game being played:=20 World of Warcraft: Classic Wine/DXVK 1.3.2 > Crash type: Game crash? Full System freeze? System freeze but still can d= rop > to tty? GPU doesn't successfully reset. Cannot drop to a different tty. However, I = am able to access logs via SSH. Full dmesg log: https://pastebin.com/E2071wHF > DMESG output after the crash: > sudo dmesg | grep amdgpu https://pastebin.com/2kWpeP1y > systemd logs output after the crash (If your system did not freeze and you > can get it before reboot): > sudo journalctl -b | grep amdgpu https://pastebin.com/4e1PkJ39 > systemd logs output after the crash (If your system froze and you get logs > after reboot): > sudo journalctl -b -1 | grep amdgpu https://pastebin.com/4mqXNsNQ Hopefully this information is detailed enough to assist in tracking down the root cause of the issue! --=20 You are receiving this mail because: You are the assignee for the bug.= --15673781974.d99aDDaf.16765 Date: Sun, 1 Sep 2019 22:49:57 +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

Comme= nt # 92 on bug 10995= 5 from Jaap Buurman 
(In reply to Mauro Gaspari from comment #90)
> @Sam and @Jaap Buurman
>=20
> Can you please help and post system info regarding your crash? I hope =
that
> with more detailed reports, we can get better help.

OS: Arch Linux x86_64=20
                `+oooo:                  Host: AB350-Gaming 3=20
               `+oooooo:                 Kernel: 5.2.11-arch1-1-ARCH=20
               -+oooooo+:                Uptime: 1 min=20
             `/:-:++oooo+:               Packages: 1229 (pacman)=20
            `/++++/+++++++:              Shell: bash 5.0.9=20
           `/++++++++++++++:             Terminal: /dev/pts/0=20
          `/+++ooooooooooooo/`           CPU: AMD Ryzen 7 1800X (16) @ =
3.600GHz=20
         ./ooosssso++osssssso+`          GPU: AMD ATI Radeon RX Vega 56/64=
=20
        .oossssso-````/ossssss+`         Memory: 1178MiB / 48304MiB=20



> Mesa info can be taken from this command:
> glxinfo | grep "OpenGL version" 

[jaap@Jaap-Desktop ~]$ glxinfo | grep "OpenGL version"
OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.3.0-devel
(git-db73bde35c)

I am running this version because I was trying out the mesa-aco from the AU=
R. I
experienced the same crashes with the regular mesa drivers from Arch's offi=
cial
repositories.

> Game being played: 

World of Warcraft: Classic Wine/DXVK 1.3.2

> Crash type: Game crash? Full System freeze? Syst=
em freeze but still can drop
> to tty?

GPU doesn't successfully reset. Cannot drop to a different tty. However, I =
am
able to access logs via SSH. Full dmesg log: https://pastebin.com/E2071wHF

> DMESG output after the crash:
> sudo dmesg | grep amdgpu

https://pastebin.com/2kWpeP1y

> systemd logs output after the crash (If your sys=
tem did not freeze and you
> can get it before reboot):
> sudo journalctl -b | grep amdgpu

https://pastebin.com/4e1PkJ39

> systemd logs output after the crash (If your sys=
tem froze and you get logs
> after reboot):
> sudo journalctl -b -1 | grep amdgpu

https://pastebin.com/4mqXNsNQ



Hopefully this information is detailed enough to assist in tracking down the
root cause of the issue!

You are receiving this mail because:
  • You are the assignee for the bug.
= --15673781974.d99aDDaf.16765-- --===============2048614528== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============2048614528==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 02 Sep 2019 07:48:19 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0434680938==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 10EDC89B11 for ; Mon, 2 Sep 2019 07:48:20 +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 --===============0434680938== Content-Type: multipart/alternative; boundary="15674105000.C3FD.16830" Content-Transfer-Encoding: 7bit --15674105000.C3FD.16830 Date: Mon, 2 Sep 2019 07:48:20 +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=3D109955 --- Comment #93 from Wilko Bartels --- (In reply to Wilko Bartels from comment #91) > how big are your swap partitions guys? just toying around here :-) also i wanna know if anyone else on arch tested the amdgpu-pro yet? i played only 3 hours now. we all know that doesnt mean anything :-) but fingers crossed. i also have no idea how to confirm its even used. the kernel module showing amdgpu in both circumstances right? --=20 You are receiving this mail because: You are the assignee for the bug.= --15674105000.C3FD.16830 Date: Mon, 2 Sep 2019 07:48:20 +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

Comme= nt # 93 on bug 10995= 5 from = Wilko Bartels 
(In reply to Wilko Bartels from comment #91)
> how big are your swap partitions guys? just toyi=
ng around here :-)

also i wanna know if anyone else on arch tested the amdgpu-pro yet?
i played only 3 hours now. we all know that doesnt mean anything :-)
but fingers crossed.
i also have no idea how to confirm its even used. the kernel module showing
amdgpu in both circumstances right?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15674105000.C3FD.16830-- --===============0434680938== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0434680938==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 02 Sep 2019 10:07:42 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0244373441==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 73BEA89906 for ; Mon, 2 Sep 2019 10:07:42 +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 --===============0244373441== Content-Type: multipart/alternative; boundary="15674188620.03AFc.7974" Content-Transfer-Encoding: 7bit --15674188620.03AFc.7974 Date: Mon, 2 Sep 2019 10:07:42 +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=3D109955 --- Comment #94 from Mauro Gaspari --- (In reply to Wilko Bartels from comment #93) > (In reply to Wilko Bartels from comment #91) > > how big are your swap partitions guys? just toying around here :-) >=20 > also i wanna know if anyone else on arch tested the amdgpu-pro yet? > i played only 3 hours now. we all know that doesnt mean anything :-) > but fingers crossed. > i also have no idea how to confirm its even used. the kernel module showi= ng > amdgpu in both circumstances right? Hello, I am testing on multiple distributions with different mesa drivers. Swap si= ze is 2GB to 8GB depending on the distro. Having 64GB RAM, my swap is constant= ly empty. So far the best performance I have is on ubuntu budgie 18.04 with MESA-ACO released by Valve. I had no crashes in quite some time. But I did not have = much time to play lately, so I need more time to test. Regarding AMDGPU-PRO, I tested on ubuntu a very long time ago, and it was q= uite bad. But I think it makes sense to test and compare. I will install another ubuntu budgie 18.04 on a separate SSD and use it with AMDGPU-PRO. and see if the same issues are shared with AMDGPU, or not. Thanks, and let me know how AMDGPU-PRO works on arch. --=20 You are receiving this mail because: You are the assignee for the bug.= --15674188620.03AFc.7974 Date: Mon, 2 Sep 2019 10:07:42 +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

Comme= nt # 94 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Wilko Bartels from comment #93)
> (In reply to Wilko Bartels from comment #91)
> > how big are your swap partitions guys? just toying around here :-)
>=20
> also i wanna know if anyone else on arch tested the amdgpu-pro yet?
> i played only 3 hours now. we all know that doesnt mean anything :-)
> but fingers crossed.
> i also have no idea how to confirm its even used. the kernel module sh=
owing
> amdgpu in both circumstances right?

Hello,
I am testing on multiple distributions with different mesa drivers. Swap si=
ze
is 2GB to 8GB depending on the distro. Having 64GB RAM, my swap is constant=
ly
empty.
So far the best performance I have is on ubuntu budgie 18.04 with MESA-ACO
released by Valve. I had no crashes in quite some time. But I did not have =
much
time to play lately, so I need more time to test.

Regarding AMDGPU-PRO, I tested on ubuntu a very long time ago, and it was q=
uite
bad. But I think it makes sense to test and compare. I will install another
ubuntu budgie 18.04 on a separate SSD and use it with AMDGPU-PRO. and see if
the same issues are shared with AMDGPU, or not.

Thanks, and let me know how AMDGPU-PRO works on arch.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15674188620.03AFc.7974-- --===============0244373441== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0244373441==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 04 Sep 2019 20:41:33 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1514995052==" 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 5174C89C82 for ; Wed, 4 Sep 2019 20:41:33 +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 --===============1514995052== Content-Type: multipart/alternative; boundary="15676296934.9E061fd3.6933" Content-Transfer-Encoding: 7bit --15676296934.9E061fd3.6933 Date: Wed, 4 Sep 2019 20:41:33 +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=3D109955 --- Comment #95 from koala_man --- I am also seeing this issue on my stock Ubuntu.=20 >OS Info can be taken from neofetch OS: Ubuntu 19.04 x86_64 Host: All Series Kernel: 5.0.0-27-generic Uptime: 8 mins Packages: 2671 (dpkg), 6 (flatpak), 10 (snap) Shell: bash 5.0.3 Terminal: /dev/pts/1 CPU: Intel i5-4690 (4) @ 3.900GHz GPU: Intel HD Graphics GPU: AMD ATI Radeon RX Vega 64 Memory: 861MiB / 23976MiB > glxinfo | grep "OpenGL version"=20 OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.0.8 >Game being played glxgears in a window, no other applications running >Native or Wine or Wine+DXVK Native > Crash type:=20 X crashed with colorful pattern, stopped responding to Ctrl-Alt-Fx. `ssh` s= till works. X server does not accept new commands, e.g. `DISPLAY=3D:0 glxgears` >sudo dmesg | grep amdgpu [ 2.328917] [drm] amdgpu kernel modesetting enabled. [ 2.331916] fb0: switching to amdgpudrmfb from EFI VGA [ 2.333325] amdgpu 0000:03:00.0: No more image in the PCI ROM [ 2.333400] amdgpu 0000:03:00.0: VRAM: 8176M 0x000000F400000000 - 0x000000F5FEFFFFFF (8176M used) [ 2.333401] amdgpu 0000:03:00.0: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF [ 2.333403] amdgpu 0000:03:00.0: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF [ 2.333866] [drm] amdgpu: 8176M of VRAM memory ready [ 2.333870] [drm] amdgpu: 8176M of GTT memory ready. [ 2.871622] fbcon: amdgpudrmfb (fb0) is primary device [ 2.929315] amdgpu 0000:03:00.0: fb0: amdgpudrmfb frame buffer device [ 2.944233] amdgpu 0000:03:00.0: ring gfx uses VM inv eng 0 on hub 0 [ 2.944249] amdgpu 0000:03:00.0: ring comp_1.0.0 uses VM inv eng 1 on hu= b 0 [ 2.944264] amdgpu 0000:03:00.0: ring comp_1.1.0 uses VM inv eng 4 on hu= b 0 [ 2.944279] amdgpu 0000:03:00.0: ring comp_1.2.0 uses VM inv eng 5 on hu= b 0 [ 2.944294] amdgpu 0000:03:00.0: ring comp_1.3.0 uses VM inv eng 6 on hu= b 0 [ 2.944308] amdgpu 0000:03:00.0: ring comp_1.0.1 uses VM inv eng 7 on hu= b 0 [ 2.944323] amdgpu 0000:03:00.0: ring comp_1.1.1 uses VM inv eng 8 on hu= b 0 [ 2.944338] amdgpu 0000:03:00.0: ring comp_1.2.1 uses VM inv eng 9 on hu= b 0 [ 2.944353] amdgpu 0000:03:00.0: ring comp_1.3.1 uses VM inv eng 10 on h= ub 0 [ 2.944368] amdgpu 0000:03:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hu= b 0 [ 2.944382] amdgpu 0000:03:00.0: ring sdma0 uses VM inv eng 0 on hub 1 [ 2.944396] amdgpu 0000:03:00.0: ring page0 uses VM inv eng 1 on hub 1 [ 2.944410] amdgpu 0000:03:00.0: ring sdma1 uses VM inv eng 4 on hub 1 [ 2.944424] amdgpu 0000:03:00.0: ring page1 uses VM inv eng 5 on hub 1 [ 2.944438] amdgpu 0000:03:00.0: ring uvd_0 uses VM inv eng 6 on hub 1 [ 2.944452] amdgpu 0000:03:00.0: ring uvd_enc_0.0 uses VM inv eng 7 on h= ub 1 [ 2.944467] amdgpu 0000:03:00.0: ring uvd_enc_0.1 uses VM inv eng 8 on h= ub 1 [ 2.944482] amdgpu 0000:03:00.0: ring vce0 uses VM inv eng 9 on hub 1 [ 2.944496] amdgpu 0000:03:00.0: ring vce1 uses VM inv eng 10 on hub 1 [ 2.944510] amdgpu 0000:03:00.0: ring vce2 uses VM inv eng 11 on hub 1 [ 2.945073] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:03:00.0 on minor 1 [ 288.676190] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D72560, emitted seq=3D72562 [ 288.676350] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati= on: process glxgears pid 2963 thread glxgears:cs0 pid 2964 [ 288.676358] amdgpu 0000:03:00.0: GPU reset begin! [ 288.759763] amdgpu 0000:03:00.0: GPU reset [ 289.208563] RIP: 0010:amdgpu_cs_ioctl+0xaa3/0x1320 [amdgpu] [ 289.208604] ? amdgpu_cs_find_mapping+0x120/0x120 [amdgpu] [ 289.208647] ? amdgpu_cs_find_mapping+0x120/0x120 [amdgpu] [ 289.208673] amdgpu_drm_ioctl+0x4f/0x80 [amdgpu] [ 289.208690] Modules linked in: aufs overlay cmac bnep binfmt_misc nls_iso8859_1 snd_hda_codec_ca0132 snd_hda_codec_realtek snd_hda_codec_gene= ric snd_hda_codec_hdmi ledtrig_audio snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi btusb input_l= eds btrtl btbcm btintel bluetooth eeepc_wmi asus_wmi snd_seq ecdh_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp sparse_keymap kvm_intel intel_cstate intel_rapl_perf snd_seq_device snd_timer wmi_bmof snd soundcore mei_me mei tpm_infineon mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg hid_gener= ic usbhid hid dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel amdgpu i915 kvmgt vfio_mdev mdev chash aes_x86_64 amd_iommu_v2 crypto_simd vfio_iommu_type1 gpu_sched cryptd glue_helper ttm vfio ahci lib= ahci i2c_i801 kvm mxm_wmi lpc_ich irqbypass i2c_algo_bit pata_acpi e1000e drm_kms_helper syscopyarea sysfillrect [ 289.208743] RIP: 0010:amdgpu_cs_ioctl+0xaa3/0x1320 [amdgpu] [ 289.395715] amdgpu 0000:03:00.0: GPU reset succeeded, trying to resume [ 289.395813] [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* VRAM is los= t! [ 289.969158] amdgpu 0000:03:00.0: GPU reset(2) succeeded! [ 289.969333] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 289.969519] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! >sudo journalctl -b | grep amdgpu Same as dmesg output (after dropping timestamps), verified by vimdiff. >Other No swap, 144hz monitor, GPU was very hot to the touch considering it had on= ly run glxgears @ 144 fps for 5 minutes. --=20 You are receiving this mail because: You are the assignee for the bug.= --15676296934.9E061fd3.6933 Date: Wed, 4 Sep 2019 20:41:33 +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

Comme= nt # 95 on bug 10995= 5 from koala_man 
I am also seeing this issue on my stock Ubuntu.=20

>OS Info can be taken from neofetch
OS: Ubuntu 19.04 x86_64
Host: All Series
Kernel: 5.0.0-27-generic
Uptime: 8 mins
Packages: 2671 (dpkg), 6 (flatpak), 10 (snap)
Shell: bash 5.0.3
Terminal: /dev/pts/1
CPU: Intel i5-4690 (4) @ 3.900GHz
GPU: Intel HD Graphics
GPU: AMD ATI Radeon RX Vega 64
Memory: 861MiB / 23976MiB

> glxinfo | grep "OpenGL version" 
OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.0.8

>Game being played
glxgears in a window, no other applications running

>Native or Wine or Wine+DXVK
Native

> Crash type: 
X crashed with colorful pattern, stopped responding to Ctrl-Alt-Fx. `ssh` s=
till
works. X server does not accept new commands, e.g. `DISPLAY=3D:0 glxgears`

>sudo dmesg | grep amdgpu
[    2.328917] [drm] amdgpu kernel modesetting enabled.
[    2.331916] fb0: switching to amdgpudrmfb from EFI VGA
[    2.333325] amdgpu 0000:03:00.0: No more image in the PCI ROM
[    2.333400] amdgpu 0000:03:00.0: VRAM: 8176M 0x000000F400000000 -
0x000000F5FEFFFFFF (8176M used)
[    2.333401] amdgpu 0000:03:00.0: GART: 512M 0x0000000000000000 -
0x000000001FFFFFFF
[    2.333403] amdgpu 0000:03:00.0: AGP: 267419648M 0x000000F800000000 -
0x0000FFFFFFFFFFFF
[    2.333866] [drm] amdgpu: 8176M of VRAM memory ready
[    2.333870] [drm] amdgpu: 8176M of GTT memory ready.
[    2.871622] fbcon: amdgpudrmfb (fb0) is primary device
[    2.929315] amdgpu 0000:03:00.0: fb0: amdgpudrmfb frame buffer device
[    2.944233] amdgpu 0000:03:00.0: ring gfx uses VM inv eng 0 on hub 0
[    2.944249] amdgpu 0000:03:00.0: ring comp_1.0.0 uses VM inv eng 1 on hu=
b 0
[    2.944264] amdgpu 0000:03:00.0: ring comp_1.1.0 uses VM inv eng 4 on hu=
b 0
[    2.944279] amdgpu 0000:03:00.0: ring comp_1.2.0 uses VM inv eng 5 on hu=
b 0
[    2.944294] amdgpu 0000:03:00.0: ring comp_1.3.0 uses VM inv eng 6 on hu=
b 0
[    2.944308] amdgpu 0000:03:00.0: ring comp_1.0.1 uses VM inv eng 7 on hu=
b 0
[    2.944323] amdgpu 0000:03:00.0: ring comp_1.1.1 uses VM inv eng 8 on hu=
b 0
[    2.944338] amdgpu 0000:03:00.0: ring comp_1.2.1 uses VM inv eng 9 on hu=
b 0
[    2.944353] amdgpu 0000:03:00.0: ring comp_1.3.1 uses VM inv eng 10 on h=
ub 0
[    2.944368] amdgpu 0000:03:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hu=
b 0
[    2.944382] amdgpu 0000:03:00.0: ring sdma0 uses VM inv eng 0 on hub 1
[    2.944396] amdgpu 0000:03:00.0: ring page0 uses VM inv eng 1 on hub 1
[    2.944410] amdgpu 0000:03:00.0: ring sdma1 uses VM inv eng 4 on hub 1
[    2.944424] amdgpu 0000:03:00.0: ring page1 uses VM inv eng 5 on hub 1
[    2.944438] amdgpu 0000:03:00.0: ring uvd_0 uses VM inv eng 6 on hub 1
[    2.944452] amdgpu 0000:03:00.0: ring uvd_enc_0.0 uses VM inv eng 7 on h=
ub 1
[    2.944467] amdgpu 0000:03:00.0: ring uvd_enc_0.1 uses VM inv eng 8 on h=
ub 1
[    2.944482] amdgpu 0000:03:00.0: ring vce0 uses VM inv eng 9 on hub 1
[    2.944496] amdgpu 0000:03:00.0: ring vce1 uses VM inv eng 10 on hub 1
[    2.944510] amdgpu 0000:03:00.0: ring vce2 uses VM inv eng 11 on hub 1
[    2.945073] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:03:00.0 on
minor 1
[  288.676190] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=3D72560, emitted seq=3D72562
[  288.676350] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati=
on:
process glxgears pid 2963 thread glxgears:cs0 pid 2964
[  288.676358] amdgpu 0000:03:00.0: GPU reset begin!
[  288.759763] amdgpu 0000:03:00.0: GPU reset
[  289.208563] RIP: 0010:amdgpu_cs_ioctl+0xaa3/0x1320 [amdgpu]
[  289.208604]  ? amdgpu_cs_find_mapping+0x120/0x120 [amdgpu]
[  289.208647]  ? amdgpu_cs_find_mapping+0x120/0x120 [amdgpu]
[  289.208673]  amdgpu_drm_ioctl+0x4f/0x80 [amdgpu]
[  289.208690] Modules linked in: aufs overlay cmac bnep binfmt_misc
nls_iso8859_1 snd_hda_codec_ca0132 snd_hda_codec_realtek snd_hda_codec_gene=
ric
snd_hda_codec_hdmi ledtrig_audio snd_hda_intel snd_hda_codec snd_hda_core
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi btusb input_l=
eds
btrtl btbcm btintel bluetooth eeepc_wmi asus_wmi snd_seq ecdh_generic
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp sparse_keymap
kvm_intel intel_cstate intel_rapl_perf snd_seq_device snd_timer wmi_bmof snd
soundcore mei_me mei tpm_infineon mac_hid acpi_pad sch_fq_codel parport_pc
ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg hid_gener=
ic
usbhid hid dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel
aesni_intel amdgpu i915 kvmgt vfio_mdev mdev chash aes_x86_64 amd_iommu_v2
crypto_simd vfio_iommu_type1 gpu_sched cryptd glue_helper ttm vfio ahci lib=
ahci
i2c_i801 kvm mxm_wmi lpc_ich irqbypass i2c_algo_bit pata_acpi e1000e
drm_kms_helper syscopyarea sysfillrect
[  289.208743] RIP: 0010:amdgpu_cs_ioctl+0xaa3/0x1320 [amdgpu]
[  289.395715] amdgpu 0000:03:00.0: GPU reset succeeded, trying to resume
[  289.395813] [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* VRAM is los=
t!
[  289.969158] amdgpu 0000:03:00.0: GPU reset(2) succeeded!
[  289.969333] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[  289.969519] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!


>sudo journalctl -b | grep amdgpu

Same as dmesg output (after dropping timestamps), verified by vimdiff.

>Other

No swap, 144hz monitor, GPU was very hot to the touch considering it had on=
ly
run glxgears @ 144 fps for 5 minutes.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15676296934.9E061fd3.6933-- --===============1514995052== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1514995052==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 07 Sep 2019 03:48:56 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0010374679==" 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 CB95589F8B for ; Sat, 7 Sep 2019 03:48:57 +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 --===============0010374679== Content-Type: multipart/alternative; boundary="15678281375.C952C.25929" Content-Transfer-Encoding: 7bit --15678281375.C952C.25929 Date: Sat, 7 Sep 2019 03:48:57 +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=3D109955 --- Comment #96 from Rodney A Morris --- (In reply to Mauro Gaspari from comment #90) I am experiencing periodic lockups with various games, including Hearts of = Iron IV, BATTLETECH, and Stellaris all being played through Steam. Below is the most recent crash from playing less than 5 minutes of Hearts of Iron IV. >=20 > OS Info can be taken from neofetch: > System info: /:-------------:\=20=20=20=20=20=20=20=20=20=20 :-------------------:: --------------------------------=20 :-----------/shhOHbmp---:\ OS: Fedora release 30 (Thirty) x86_64= =20 /-----------omMMMNNNMMD ---: Kernel: 5.2.11-200.fc30.x86_64+debug=20 :-----------sMMMMNMNMP. ---: Uptime: 11 mins=20 :-----------:MMMdP------- ---\ Packages: 2198 (rpm), 27 (flatpak)=20 ,------------:MMMd-------- ---: Shell: bash 5.0.7=20 :------------:MMMd------- .---: Resolution: 2560x1440=20 :---- oNMMMMMMMMMNho .----: DE: GNOME 3.32.2=20 :-- .+shhhMMMmhhy++ .------/ WM: GNOME Shell=20 :- -------:MMMd--------------: WM Theme: Adwaita=20 :- --------/MMMd-------------; Theme: Adapta-Nokto-Eta [GTK2/3]=20 :- ------/hMMMy------------: Icons: Adwaita [GTK2/3]=20 :-- :dMNdhhdNMMNo------------; Terminal: tilix=20 :---:sdNMMMMNds:------------: CPU: Intel i7-6850K (12) @ 4.000GHz=20 :------:://:-------------:: GPU: AMD ATI Radeon RX Vega 56/64=20 :---------------------:// Memory: 1666MiB / 32045MiB=20 >=20 > Mesa info can be taken from this command: > glxinfo | grep "OpenGL version"=20 OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.5 >=20 > Game being played:=20 Hearts of Iron IV through Steam for Linux > Native or Wine or Wine+DXVK: Native >=20 > Crash type: Game crash? Full System freeze? System freeze but still can d= rop > to tty? Screen goes black suddenly while music continues plays for less than a minu= te; music begins to loop; and computer reboots. >=20 > DMESG output after the crash: > sudo dmesg | grep amdgpu Here is the pertinent part dmesg with kernel debugging turned on. Some of = the information the crash would not be captured by grepping amdgpu. Entire dme= sg provided as an attachment. [46957.810300] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting = for fences timed out or interrupted! [46962.941366] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D2446766, emitted seq=3D2446767 [46962.941453] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati= on: process hoi4 pid 24014 thread hoi4:cs0 pid 24015 [46962.941459] amdgpu 0000:06:00.0: GPU reset begin! [46962.942698] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D [46962.942700] WARNING: possible circular locking dependency detected [46962.942702] 5.2.11-200.fc30.x86_64+debug #1 Not tainted [46962.942704] ------------------------------------------------------ [46962.942705] kworker/3:0/20416 is trying to acquire lock: [46962.942708] 00000000a4a3593f (&(&ring->fence_drv.lock)->rlock){-.-.}, at: dma_fence_remove_callback+0x1a/0x60 [46962.942717]=20 but task is already holding lock: [46962.942718] 00000000d45cbf2b (&(&sched->job_list_lock)->rlock){-.-.}, at: drm_sched_stop+0x34/0x130 [gpu_sched] [46962.942724]=20 which lock already depends on the new lock. [46962.942725]=20 the existing dependency chain (in reverse order) is: [46962.942727]=20 -> #1 (&(&sched->job_list_lock)->rlock){-.-.}: [46962.942735] _raw_spin_lock_irqsave+0x49/0x83 [46962.942738] drm_sched_process_job+0x4d/0x180 [gpu_sched] [46962.942741] dma_fence_signal+0x111/0x1a0 [46962.942794] amdgpu_fence_process+0xa3/0x100 [amdgpu] [46962.942858] sdma_v4_0_process_trap_irq+0x8d/0xa0 [amdgpu] [46962.942918] amdgpu_irq_dispatch+0xc0/0x250 [amdgpu] [46962.942978] amdgpu_ih_process+0x8d/0x110 [amdgpu] [46962.943038] amdgpu_irq_handler+0x1b/0x50 [amdgpu] [46962.943043] __handle_irq_event_percpu+0x3f/0x290 [46962.943046] handle_irq_event_percpu+0x31/0x80 [46962.943048] handle_irq_event+0x34/0x51 [46962.943053] handle_edge_irq+0x83/0x1a0 [46962.943057] handle_irq+0x1c/0x30 [46962.943059] do_IRQ+0x61/0x120 [46962.943063] ret_from_intr+0x0/0x22 [46962.943067] cpuidle_enter_state+0xc9/0x450 [46962.943069] cpuidle_enter+0x29/0x40 [46962.943074] do_idle+0x1ec/0x280 [46962.943076] cpu_startup_entry+0x19/0x20 [46962.943079] start_secondary+0x189/0x1e0 [46962.943083] secondary_startup_64+0xa4/0xb0 [46962.943087]=20 -> #0 (&(&ring->fence_drv.lock)->rlock){-.-.}: [46962.943095] lock_acquire+0xa2/0x1b0 [46962.943105] _raw_spin_lock_irqsave+0x49/0x83 [46962.943109] dma_fence_remove_callback+0x1a/0x60 [46962.943114] drm_sched_stop+0x59/0x130 [gpu_sched] [46962.943225] amdgpu_device_pre_asic_reset+0x41/0x20c [amdgpu] [46962.943338] amdgpu_device_gpu_recover+0x77/0x788 [amdgpu] [46962.943413] amdgpu_job_timedout+0x109/0x130 [amdgpu] [46962.943418] drm_sched_job_timedout+0x40/0x70 [gpu_sched] [46962.943421] process_one_work+0x272/0x5e0 [46962.943423] worker_thread+0x50/0x3b0 [46962.943427] kthread+0x108/0x140 [46962.943431] ret_from_fork+0x3a/0x50 [46962.943432]=20 other info that might help us debug this: [46962.943435] Possible unsafe locking scenario: [46962.943437] CPU0 CPU1 [46962.943438] ---- ---- [46962.943439] lock(&(&sched->job_list_lock)->rlock); [46962.943441]=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 lock(&(&ring->fence_drv.lock)->rlock); [46962.943443]=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 lock(&(&sched->job_list_lock)->rlock); [46962.943445] lock(&(&ring->fence_drv.lock)->rlock); [46962.943447]=20 *** DEADLOCK *** [46962.943449] 5 locks held by kworker/3:0/20416: [46962.943450] #0: 0000000043c92b99 ((wq_completion)events){+.+.}, at: process_one_work+0x1e9/0x5e0 [46962.943456] #1: 000000000c360f0c ((work_completion)(&(&sched->work_tdr)->work)){+.+.}, at: process_one_work+0x1e9/0x5e0 [46962.943459] #2: 000000007a135814 (&adev->lock_reset){+.+.}, at: amdgpu_device_lock_adev+0x17/0x39 [amdgpu] [46962.943543] #3: 00000000e83f7d6b (&dqm->lock_hidden){+.+.}, at: kgd2kfd_pre_reset+0x30/0x60 [amdgpu] [46962.943614] #4: 00000000d45cbf2b (&(&sched->job_list_lock)->rlock){-.-.= }, at: drm_sched_stop+0x34/0x130 [gpu_sched] [46962.943620]=20 stack backtrace: [46962.943629] CPU: 3 PID: 20416 Comm: kworker/3:0 Not tainted 5.2.11-200.fc30.x86_64+debug #1 [46962.943631] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M.= /X99 Taichi, BIOS P1.80 04/06/2018 [46962.943636] Workqueue: events drm_sched_job_timedout [gpu_sched] [46962.943638] Call Trace: [46962.943648] dump_stack+0x85/0xc0 [46962.943654] print_circular_bug.cold+0x15c/0x195 [46962.943658] __lock_acquire+0x167c/0x1c90 [46962.943664] lock_acquire+0xa2/0x1b0 [46962.943668] ? dma_fence_remove_callback+0x1a/0x60 [46962.943674] _raw_spin_lock_irqsave+0x49/0x83 [46962.943677] ? dma_fence_remove_callback+0x1a/0x60 [46962.943680] dma_fence_remove_callback+0x1a/0x60 [46962.943684] drm_sched_stop+0x59/0x130 [gpu_sched] [46962.943764] amdgpu_device_pre_asic_reset+0x41/0x20c [amdgpu] [46962.943847] amdgpu_device_gpu_recover+0x77/0x788 [amdgpu] [46962.943923] amdgpu_job_timedout+0x109/0x130 [amdgpu] [46962.943930] drm_sched_job_timedout+0x40/0x70 [gpu_sched] [46962.943934] process_one_work+0x272/0x5e0 [46962.943938] worker_thread+0x50/0x3b0 [46962.943942] kthread+0x108/0x140 [46962.943945] ? process_one_work+0x5e0/0x5e0 [46962.943948] ? kthread_park+0x80/0x80 [46962.943952] ret_from_fork+0x3a/0x50 [46962.961034] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [46962.961044] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [46962.961048] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [46962.961051] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [46962.961149] pcieport 0000:00:03.0: AER: Device recovery failed [46963.955209] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring page1 timeou= t, signaled seq=3D95391072, emitted seq=3D95391072 [46963.955328] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati= on: process pid 0 thread pid 0 [46963.955336] amdgpu 0000:06:00.0: GPU reset begin! [46968.050083] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out [46973.170223] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-= 0] hw_done or flip_done timed out [46983.410080] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper= ]] *ERROR* [CRTC:47:crtc-0] flip_done timed out [46993.650098] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper= ]] *ERROR* [PLANE:45:plane-5] flip_done timed out [46993.962192] amdgpu: [powerplay] No response from smu [46993.962195] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x= 0, error code: 0x0 [46994.277773] amdgpu: [powerplay] No response from smu [46994.593416] amdgpu: [powerplay] No response from smu [46994.593420] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0= x1, error code: 0x0 [46994.908354] amdgpu: [powerplay] No response from smu [46995.223718] amdgpu: [powerplay] No response from smu [46995.223722] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0= x0, error code: 0x0 [46995.286504] [drm] REG_WAIT timeout 10us * 3500 tries - dce_mi_free_dmif line:634 [46995.286506] ------------[ cut here ]------------ [46995.286605] WARNING: CPU: 3 PID: 20416 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:329 generic_reg_wait.cold+0x31/0x53 [amdgpu] [46995.286606] Modules linked in: vhost_net vhost tap rfcomm xt_CHECKSUM xt_MASQUERADE tun bridge stp llc nf_conntrack_netbios_ns nf_conntrack_broad= cast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables bnep nct6775 hwmon_vid intel_rapl vfat fat arc4 x86_pkg_temp_ther= mal intel_powerclamp coretemp fuse kvm_intel kvm iwlmvm irqbypass iTCO_wdt iTCO_vendor_support mac80211 crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek ghash_clmulni_intel intel_cstate snd_hda_codec_generic iwlwifi snd_hda_codec_hdmi ledtrig_audio intel_uncore snd_hda_intel intel_rapl_perf cfg80211 snd_hda_codec btusb mxm_wmi snd_hda_core btrtl btb= cm snd_hwdep btintel snd_seq i2c_i801 lpc_ich bluetooth [46995.286626] snd_seq_device joydev snd_pcm ecdh_generic snd_timer rfkill= ecc mei_me snd mei soundcore pcc_cpufreq binfmt_misc auth_rpcgss sunrpc amdgpu amd_iommu_v2 gpu_sched ttm drm_kms_helper crc32c_intel igb uas drm usb_stor= age dca mpt3sas i2c_algo_bit e1000e nvme raid_class nvme_core scsi_transport_sas wmi [46995.286638] CPU: 3 PID: 20416 Comm: kworker/3:0 Not tainted 5.2.11-200.fc30.x86_64+debug #1 [46995.286639] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M.= /X99 Taichi, BIOS P1.80 04/06/2018 [46995.286643] Workqueue: events drm_sched_job_timedout [gpu_sched] [46995.286682] RIP: 0010:generic_reg_wait.cold+0x31/0x53 [amdgpu] [46995.286684] Code: 4c 24 18 44 89 fa 89 ee 48 c7 c7 78 93 80 c0 e8 45 fd = a0 ca 83 7b 20 01 0f 84 27 11 fe ff 48 c7 c7 70 92 80 c0 e8 2f fd a0 ca <0f> 0= b e9 14 11 fe ff 48 c7 c7 70 92 80 c0 89 54 24 04 e8 18 fd a0 [46995.286685] RSP: 0018:ffff9cd009b3f728 EFLAGS: 00010246 [46995.286687] RAX: 0000000000000024 RBX: ffff8ada6be8a780 RCX: 0000000000000006 [46995.286688] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8ada7ebd9c80 [46995.286689] RBP: 000000000000000a R08: 0000000000000001 R09: 0000000000000000 [46995.286690] R10: 0000000000000000 R11: 0000000000000000 R12: 00000000000035af [46995.286691] R13: 0000000000000dad R14: 0000000000000001 R15: 0000000000000dac [46995.286692] FS: 0000000000000000(0000) GS:ffff8ada7ea00000(0000) knlGS:0000000000000000 [46995.286694] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [46995.286695] CR2: 0000085777c78000 CR3: 00000003cb612005 CR4: 00000000003606e0 [46995.286696] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [46995.286697] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [46995.286698] Call Trace: [46995.286741] dce_mi_free_dmif+0xef/0x150 [amdgpu] [46995.286780] dce110_reset_hw_ctx_wrap+0x14a/0x1e0 [amdgpu] [46995.286819] dce110_apply_ctx_to_hw+0x4a/0x490 [amdgpu] [46995.286843] ? amdgpu_pm_compute_clocks.part.0+0xcb/0x610 [amdgpu] [46995.286882] ? dm_pp_apply_display_requirements+0x19e/0x1c0 [amdgpu] [46995.286920] dc_commit_state+0x262/0x580 [amdgpu] [46995.286925] ? vsnprintf+0x3aa/0x4f0 [46995.286965] amdgpu_dm_atomic_commit_tail+0xc34/0x1970 [amdgpu] [46995.286971] ? console_unlock+0x363/0x5d0 [46995.286976] ? __irq_work_queue_local+0x50/0x60 [46995.286977] ? irq_work_queue+0x4d/0x60 [46995.286979] ? wake_up_klogd+0x37/0x40 [46995.286984] ? wait_for_completion_timeout+0x4c/0x190 [46995.286987] ? _raw_spin_unlock_irq+0x29/0x40 [46995.286989] ? wait_for_completion_timeout+0x75/0x190 [46995.287016] ? commit_tail+0x3c/0x70 [drm_kms_helper] [46995.287021] commit_tail+0x3c/0x70 [drm_kms_helper] [46995.287026] drm_atomic_helper_commit+0xe3/0x150 [drm_kms_helper] [46995.287031] drm_atomic_helper_disable_all+0x14c/0x160 [drm_kms_helper] [46995.287035] drm_atomic_helper_suspend+0x66/0x100 [drm_kms_helper] [46995.287076] dm_suspend+0x20/0x60 [amdgpu] [46995.287098] amdgpu_device_ip_suspend_phase1+0x91/0xc0 [amdgpu] [46995.287123] amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu] [46995.287164] amdgpu_device_pre_asic_reset+0x1f7/0x20c [amdgpu] [46995.287204] amdgpu_device_gpu_recover+0x77/0x788 [amdgpu] [46995.287242] amdgpu_job_timedout+0x109/0x130 [amdgpu] [46995.287246] drm_sched_job_timedout+0x40/0x70 [gpu_sched] [46995.287249] process_one_work+0x272/0x5e0 [46995.287252] worker_thread+0x50/0x3b0 [46995.287256] kthread+0x108/0x140 [46995.287258] ? process_one_work+0x5e0/0x5e0 [46995.287260] ? kthread_park+0x80/0x80 [46995.287263] ret_from_fork+0x3a/0x50 [46995.287267] irq event stamp: 6288284 [46995.287269] hardirqs last enabled at (6288283): [] _raw_spin_unlock_irqrestore+0x4b/0x60 [46995.287271] hardirqs last disabled at (6288284): [] _raw_spin_lock_irqsave+0x23/0x83 [46995.287273] softirqs last enabled at (6288276): [] __do_softirq+0x35d/0x468 [46995.287276] softirqs last disabled at (6288269): [] irq_exit+0x102/0x110 [46995.287277] ---[ end trace 6a2158c4cfef5172 ]--- [46995.603082] amdgpu: [powerplay] No response from smu [46995.918767] amdgpu: [powerplay] No response from smu [46995.918770] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0= x1, error code: 0x0 [46996.233769] amdgpu: [powerplay] No response from smu [46996.549255] amdgpu: [powerplay] No response from smu [46996.549258] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0= x3, error code: 0x0 [46996.865320] amdgpu: [powerplay] No response from smu [46997.181203] amdgpu: [powerplay] No response from smu [46997.181206] amdgpu: [powerplay] Failed message: 0x9, input parameter: 0x= f4, error code: 0x0 [46997.495804] amdgpu: [powerplay] No response from smu [46997.811227] amdgpu: [powerplay] No response from smu [46997.811231] amdgpu: [powerplay] Failed message: 0xa, input parameter: 0xa0b000, error code: 0x0 [46998.126794] amdgpu: [powerplay] No response from smu [46998.442559] amdgpu: [powerplay] No response from smu [46998.442561] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x= 0, error code: 0x0 [46998.756884] amdgpu: [powerplay] No response from smu [46999.072680] amdgpu: [powerplay] No response from smu [46999.072684] amdgpu: [powerplay] Failed message: 0x4, input parameter: 0x= 400, error code: 0x0 [46999.388310] amdgpu: [powerplay] No response from smu [46999.704067] amdgpu: [powerplay] No response from smu [46999.704069] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0= x1, error code: 0x0 [47000.019626] amdgpu: [powerplay] No response from smu [47000.334247] amdgpu: [powerplay] No response from smu [47000.334251] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0= x0, error code: 0x0 [47000.350026] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [47000.350043] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [47000.350052] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [47000.350061] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [47000.350202] pcieport 0000:00:03.0: AER: Device recovery failed [47000.367437] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [47000.367443] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [47000.367444] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [47000.367446] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [47000.367486] pcieport 0000:00:03.0: AER: Device recovery failed [47000.384977] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [47000.384982] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [47000.384983] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [47000.384985] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [47000.385055] pcieport 0000:00:03.0: AER: Device recovery failed [47000.402521] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [47000.402530] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [47000.402532] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [47000.402535] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [47000.402578] pcieport 0000:00:03.0: AER: Device recovery failed [47000.420068] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [47000.420079] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [47000.420085] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [47000.420090] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [47000.420186] pcieport 0000:00:03.0: AER: Device recovery failed [47000.437608] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [47000.437617] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [47000.437621] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [47000.437625] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [47000.437726] pcieport 0000:00:03.0: AER: Device recovery failed [47000.455143] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [47000.455151] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [47000.455154] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [47000.455157] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [47000.455209] pcieport 0000:00:03.0: AER: Device recovery failed [47000.472688] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [47000.472698] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [47000.472703] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [47000.472708] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [47000.472826] pcieport 0000:00:03.0: AER: Device recovery failed [47000.490225] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [47000.490232] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [47000.490236] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [47000.490239] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [47000.490289] pcieport 0000:00:03.0: AER: Device recovery failed [47000.507760] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal) error received: 0000:00:03.0 [47000.735787] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [47000.735791] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [47000.735793] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [47000.735824] pcieport 0000:00:03.0: AER: Device recovery failed [47000.735826] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal) error received: 0000:00:03.0 > systemd logs output after the crash (If your system froze and you get logs > after reboot): Sep 06 08:36:58 ezra.blanchardmorris.net kernel: Command line: BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.11-200.fc30.x86_64+debug root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d= ebug=3D1 Sep 06 08:36:58 ezra.blanchardmorris.net kernel: Kernel command line: BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.11-200.fc30.x86_64+debug root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d= ebug=3D1 Sep 06 08:36:59 ezra.blanchardmorris.net dracut-cmdline[361]: Using kernel command line parameters: BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.11-200.fc30.x86_64+debug root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d= ebug=3D1 Sep 06 08:37:00 ezra.blanchardmorris.net kernel: [drm] amdgpu kernel modesetting enabled. Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: remove_conflicting_pci_framebuffers: bar 0: 0xe0000000 -> 0xefffffff Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: remove_conflicting_pci_framebuffers: bar 2: 0xf0000000 -> 0xf01fffff Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: remove_conflicting_pci_framebuffers: bar 5: 0xfb600000 -> 0xfb67ffff Sep 06 08:37:00 ezra.blanchardmorris.net kernel: fb0: switching to amdgpudr= mfb from EFI VGA Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: vgaar= b: deactivate vga console Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: No mo= re image in the PCI ROM Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: VRAM: 8176M 0x000000F400000000 - 0x000000F5FEFFFFFF (8176M used) Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF Sep 06 08:37:00 ezra.blanchardmorris.net kernel: [drm] amdgpu: 8176M of VRAM memory ready Sep 06 08:37:00 ezra.blanchardmorris.net kernel: [drm] amdgpu: 8176M of GTT memory ready. Sep 06 08:37:01 ezra.blanchardmorris.net kernel: fbcon: amdgpudrmfb (fb0) is primary device Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: fb0: amdgpudrmfb frame buffer device Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring = gfx uses VM inv eng 0 on hub 0 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring sdma0 uses VM inv eng 0 on hub 1 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring page0 uses VM inv eng 1 on hub 1 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring sdma1 uses VM inv eng 4 on hub 1 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring page1 uses VM inv eng 5 on hub 1 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring uvd_0 uses VM inv eng 6 on hub 1 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring uvd_enc_0.0 uses VM inv eng 7 on hub 1 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring uvd_enc_0.1 uses VM inv eng 8 on hub 1 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring = vce0 uses VM inv eng 9 on hub 1 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring = vce1 uses VM inv eng 10 on hub 1 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring = vce2 uses VM inv eng 11 on hub 1 Sep 06 08:37:01 ezra.blanchardmorris.net kernel: [drm] Initialized amdgpu 3.32.0 20150101 for 0000:06:00.0 on minor 0 Sep 06 08:37:48 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1969]: Kernel command line: BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.11-200.fc30.x86_64= +debug root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d= ebug=3D1 Sep 06 08:37:48 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1969]:= =20=20=20=20=20 loading driver: amdgpu Sep 06 08:37:48 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1969]: = (=3D=3D) Matched amdgpu as autoconfigured driver 0 Sep 06 08:37:48 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1969]: = (II) LoadModule: "amdgpu" Sep 06 08:37:48 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1969]: = (II) Loading /usr/lib64/xorg/modules/drivers/amdgpu_drv.so Sep 06 08:37:48 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1969]: = (II) Module amdgpu: vendor=3D"X.Org Foundation" Sep 06 08:37:48 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1969]:= =20=20=20=20=20 All GPUs supported by the amdgpu kernel driver Sep 06 16:13:18 ezra.blanchardmorris.net net.lutris.Lutris.desktop[2234]: 2019-09-06 16:13:18,530: GPU: 1002:687F 1002:0B36 using amdgpu drivers Sep 06 21:39:39 ezra.blanchardmorris.net kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out or interrupted! Sep 06 21:39:39 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D2446766, emitted seq=3D2= 446767 Sep 06 21:39:39 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process hoi4 pid 24014 thread hoi4:c= s0 pid 24015 Sep 06 21:39:39 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: GPU r= eset begin! Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20 amdgpu_fence_process+0xa3/0x100 [amdgpu] Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20 sdma_v4_0_process_trap_irq+0x8d/0xa0 [amdgpu] Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20 amdgpu_irq_dispatch+0xc0/0x250 [amdgpu] Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20 amdgpu_ih_process+0x8d/0x110 [amdgpu] Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20 amdgpu_irq_handler+0x1b/0x50 [amdgpu] Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20 amdgpu_device_pre_asic_reset+0x41/0x20c [amdgpu] Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20 amdgpu_device_gpu_recover+0x77/0x788 [amdgpu] Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20 amdgpu_job_timedout+0x109/0x130 [amdgpu] Sep 06 21:39:39 ezra.blanchardmorris.net kernel: #2: 000000007a135814 (&adev->lock_reset){+.+.}, at: amdgpu_device_lock_adev+0x17/0x39 [amdgpu] Sep 06 21:39:39 ezra.blanchardmorris.net kernel: #3: 00000000e83f7d6b (&dqm->lock_hidden){+.+.}, at: kgd2kfd_pre_reset+0x30/0x60 [amdgpu] Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20 amdgpu_device_pre_asic_reset+0x41/0x20c [amdgpu] Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20 amdgpu_device_gpu_recover+0x77/0x788 [amdgpu] Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20 amdgpu_job_timedout+0x109/0x130 [amdgpu] Sep 06 21:39:40 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring page1 timeout, signaled seq=3D95391072, emitted seq=3D95391072 Sep 06 21:39:40 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 Sep 06 21:39:40 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: GPU r= eset begin! Sep 06 21:39:49 ezra.blanchardmorris.net kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-0] hw_done or flip_done timed out Sep 06 21:40:10 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Sep 06 21:40:10 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x0, error code: 0x0 Sep 06 21:40:10 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Sep 06 21:40:10 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Sep 06 21:40:10 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed message: 0x42, input parameter: 0x1, error code: 0x0 Sep 06 21:40:11 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu I will try to run apitrace on Hearts of Iron IV to try to capture more information. Please let me know if I can be of further assistance in squas= hing this annoying bug, like providing crash information with the mesa debug packages installed. --=20 You are receiving this mail because: You are the assignee for the bug.= --15678281375.C952C.25929 Date: Sat, 7 Sep 2019 03:48:57 +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

Comme= nt # 96 on bug 10995= 5 from Rodney A Morris 
(In reply to Mauro Gaspari from comment #90)

I am experiencing periodic lockups with various games, including Hearts of =
Iron
IV, BATTLETECH, and Stellaris all being played through Steam.  Below is the
most recent crash from playing less than 5 minutes of Hearts of Iron IV.



>=20
> OS Info can be taken from neofetch:
> System info:

           /:-------------:\=20=20=20=20=20=20=20=20=20=20
       :-------------------::        --------------------------------=20
     :-----------/shhOHbmp---:\      OS: Fedora release 30 (Thirty) x86_64=
=20
   /-----------omMMMNNNMMD  ---:     Kernel: 5.2.11-200.fc30.x86_64+debug=20
  :-----------sMMMMNMNMP.    ---:    Uptime: 11 mins=20
 :-----------:MMMdP-------    ---\   Packages: 2198 (rpm), 27 (flatpak)=20
,------------:MMMd--------    ---:   Shell: bash 5.0.7=20
:------------:MMMd-------    .---:   Resolution: 2560x1440=20
:----    oNMMMMMMMMMNho     .----:   DE: GNOME 3.32.2=20
:--     .+shhhMMMmhhy++   .------/   WM: GNOME Shell=20
:-    -------:MMMd--------------:    WM Theme: Adwaita=20
:-   --------/MMMd-------------;     Theme: Adapta-Nokto-Eta [GTK2/3]=20
:-    ------/hMMMy------------:      Icons: Adwaita [GTK2/3]=20
:-- :dMNdhhdNMMNo------------;       Terminal: tilix=20
:---:sdNMMMMNds:------------:        CPU: Intel i7-6850K (12) @ 4.000GH=
z=20
:------:://:-------------::          GPU: AMD ATI Radeon RX Vega 56/64=20
:---------------------://            Memory: 1666MiB / 32045MiB=20

>=20
> Mesa info can be taken from this command:
> glxinfo | grep "OpenGL version" 

OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.5

>=20
> Game being played: 

Hearts of Iron IV through Steam for Linux

> Native or Wine or Wine+DXVK:

Native

>=20
> Crash type: Game crash? Full System freeze? System freeze but still ca=
n drop
> to tty?

Screen goes black suddenly while music continues plays for less than a minu=
te;
music begins to loop; and computer reboots.

>=20
> DMESG output after the crash:
> sudo dmesg | grep amdgpu

Here is the pertinent part dmesg with kernel debugging turned on.  Some of =
the
information the crash would not be captured by grepping amdgpu.  Entire dme=
sg
provided as an attachment.

[46957.810300] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting =
for
fences timed out or interrupted!
[46962.941366] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=3D2446766, emitted seq=3D2446767
[46962.941453] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati=
on:
process hoi4 pid 24014 thread hoi4:cs0 pid 24015
[46962.941459] amdgpu 0000:06:00.0: GPU reset begin!

[46962.942698] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
[46962.942700] WARNING: possible circular locking dependency detected
[46962.942702] 5.2.11-200.fc30.x86_64+debug #1 Not tainted
[46962.942704] ------------------------------------------------------
[46962.942705] kworker/3:0/20416 is trying to acquire lock:
[46962.942708] 00000000a4a3593f (&(&ring->fence_drv.lock)->rl=
ock){-.-.}, at:
dma_fence_remove_callback+0x1a/0x60
[46962.942717]=20
               but task is already holding lock:
[46962.942718] 00000000d45cbf2b (&(&sched->job_list_lock)->rl=
ock){-.-.}, at:
drm_sched_stop+0x34/0x130 [gpu_sched]
[46962.942724]=20
               which lock already depends on the new lock.

[46962.942725]=20
               the existing dependency chain (in reverse order) is:
[46962.942727]=20
               -> #1 (&(&sched->job_list_lock)->rlock){-.-=
.}:
[46962.942735]        _raw_spin_lock_irqsave+0x49/0x83
[46962.942738]        drm_sched_process_job+0x4d/0x180 [gpu_sched]
[46962.942741]        dma_fence_signal+0x111/0x1a0
[46962.942794]        amdgpu_fence_process+0xa3/0x100 [amdgpu]
[46962.942858]        sdma_v4_0_process_trap_irq+0x8d/0xa0 [amdgpu]
[46962.942918]        amdgpu_irq_dispatch+0xc0/0x250 [amdgpu]
[46962.942978]        amdgpu_ih_process+0x8d/0x110 [amdgpu]
[46962.943038]        amdgpu_irq_handler+0x1b/0x50 [amdgpu]
[46962.943043]        __handle_irq_event_percpu+0x3f/0x290
[46962.943046]        handle_irq_event_percpu+0x31/0x80
[46962.943048]        handle_irq_event+0x34/0x51
[46962.943053]        handle_edge_irq+0x83/0x1a0
[46962.943057]        handle_irq+0x1c/0x30
[46962.943059]        do_IRQ+0x61/0x120
[46962.943063]        ret_from_intr+0x0/0x22
[46962.943067]        cpuidle_enter_state+0xc9/0x450
[46962.943069]        cpuidle_enter+0x29/0x40
[46962.943074]        do_idle+0x1ec/0x280
[46962.943076]        cpu_startup_entry+0x19/0x20
[46962.943079]        start_secondary+0x189/0x1e0
[46962.943083]        secondary_startup_64+0xa4/0xb0
[46962.943087]=20
               -> #0 (&(&ring->fence_drv.lock)->rlock){-.-=
.}:
[46962.943095]        lock_acquire+0xa2/0x1b0
[46962.943105]        _raw_spin_lock_irqsave+0x49/0x83
[46962.943109]        dma_fence_remove_callback+0x1a/0x60
[46962.943114]        drm_sched_stop+0x59/0x130 [gpu_sched]
[46962.943225]        amdgpu_device_pre_asic_reset+0x41/0x20c [amdgpu]
[46962.943338]        amdgpu_device_gpu_recover+0x77/0x788 [amdgpu]
[46962.943413]        amdgpu_job_timedout+0x109/0x130 [amdgpu]
[46962.943418]        drm_sched_job_timedout+0x40/0x70 [gpu_sched]
[46962.943421]        process_one_work+0x272/0x5e0
[46962.943423]        worker_thread+0x50/0x3b0
[46962.943427]        kthread+0x108/0x140
[46962.943431]        ret_from_fork+0x3a/0x50
[46962.943432]=20
               other info that might help us debug this:

[46962.943435]  Possible unsafe locking scenario:

[46962.943437]        CPU0                    CPU1
[46962.943438]        ----                    ----
[46962.943439]   lock(&(&sched->job_list_lock)->rlock);
[46962.943441]=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20
lock(&(&ring->fence_drv.lock)->rlock);
[46962.943443]=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20
lock(&(&sched->job_list_lock)->rlock);
[46962.943445]   lock(&(&ring->fence_drv.lock)->rlock);
[46962.943447]=20
                *** DEADLOCK ***

[46962.943449] 5 locks held by kworker/3:0/20416:
[46962.943450]  #0: 0000000043c92b99 ((wq_completion)events){+.+.}, at:
process_one_work+0x1e9/0x5e0
[46962.943456]  #1: 000000000c360f0c
((work_completion)(&(&sched->work_tdr)->work)){+.+.}, at:
process_one_work+0x1e9/0x5e0
[46962.943459]  #2: 000000007a135814 (&adev->lock_reset){+.+.}, at:
amdgpu_device_lock_adev+0x17/0x39 [amdgpu]
[46962.943543]  #3: 00000000e83f7d6b (&dqm->lock_hidden){+.+.}, at:
kgd2kfd_pre_reset+0x30/0x60 [amdgpu]
[46962.943614]  #4: 00000000d45cbf2b (&(&sched->job_list_lock)-&=
gt;rlock){-.-.},
at: drm_sched_stop+0x34/0x130 [gpu_sched]
[46962.943620]=20
               stack backtrace:
[46962.943629] CPU: 3 PID: 20416 Comm: kworker/3:0 Not tainted
5.2.11-200.fc30.x86_64+debug #1
[46962.943631] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M.=
/X99
Taichi, BIOS P1.80 04/06/2018
[46962.943636] Workqueue: events drm_sched_job_timedout [gpu_sched]
[46962.943638] Call Trace:
[46962.943648]  dump_stack+0x85/0xc0
[46962.943654]  print_circular_bug.cold+0x15c/0x195
[46962.943658]  __lock_acquire+0x167c/0x1c90
[46962.943664]  lock_acquire+0xa2/0x1b0
[46962.943668]  ? dma_fence_remove_callback+0x1a/0x60
[46962.943674]  _raw_spin_lock_irqsave+0x49/0x83
[46962.943677]  ? dma_fence_remove_callback+0x1a/0x60
[46962.943680]  dma_fence_remove_callback+0x1a/0x60
[46962.943684]  drm_sched_stop+0x59/0x130 [gpu_sched]
[46962.943764]  amdgpu_device_pre_asic_reset+0x41/0x20c [amdgpu]
[46962.943847]  amdgpu_device_gpu_recover+0x77/0x788 [amdgpu]
[46962.943923]  amdgpu_job_timedout+0x109/0x130 [amdgpu]
[46962.943930]  drm_sched_job_timedout+0x40/0x70 [gpu_sched]
[46962.943934]  process_one_work+0x272/0x5e0
[46962.943938]  worker_thread+0x50/0x3b0
[46962.943942]  kthread+0x108/0x140
[46962.943945]  ? process_one_work+0x5e0/0x5e0
[46962.943948]  ? kthread_park+0x80/0x80
[46962.943952]  ret_from_fork+0x3a/0x50
[46962.961034] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[46962.961044] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[46962.961048] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[46962.961051] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[46962.961149] pcieport 0000:00:03.0: AER: Device recovery failed
[46963.955209] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring page1 timeou=
t,
signaled seq=3D95391072, emitted seq=3D95391072
[46963.955328] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati=
on:
process  pid 0 thread  pid 0
[46963.955336] amdgpu 0000:06:00.0: GPU reset begin!
[46968.050083] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
*ERROR* [CRTC:47:crtc-0] flip_done timed out
[46973.170223] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-=
0]
hw_done or flip_done timed out
[46983.410080] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper=
]]
*ERROR* [CRTC:47:crtc-0] flip_done timed out
[46993.650098] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper=
]]
*ERROR* [PLANE:45:plane-5] flip_done timed out
[46993.962192] amdgpu: [powerplay] No response from smu
[46993.962195] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x=
0,
error code: 0x0
[46994.277773] amdgpu: [powerplay] No response from smu
[46994.593416] amdgpu: [powerplay] No response from smu
[46994.593420] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0=
x1,
error code: 0x0
[46994.908354] amdgpu: [powerplay] No response from smu
[46995.223718] amdgpu: [powerplay] No response from smu
[46995.223722] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0=
x0,
error code: 0x0
[46995.286504] [drm] REG_WAIT timeout 10us * 3500 tries - dce_mi_free_dmif
line:634
[46995.286506] ------------[ cut here ]------------
[46995.286605] WARNING: CPU: 3 PID: 20416 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:329
generic_reg_wait.cold+0x31/0x53 [amdgpu]
[46995.286606] Modules linked in: vhost_net vhost tap rfcomm xt_CHECKSUM
xt_MASQUERADE tun bridge stp llc nf_conntrack_netbios_ns nf_conntrack_broad=
cast
xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4
xt_conntrack ebtable_nat ip6table_nat ip6table_mangle ip6table_raw
ip6table_security iptable_nat nf_nat iptable_mangle iptable_raw
iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set
nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter
ip_tables bnep nct6775 hwmon_vid intel_rapl vfat fat arc4 x86_pkg_temp_ther=
mal
intel_powerclamp coretemp fuse kvm_intel kvm iwlmvm irqbypass iTCO_wdt
iTCO_vendor_support mac80211 crct10dif_pclmul crc32_pclmul
snd_hda_codec_realtek ghash_clmulni_intel intel_cstate snd_hda_codec_generic
iwlwifi snd_hda_codec_hdmi ledtrig_audio intel_uncore snd_hda_intel
intel_rapl_perf cfg80211 snd_hda_codec btusb mxm_wmi snd_hda_core btrtl btb=
cm
snd_hwdep btintel snd_seq i2c_i801 lpc_ich bluetooth
[46995.286626]  snd_seq_device joydev snd_pcm ecdh_generic snd_timer rfkill=
 ecc
mei_me snd mei soundcore pcc_cpufreq binfmt_misc auth_rpcgss sunrpc amdgpu
amd_iommu_v2 gpu_sched ttm drm_kms_helper crc32c_intel igb uas drm usb_stor=
age
dca mpt3sas i2c_algo_bit e1000e nvme raid_class nvme_core scsi_transport_sas
wmi
[46995.286638] CPU: 3 PID: 20416 Comm: kworker/3:0 Not tainted
5.2.11-200.fc30.x86_64+debug #1
[46995.286639] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M.=
/X99
Taichi, BIOS P1.80 04/06/2018
[46995.286643] Workqueue: events drm_sched_job_timedout [gpu_sched]
[46995.286682] RIP: 0010:generic_reg_wait.cold+0x31/0x53 [amdgpu]
[46995.286684] Code: 4c 24 18 44 89 fa 89 ee 48 c7 c7 78 93 80 c0 e8 45 fd =
a0
ca 83 7b 20 01 0f 84 27 11 fe ff 48 c7 c7 70 92 80 c0 e8 2f fd a0 ca <0f=
> 0b e9
14 11 fe ff 48 c7 c7 70 92 80 c0 89 54 24 04 e8 18 fd a0
[46995.286685] RSP: 0018:ffff9cd009b3f728 EFLAGS: 00010246
[46995.286687] RAX: 0000000000000024 RBX: ffff8ada6be8a780 RCX:
0000000000000006
[46995.286688] RDX: 0000000000000000 RSI: 0000000000000001 RDI:
ffff8ada7ebd9c80
[46995.286689] RBP: 000000000000000a R08: 0000000000000001 R09:
0000000000000000
[46995.286690] R10: 0000000000000000 R11: 0000000000000000 R12:
00000000000035af
[46995.286691] R13: 0000000000000dad R14: 0000000000000001 R15:
0000000000000dac
[46995.286692] FS:  0000000000000000(0000) GS:ffff8ada7ea00000(0000)
knlGS:0000000000000000
[46995.286694] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[46995.286695] CR2: 0000085777c78000 CR3: 00000003cb612005 CR4:
00000000003606e0
[46995.286696] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[46995.286697] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
0000000000000400
[46995.286698] Call Trace:
[46995.286741]  dce_mi_free_dmif+0xef/0x150 [amdgpu]
[46995.286780]  dce110_reset_hw_ctx_wrap+0x14a/0x1e0 [amdgpu]
[46995.286819]  dce110_apply_ctx_to_hw+0x4a/0x490 [amdgpu]
[46995.286843]  ? amdgpu_pm_compute_clocks.part.0+0xcb/0x610 [amdgpu]
[46995.286882]  ? dm_pp_apply_display_requirements+0x19e/0x1c0 [amdgpu]
[46995.286920]  dc_commit_state+0x262/0x580 [amdgpu]
[46995.286925]  ? vsnprintf+0x3aa/0x4f0
[46995.286965]  amdgpu_dm_atomic_commit_tail+0xc34/0x1970 [amdgpu]
[46995.286971]  ? console_unlock+0x363/0x5d0
[46995.286976]  ? __irq_work_queue_local+0x50/0x60
[46995.286977]  ? irq_work_queue+0x4d/0x60
[46995.286979]  ? wake_up_klogd+0x37/0x40
[46995.286984]  ? wait_for_completion_timeout+0x4c/0x190
[46995.286987]  ? _raw_spin_unlock_irq+0x29/0x40
[46995.286989]  ? wait_for_completion_timeout+0x75/0x190
[46995.287016]  ? commit_tail+0x3c/0x70 [drm_kms_helper]
[46995.287021]  commit_tail+0x3c/0x70 [drm_kms_helper]
[46995.287026]  drm_atomic_helper_commit+0xe3/0x150 [drm_kms_helper]
[46995.287031]  drm_atomic_helper_disable_all+0x14c/0x160 [drm_kms_helper]
[46995.287035]  drm_atomic_helper_suspend+0x66/0x100 [drm_kms_helper]
[46995.287076]  dm_suspend+0x20/0x60 [amdgpu]
[46995.287098]  amdgpu_device_ip_suspend_phase1+0x91/0xc0 [amdgpu]
[46995.287123]  amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu]
[46995.287164]  amdgpu_device_pre_asic_reset+0x1f7/0x20c [amdgpu]
[46995.287204]  amdgpu_device_gpu_recover+0x77/0x788 [amdgpu]
[46995.287242]  amdgpu_job_timedout+0x109/0x130 [amdgpu]
[46995.287246]  drm_sched_job_timedout+0x40/0x70 [gpu_sched]
[46995.287249]  process_one_work+0x272/0x5e0
[46995.287252]  worker_thread+0x50/0x3b0
[46995.287256]  kthread+0x108/0x140
[46995.287258]  ? process_one_work+0x5e0/0x5e0
[46995.287260]  ? kthread_park+0x80/0x80
[46995.287263]  ret_from_fork+0x3a/0x50
[46995.287267] irq event stamp: 6288284
[46995.287269] hardirqs last  enabled at (6288283): [<ffffffff8bb04d8b&g=
t;]
_raw_spin_unlock_irqrestore+0x4b/0x60
[46995.287271] hardirqs last disabled at (6288284): [<ffffffff8bb05533&g=
t;]
_raw_spin_lock_irqsave+0x23/0x83
[46995.287273] softirqs last  enabled at (6288276): [<ffffffff8be0035d&g=
t;]
__do_softirq+0x35d/0x468
[46995.287276] softirqs last disabled at (6288269): [<ffffffff8b0f07a2&g=
t;]
irq_exit+0x102/0x110
[46995.287277] ---[ end trace 6a2158c4cfef5172 ]---
[46995.603082] amdgpu: [powerplay] No response from smu
[46995.918767] amdgpu: [powerplay] No response from smu
[46995.918770] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0=
x1,
error code: 0x0
[46996.233769] amdgpu: [powerplay] No response from smu
[46996.549255] amdgpu: [powerplay] No response from smu
[46996.549258] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0=
x3,
error code: 0x0
[46996.865320] amdgpu: [powerplay] No response from smu
[46997.181203] amdgpu: [powerplay] No response from smu
[46997.181206] amdgpu: [powerplay] Failed message: 0x9, input parameter: 0x=
f4,
error code: 0x0
[46997.495804] amdgpu: [powerplay] No response from smu
[46997.811227] amdgpu: [powerplay] No response from smu
[46997.811231] amdgpu: [powerplay] Failed message: 0xa, input parameter:
0xa0b000, error code: 0x0
[46998.126794] amdgpu: [powerplay] No response from smu
[46998.442559] amdgpu: [powerplay] No response from smu
[46998.442561] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x=
0,
error code: 0x0
[46998.756884] amdgpu: [powerplay] No response from smu
[46999.072680] amdgpu: [powerplay] No response from smu
[46999.072684] amdgpu: [powerplay] Failed message: 0x4, input parameter: 0x=
400,
error code: 0x0
[46999.388310] amdgpu: [powerplay] No response from smu
[46999.704067] amdgpu: [powerplay] No response from smu
[46999.704069] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0=
x1,
error code: 0x0
[47000.019626] amdgpu: [powerplay] No response from smu
[47000.334247] amdgpu: [powerplay] No response from smu
[47000.334251] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0=
x0,
error code: 0x0
[47000.350026] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[47000.350043] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[47000.350052] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[47000.350061] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[47000.350202] pcieport 0000:00:03.0: AER: Device recovery failed
[47000.367437] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[47000.367443] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[47000.367444] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[47000.367446] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[47000.367486] pcieport 0000:00:03.0: AER: Device recovery failed
[47000.384977] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[47000.384982] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[47000.384983] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[47000.384985] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[47000.385055] pcieport 0000:00:03.0: AER: Device recovery failed
[47000.402521] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[47000.402530] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[47000.402532] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[47000.402535] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[47000.402578] pcieport 0000:00:03.0: AER: Device recovery failed
[47000.420068] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[47000.420079] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[47000.420085] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[47000.420090] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[47000.420186] pcieport 0000:00:03.0: AER: Device recovery failed
[47000.437608] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[47000.437617] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[47000.437621] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[47000.437625] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[47000.437726] pcieport 0000:00:03.0: AER: Device recovery failed
[47000.455143] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[47000.455151] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[47000.455154] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[47000.455157] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[47000.455209] pcieport 0000:00:03.0: AER: Device recovery failed
[47000.472688] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[47000.472698] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[47000.472703] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[47000.472708] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[47000.472826] pcieport 0000:00:03.0: AER: Device recovery failed
[47000.490225] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[47000.490232] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[47000.490236] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[47000.490239] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[47000.490289] pcieport 0000:00:03.0: AER: Device recovery failed
[47000.507760] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal)
error received: 0000:00:03.0
[47000.735787] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[47000.735791] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[47000.735793] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[47000.735824] pcieport 0000:00:03.0: AER: Device recovery failed
[47000.735826] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal)
error received: 0000:00:03.0


> systemd logs output after the crash (If your sys=
tem froze and you get logs
> after reboot):

Sep 06 08:36:58 ezra.blanchardmorris.net kernel: Command line:
BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.11-200.fc30.x86_64+debug
root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro
resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d=
ebug=3D1
Sep 06 08:36:58 ezra.blanchardmorris.net kernel: Kernel command line:
BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.11-200.fc30.x86_64+debug
root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro
resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d=
ebug=3D1
Sep 06 08:36:59 ezra.blanchardmorris.net dracut-cmdline[361]: Using kernel
command line parameters:
BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.11-200.fc30.x86_64+debug
root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro
resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d=
ebug=3D1
Sep 06 08:37:00 ezra.blanchardmorris.net kernel: [drm] amdgpu kernel
modesetting enabled.
Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0:
remove_conflicting_pci_framebuffers: bar 0: 0xe0000000 -> 0xefffffff
Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0:
remove_conflicting_pci_framebuffers: bar 2: 0xf0000000 -> 0xf01fffff
Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0:
remove_conflicting_pci_framebuffers: bar 5: 0xfb600000 -> 0xfb67ffff
Sep 06 08:37:00 ezra.blanchardmorris.net kernel: fb0: switching to amdgpudr=
mfb
from EFI VGA
Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: vgaar=
b:
deactivate vga console
Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: No mo=
re
image in the PCI ROM
Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: VRAM:
8176M 0x000000F400000000 - 0x000000F5FEFFFFFF (8176M used)
Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: GART:
512M 0x0000000000000000 - 0x000000001FFFFFFF
Sep 06 08:37:00 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: AGP:
267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF
Sep 06 08:37:00 ezra.blanchardmorris.net kernel: [drm] amdgpu: 8176M of VRAM
memory ready
Sep 06 08:37:00 ezra.blanchardmorris.net kernel: [drm] amdgpu: 8176M of GTT
memory ready.
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: fbcon: amdgpudrmfb (fb0) is
primary device
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: fb0:
amdgpudrmfb frame buffer device
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring =
gfx
uses VM inv eng 0 on hub 0
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.0.0 uses VM inv eng 1 on hub 0
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.1.0 uses VM inv eng 4 on hub 0
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.2.0 uses VM inv eng 5 on hub 0
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.3.0 uses VM inv eng 6 on hub 0
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.0.1 uses VM inv eng 7 on hub 0
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.1.1 uses VM inv eng 8 on hub 0
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.2.1 uses VM inv eng 9 on hub 0
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.3.1 uses VM inv eng 10 on hub 0
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
kiq_2.1.0 uses VM inv eng 11 on hub 0
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
sdma0 uses VM inv eng 0 on hub 1
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
page0 uses VM inv eng 1 on hub 1
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
sdma1 uses VM inv eng 4 on hub 1
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
page1 uses VM inv eng 5 on hub 1
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
uvd_0 uses VM inv eng 6 on hub 1
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
uvd_enc_0.0 uses VM inv eng 7 on hub 1
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
uvd_enc_0.1 uses VM inv eng 8 on hub 1
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring =
vce0
uses VM inv eng 9 on hub 1
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring =
vce1
uses VM inv eng 10 on hub 1
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring =
vce2
uses VM inv eng 11 on hub 1
Sep 06 08:37:01 ezra.blanchardmorris.net kernel: [drm] Initialized amdgpu
3.32.0 20150101 for 0000:06:00.0 on minor 0
Sep 06 08:37:48 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1969]:
Kernel command line: BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.11-200.fc30.x86_64=
+debug
root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro
resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d=
ebug=3D1
Sep 06 08:37:48 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1969]:=
=20=20=20=20=20
   loading driver: amdgpu
Sep 06 08:37:48 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1969]: =
(=3D=3D)
Matched amdgpu as autoconfigured driver 0
Sep 06 08:37:48 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1969]: =
(II)
LoadModule: "amdgpu"
Sep 06 08:37:48 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1969]: =
(II)
Loading /usr/lib64/xorg/modules/drivers/amdgpu_drv.so
Sep 06 08:37:48 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1969]: =
(II)
Module amdgpu: vendor=3D"X.Org Foundation"
Sep 06 08:37:48 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1969]:=
=20=20=20=20=20
   All GPUs supported by the amdgpu kernel driver
Sep 06 16:13:18 ezra.blanchardmorris.net net.lutris.Lutris.desktop[2234]:
2019-09-06 16:13:18,530: GPU: 1002:687F 1002:0B36 using amdgpu drivers
Sep 06 21:39:39 ezra.blanchardmorris.net kernel:
[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed
out or interrupted!
Sep 06 21:39:39 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D2446766, emitted seq=3D2=
446767
Sep 06 21:39:39 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout
[amdgpu]] *ERROR* Process information: process hoi4 pid 24014 thread hoi4:c=
s0
pid 24015
Sep 06 21:39:39 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: GPU r=
eset
begin!
Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20
amdgpu_fence_process+0xa3/0x100 [amdgpu]
Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20
sdma_v4_0_process_trap_irq+0x8d/0xa0 [amdgpu]
Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20
amdgpu_irq_dispatch+0xc0/0x250 [amdgpu]
Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20
amdgpu_ih_process+0x8d/0x110 [amdgpu]
Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20
amdgpu_irq_handler+0x1b/0x50 [amdgpu]
Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20
amdgpu_device_pre_asic_reset+0x41/0x20c [amdgpu]
Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20
amdgpu_device_gpu_recover+0x77/0x788 [amdgpu]
Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20=20=20=20=20=20=20
amdgpu_job_timedout+0x109/0x130 [amdgpu]
Sep 06 21:39:39 ezra.blanchardmorris.net kernel:  #2: 000000007a135814
(&adev->lock_reset){+.+.}, at: amdgpu_device_lock_adev+0x17/0x39 [am=
dgpu]
Sep 06 21:39:39 ezra.blanchardmorris.net kernel:  #3: 00000000e83f7d6b
(&dqm->lock_hidden){+.+.}, at: kgd2kfd_pre_reset+0x30/0x60 [amdgpu]
Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20
amdgpu_device_pre_asic_reset+0x41/0x20c [amdgpu]
Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20
amdgpu_device_gpu_recover+0x77/0x788 [amdgpu]
Sep 06 21:39:39 ezra.blanchardmorris.net kernel:=20
amdgpu_job_timedout+0x109/0x130 [amdgpu]
Sep 06 21:39:40 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout
[amdgpu]] *ERROR* ring page1 timeout, signaled seq=3D95391072, emitted
seq=3D95391072
Sep 06 21:39:40 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout
[amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
Sep 06 21:39:40 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: GPU r=
eset
begin!
Sep 06 21:39:49 ezra.blanchardmorris.net kernel: [drm:amdgpu_dm_atomic_check
[amdgpu]] *ERROR* [CRTC:47:crtc-0] hw_done or flip_done timed out
Sep 06 21:40:10 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Sep 06 21:40:10 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed
message: 0xe, input parameter: 0x0, error code: 0x0
Sep 06 21:40:10 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Sep 06 21:40:10 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Sep 06 21:40:10 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed
message: 0x42, input parameter: 0x1, error code: 0x0
Sep 06 21:40:11 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu

I will try to run apitrace on Hearts of Iron IV to try to capture more
information.  Please let me know if I can be of further assistance in squas=
hing
this annoying bug, like providing crash information with the mesa debug
packages installed.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15678281375.C952C.25929-- --===============0010374679== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0010374679==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 07 Sep 2019 03:50:40 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0784460212==" 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 545C06E0C4 for ; Sat, 7 Sep 2019 03:50:41 +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 --===============0784460212== Content-Type: multipart/alternative; boundary="15678282414.7D89.27716" Content-Transfer-Encoding: 7bit --15678282414.7D89.27716 Date: Sat, 7 Sep 2019 03:50:41 +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=3D109955 --- Comment #97 from Rodney A Morris --- Created attachment 145290 --> https://bugs.freedesktop.org/attachment.cgi?id=3D145290&action=3Dedit dmesg for crash dmesg from crash while playing Hearts of Iron IV using Steam. Related to comment #96. --=20 You are receiving this mail because: You are the assignee for the bug.= --15678282414.7D89.27716 Date: Sat, 7 Sep 2019 03:50:41 +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

Comme= nt # 97 on bug 10995= 5 from Rodney A Morris 
Created attachment 145290 [details]
dmesg for crash

dmesg from crash while playing Hearts of Iron IV using Steam.  Related to
comment #96.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15678282414.7D89.27716-- --===============0784460212== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0784460212==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 12 Sep 2019 20:08:21 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0427810321==" 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 C492D6EE20 for ; Thu, 12 Sep 2019 20:08:21 +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 --===============0427810321== Content-Type: multipart/alternative; boundary="15683189012.Fb60ff5C.32218" Content-Transfer-Encoding: 7bit --15683189012.Fb60ff5C.32218 Date: Thu, 12 Sep 2019 20:08:21 +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=3D109955 --- Comment #98 from koala_man --- (In reply to koala_man from comment #95) > I am also seeing this issue on my stock Ubuntu.=20 In my case it appears to have been faulty hardware. I tried it on Windows 10 with the latest drivers and still got crashes and reboots. Performance throttling did not help. I swapped out the GPU and haven't seen any crashes since. --=20 You are receiving this mail because: You are the assignee for the bug.= --15683189012.Fb60ff5C.32218 Date: Thu, 12 Sep 2019 20:08:21 +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

Comme= nt # 98 on bug 10995= 5 from koala_man 
(In reply to koala_man from comment #95)
> I am also seeing this issue on my stock Ubuntu. =


In my case it appears to have been faulty hardware. I tried it on Windows 10
with the latest drivers and still got crashes and reboots. Performance
throttling did not help. I swapped out the GPU and haven't seen any crashes
since.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15683189012.Fb60ff5C.32218-- --===============0427810321== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0427810321==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 15 Sep 2019 01:16:19 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1176189894==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 0044F6F56F for ; Sun, 15 Sep 2019 01:17:47 +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 --===============1176189894== Content-Type: multipart/alternative; boundary="15685102671.6Cd6.5743" Content-Transfer-Encoding: 7bit --15685102671.6Cd6.5743 Date: Sun, 15 Sep 2019 01:17:47 +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=3D109955 --- Comment #99 from Rodney A Morris --- Created attachment 145366 --> https://bugs.freedesktop.org/attachment.cgi?id=3D145366&action=3Dedit apitrace of Hearts of Iron IV hard lock Apitrace from hard lock playing Hearts of Iron IV without Steam. The replay from this trace will hard lock the computer, though inconsistently. I've replayed the trace three times. The replay hard locked computer one time. --=20 You are receiving this mail because: You are the assignee for the bug.= --15685102671.6Cd6.5743 Date: Sun, 15 Sep 2019 01:17:47 +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

Comme= nt # 99 on bug 10995= 5 from Rodney A Morris 
Created =
attachment 145366 [details]
apitrace of Hearts of Iron IV hard lock

Apitrace from hard lock playing Hearts of Iron IV without Steam.  The replay
from this trace will hard lock the computer, though inconsistently.  I've
replayed the trace three times. The replay hard locked computer one time.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15685102671.6Cd6.5743-- --===============1176189894== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1176189894==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 15 Sep 2019 01:20:36 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0211457309==" 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 9F8066F56F for ; Sun, 15 Sep 2019 01:20:51 +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 --===============0211457309== Content-Type: multipart/alternative; boundary="15685104500.CE977.9634" Content-Transfer-Encoding: 7bit --15685104500.CE977.9634 Date: Sun, 15 Sep 2019 01:20:50 +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=3D109955 --- Comment #100 from Rodney A Morris --- (In reply to Rodney A Morris from comment #99) > Created attachment 145366 [details] > apitrace of Hearts of Iron IV hard lock >=20 > Apitrace from hard lock playing Hearts of Iron IV without Steam. The rep= lay > from this trace will hard lock the computer, though inconsistently. I've > replayed the trace three times. The replay hard locked computer one time. neofetch from hardlock: /:-------------:\=20=20=20=20=20=20=20=20=20=20 :-------------------:: --------------------------------=20 :-----------/shhOHbmp---:\ OS: Fedora release 30 (Thirty) x86_64= =20 /-----------omMMMNNNMMD ---: Kernel: 5.2.13-200.fc30.x86_64=20 :-----------sMMMMNMNMP. ---: Uptime: 25 mins=20 :-----------:MMMdP------- ---\ Packages: 2202 (rpm), 27 (flatpak)=20 ,------------:MMMd-------- ---: Shell: bash 5.0.7=20 :------------:MMMd------- .---: Resolution: 2560x1440=20 :---- oNMMMMMMMMMNho .----: DE: GNOME 3.32.2=20 :-- .+shhhMMMmhhy++ .------/ WM: GNOME Shell=20 :- -------:MMMd--------------: WM Theme: Adwaita=20 :- --------/MMMd-------------; Theme: Adapta-Nokto-Eta [GTK2/3]=20 :- ------/hMMMy------------: Icons: Adwaita [GTK2/3]=20 :-- :dMNdhhdNMMNo------------; Terminal: tilix=20 :---:sdNMMMMNds:------------: CPU: Intel i7-6850K (12) @ 4.000GHz=20 :------:://:-------------:: GPU: AMD ATI Radeon RX Vega 56/64=20 :---------------------:// Memory: 2478MiB / 32084MiB=20 OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6 Note: hard lock replayed occurred when the Discord flatpak is also running. --=20 You are receiving this mail because: You are the assignee for the bug.= --15685104500.CE977.9634 Date: Sun, 15 Sep 2019 01:20:50 +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 # 100 on bug 10995= 5 from Rodney A Morris 
(In reply to Rodney A Morris from comment #99)
> Created attachment 145366 [detail=
s]
> apitrace of Hearts of Iron IV hard lock
>=20
> Apitrace from hard lock playing Hearts of Iron IV without Steam.  The =
replay
> from this trace will hard lock the computer, though inconsistently.  I=
've
> replayed the trace three times. The replay hard locked computer one ti=
me.

neofetch from hardlock:

          /:-------------:\=20=20=20=20=20=20=20=20=20=20
       :-------------------::        --------------------------------=20
     :-----------/shhOHbmp---:\      OS: Fedora release 30 (Thirty) x86_64=
=20
   /-----------omMMMNNNMMD  ---:     Kernel: 5.2.13-200.fc30.x86_64=20
  :-----------sMMMMNMNMP.    ---:    Uptime: 25 mins=20
 :-----------:MMMdP-------    ---\   Packages: 2202 (rpm), 27 (flatpak)=20
,------------:MMMd--------    ---:   Shell: bash 5.0.7=20
:------------:MMMd-------    .---:   Resolution: 2560x1440=20
:----    oNMMMMMMMMMNho     .----:   DE: GNOME 3.32.2=20
:--     .+shhhMMMmhhy++   .------/   WM: GNOME Shell=20
:-    -------:MMMd--------------:    WM Theme: Adwaita=20
:-   --------/MMMd-------------;     Theme: Adapta-Nokto-Eta [GTK2/3]=20
:-    ------/hMMMy------------:      Icons: Adwaita [GTK2/3]=20
:-- :dMNdhhdNMMNo------------;       Terminal: tilix=20
:---:sdNMMMMNds:------------:        CPU: Intel i7-6850K (12) @ 4.000GH=
z=20
:------:://:-------------::          GPU: AMD ATI Radeon RX Vega 56/64=20
:---------------------://            Memory: 2478MiB / 32084MiB=20

OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6

Note:  hard lock replayed occurred when the Discord flatpak is also running=
.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15685104500.CE977.9634-- --===============0211457309== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0211457309==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 15 Sep 2019 01:21:05 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0866200418==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 676726F56F for ; Sun, 15 Sep 2019 01:21:14 +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 --===============0866200418== Content-Type: multipart/alternative; boundary="15685104730.20B40D.9638" Content-Transfer-Encoding: 7bit --15685104730.20B40D.9638 Date: Sun, 15 Sep 2019 01:21:13 +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=3D109955 --- Comment #101 from Rodney A Morris --- (In reply to Rodney A Morris from comment #99) > Created attachment 145366 [details] > apitrace of Hearts of Iron IV hard lock >=20 > Apitrace from hard lock playing Hearts of Iron IV without Steam. The rep= lay > from this trace will hard lock the computer, though inconsistently. I've > replayed the trace three times. The replay hard locked computer one time. neofetch from hardlock: /:-------------:\=20=20=20=20=20=20=20=20=20=20 :-------------------:: --------------------------------=20 :-----------/shhOHbmp---:\ OS: Fedora release 30 (Thirty) x86_64= =20 /-----------omMMMNNNMMD ---: Kernel: 5.2.13-200.fc30.x86_64=20 :-----------sMMMMNMNMP. ---: Uptime: 25 mins=20 :-----------:MMMdP------- ---\ Packages: 2202 (rpm), 27 (flatpak)=20 ,------------:MMMd-------- ---: Shell: bash 5.0.7=20 :------------:MMMd------- .---: Resolution: 2560x1440=20 :---- oNMMMMMMMMMNho .----: DE: GNOME 3.32.2=20 :-- .+shhhMMMmhhy++ .------/ WM: GNOME Shell=20 :- -------:MMMd--------------: WM Theme: Adwaita=20 :- --------/MMMd-------------; Theme: Adapta-Nokto-Eta [GTK2/3]=20 :- ------/hMMMy------------: Icons: Adwaita [GTK2/3]=20 :-- :dMNdhhdNMMNo------------; Terminal: tilix=20 :---:sdNMMMMNds:------------: CPU: Intel i7-6850K (12) @ 4.000GHz=20 :------:://:-------------:: GPU: AMD ATI Radeon RX Vega 56/64=20 :---------------------:// Memory: 2478MiB / 32084MiB=20 OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6 Note: hard lock replayed occurred when the Discord flatpak is also running. --=20 You are receiving this mail because: You are the assignee for the bug.= --15685104730.20B40D.9638 Date: Sun, 15 Sep 2019 01:21:13 +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 # 101 on bug 10995= 5 from Rodney A Morris 
(In reply to Rodney A Morris from comment #99)
> Created attachment 145366 [detail=
s]
> apitrace of Hearts of Iron IV hard lock
>=20
> Apitrace from hard lock playing Hearts of Iron IV without Steam.  The =
replay
> from this trace will hard lock the computer, though inconsistently.  I=
've
> replayed the trace three times. The replay hard locked computer one ti=
me.

neofetch from hardlock:

          /:-------------:\=20=20=20=20=20=20=20=20=20=20
       :-------------------::        --------------------------------=20
     :-----------/shhOHbmp---:\      OS: Fedora release 30 (Thirty) x86_64=
=20
   /-----------omMMMNNNMMD  ---:     Kernel: 5.2.13-200.fc30.x86_64=20
  :-----------sMMMMNMNMP.    ---:    Uptime: 25 mins=20
 :-----------:MMMdP-------    ---\   Packages: 2202 (rpm), 27 (flatpak)=20
,------------:MMMd--------    ---:   Shell: bash 5.0.7=20
:------------:MMMd-------    .---:   Resolution: 2560x1440=20
:----    oNMMMMMMMMMNho     .----:   DE: GNOME 3.32.2=20
:--     .+shhhMMMmhhy++   .------/   WM: GNOME Shell=20
:-    -------:MMMd--------------:    WM Theme: Adwaita=20
:-   --------/MMMd-------------;     Theme: Adapta-Nokto-Eta [GTK2/3]=20
:-    ------/hMMMy------------:      Icons: Adwaita [GTK2/3]=20
:-- :dMNdhhdNMMNo------------;       Terminal: tilix=20
:---:sdNMMMMNds:------------:        CPU: Intel i7-6850K (12) @ 4.000GH=
z=20
:------:://:-------------::          GPU: AMD ATI Radeon RX Vega 56/64=20
:---------------------://            Memory: 2478MiB / 32084MiB=20

OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6

Note:  hard lock replayed occurred when the Discord flatpak is also running=
.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15685104730.20B40D.9638-- --===============0866200418== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0866200418==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 15 Sep 2019 04:35:43 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0927999402==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id EB3736F586 for ; Sun, 15 Sep 2019 04:35: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 --===============0927999402== Content-Type: multipart/alternative; boundary="15685221431.26bed45A.8675" Content-Transfer-Encoding: 7bit --15685221431.26bed45A.8675 Date: Sun, 15 Sep 2019 04:35: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=3D109955 --- Comment #102 from Rodney A Morris --- Created attachment 145367 --> https://bugs.freedesktop.org/attachment.cgi?id=3D145367&action=3Dedit Full dmesg from Stellaris crash I had another crash and soft lockup tonight playing Stellaris through Steam= .=20 Unfortunately, while I had the mesa debuginfo packages installed, I did not have the debug kernel installed. /:-------------:\=20=20=20=20=20=20=20=20=20=20 :-------------------:: --------------------------------=20 :-----------/shhOHbmp---:\ OS: Fedora release 30 (Thirty) x86_64= =20 /-----------omMMMNNNMMD ---: Kernel: 5.2.13-200.fc30.x86_64=20 :-----------sMMMMNMNMP. ---: Uptime: 25 mins=20 :-----------:MMMdP------- ---\ Packages: 2202 (rpm), 27 (flatpak)=20 ,------------:MMMd-------- ---: Shell: bash 5.0.7=20 :------------:MMMd------- .---: Resolution: 2560x1440=20 :---- oNMMMMMMMMMNho .----: DE: GNOME 3.32.2=20 :-- .+shhhMMMmhhy++ .------/ WM: GNOME Shell=20 :- -------:MMMd--------------: WM Theme: Adwaita=20 :- --------/MMMd-------------; Theme: Adapta-Nokto-Eta [GTK2/3]=20 :- ------/hMMMy------------: Icons: Adwaita [GTK2/3]=20 :-- :dMNdhhdNMMNo------------; Terminal: tilix=20 :---:sdNMMMMNds:------------: CPU: Intel i7-6850K (12) @ 4.000GHz=20 :------:://:-------------:: GPU: AMD ATI Radeon RX Vega 56/64=20 :---------------------:// Memory: 2478MiB / 32084MiB=20 OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6 > Game being played:=20 Stellaris through Steam for Linux. Like other times Discord is running. > Native or Wine or Wine+DXVK: Native >=20 > Crash type: Game crash? Full System freeze? System freeze but still can d= rop > to tty? Screen goes black suddenly while music continues plays for less than a minu= te; music begins to loop; and computer reboots. >=20 > DMESG output after the crash: Below is the pertinent dmesg messages. Full file attached. [ 5292.563342] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting = for fences timed out or interrupted! [ 5297.683350] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring page1 timeou= t, signaled seq=3D97861046, emitted seq=3D97861048 [ 5297.683465] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati= on: process pid 0 thread pid 0 [ 5297.683470] amdgpu 0000:06:00.0: GPU reset begin! [ 5297.693302] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D1321512, emitted seq=3D1321513 [ 5297.693406] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati= on: process stellaris pid 5624 thread stellaris:cs0 pid 5625 [ 5297.693409] amdgpu 0000:06:00.0: GPU reset begin! [ 5297.709624] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 5297.709631] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 5297.709634] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 5297.709637] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 5297.709706] pcieport 0000:00:03.0: AER: Device recovery failed [ 5302.803236] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out [ 5307.923355] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-= 0] hw_done or flip_done timed out [ 5318.163235] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper= ]] *ERROR* [CRTC:47:crtc-0] flip_done timed out [ 5328.403235] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper= ]] *ERROR* [PLANE:45:plane-5] flip_done timed out [ 5328.717149] amdgpu: [powerplay] No response from smu [ 5328.717151] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x= 0, error code: 0x0 [ 5329.031482] amdgpu: [powerplay] No response from smu [ 5329.345845] amdgpu: [powerplay] No response from smu [ 5329.345847] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0= x1, error code: 0x0 [ 5329.659470] amdgpu: [powerplay] No response from smu [ 5329.973320] amdgpu: [powerplay] No response from smu [ 5329.973322] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0= x0, error code: 0x0 [ 5330.044255] [drm] REG_WAIT timeout 10us * 3500 tries - dce_mi_free_dmif line:634 [ 5330.044255] ------------[ cut here ]------------ [ 5330.044355] WARNING: CPU: 9 PID: 7317 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:329 generic_reg_wait.cold+0x31/0x53 [amdgpu] [ 5330.044356] Modules linked in: rfcomm xt_CHECKSUM xt_MASQUERADE tun brid= ge stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_n= at ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_= nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables bnep nct6775 hwmon_vid intel_rapl arc4 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel vf= at fat kvm fuse irqbypass iwlmvm iTCO_wdt iTCO_vendor_support mac80211 crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek ghash_clmulni_intel intel_cstate btusb iwlwifi snd_hda_codec_generic btrtl btbcm btintel ledtrig_audio snd_hda_codec_hdmi intel_uncore bluetooth snd_hda_intel intel_rapl_perf snd_hda_codec cfg80211 snd_hda_core snd_hwdep mxm_wmi i2c_i= 801 joydev snd_seq snd_seq_device xpad ecdh_generic [ 5330.044372] ff_memless snd_pcm rfkill ecc snd_timer mei_me snd mei soundcore lpc_ich pcc_cpufreq auth_rpcgss binfmt_misc sunrpc amdgpu amd_iommu_v2 gpu_sched ttm drm_kms_helper drm mpt3sas igb crc32c_intel e100= 0e nvme raid_class nvme_core dca i2c_algo_bit scsi_transport_sas wmi uas usb_storage [ 5330.044380] CPU: 9 PID: 7317 Comm: kworker/9:0 Not tainted 5.2.13-200.fc30.x86_64 #1 [ 5330.044381] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M.= /X99 Taichi, BIOS P1.80 04/06/2018 [ 5330.044384] Workqueue: events drm_sched_job_timedout [gpu_sched] [ 5330.044424] RIP: 0010:generic_reg_wait.cold+0x31/0x53 [amdgpu] [ 5330.044425] Code: 4c 24 18 44 89 fa 89 ee 48 c7 c7 b8 e2 7b c0 e8 fb d4 = a2 fc 83 7b 20 01 0f 84 8d 14 fe ff 48 c7 c7 28 e2 7b c0 e8 e5 d4 a2 fc <0f> 0= b e9 7a 14 fe ff 48 c7 c7 28 e2 7b c0 89 54 24 04 e8 ce d4 a2 [ 5330.044426] RSP: 0000:ffffb980493f37b8 EFLAGS: 00010246 [ 5330.044426] RAX: 0000000000000024 RBX: ffff911f70720780 RCX: 0000000000000006 [ 5330.044427] RDX: 0000000000000000 RSI: 0000000000000086 RDI: ffff911f7fa57900 [ 5330.044427] RBP: 000000000000000a R08: 0000000000000001 R09: 0000000000000737 [ 5330.044428] R10: 0000000000026ddc R11: 0000000000000003 R12: 00000000000035af [ 5330.044428] R13: 0000000000000dad R14: 0000000000000001 R15: 0000000000000dac [ 5330.044429] FS: 0000000000000000(0000) GS:ffff911f7fa40000(0000) knlGS:0000000000000000 [ 5330.044429] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 5330.044430] CR2: 000006af3a9fb000 CR3: 00000007ab40a003 CR4: 00000000003606e0 [ 5330.044430] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 5330.044431] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 5330.044431] Call Trace: [ 5330.044487] dce_mi_free_dmif+0xef/0x150 [amdgpu] [ 5330.044524] dce110_reset_hw_ctx_wrap+0x14a/0x1e0 [amdgpu] [ 5330.044562] dce110_apply_ctx_to_hw+0x4a/0x490 [amdgpu] [ 5330.044588] ? amdgpu_pm_compute_clocks.part.0+0xcb/0x610 [amdgpu] [ 5330.044590] ? _cond_resched+0x15/0x30 [ 5330.044629] ? dm_pp_apply_display_requirements+0x1a8/0x1c0 [amdgpu] [ 5330.044666] dc_commit_state+0x27b/0x5c0 [amdgpu] [ 5330.044669] ? number+0x31c/0x360 [ 5330.044707] amdgpu_dm_atomic_commit_tail+0xc15/0x1930 [amdgpu] [ 5330.044710] ? va_format.isra.0+0x6e/0xa0 [ 5330.044713] ? sched_clock+0x5/0x10 [ 5330.044716] ? sched_clock_cpu+0xc/0xa0 [ 5330.044719] ? up+0x12/0x60 [ 5330.044721] ? __irq_work_queue_local+0x50/0x60 [ 5330.044722] ? irq_work_queue+0x46/0x50 [ 5330.044725] ? wake_up_klogd+0x30/0x40 [ 5330.044726] ? vprintk_emit+0x17c/0x260 [ 5330.044727] ? printk+0x58/0x6f [ 5330.044728] ? __next_timer_interrupt+0xd0/0xd0 [ 5330.044736] ? drm_atomic_helper_wait_for_dependencies+0x1e4/0x1f0 [drm_kms_helper] [ 5330.044748] ? drm_err+0x72/0x90 [drm] [ 5330.044749] ? _cond_resched+0x15/0x30 [ 5330.044750] ? wait_for_completion_timeout+0x38/0x170 [ 5330.044754] ? commit_tail+0x3c/0x70 [drm_kms_helper] [ 5330.044791] ? amdgpu_dm_atomic_check+0x6d0/0x6d0 [amdgpu] [ 5330.044795] commit_tail+0x3c/0x70 [drm_kms_helper] [ 5330.044799] drm_atomic_helper_commit+0x108/0x110 [drm_kms_helper] [ 5330.044803] drm_atomic_helper_disable_all+0x144/0x160 [drm_kms_helper] [ 5330.044807] drm_atomic_helper_suspend+0x60/0xf0 [drm_kms_helper] [ 5330.044844] dm_suspend+0x20/0x60 [amdgpu] [ 5330.044867] amdgpu_device_ip_suspend_phase1+0x8b/0xc0 [amdgpu] [ 5330.044890] amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu] [ 5330.044927] amdgpu_device_pre_asic_reset+0x1f4/0x209 [amdgpu] [ 5330.044965] amdgpu_device_gpu_recover+0x77/0x785 [amdgpu] [ 5330.044998] amdgpu_job_timedout+0xf7/0x120 [amdgpu] [ 5330.045000] drm_sched_job_timedout+0x3a/0x70 [gpu_sched] [ 5330.045003] process_one_work+0x19d/0x380 [ 5330.045005] worker_thread+0x50/0x3b0 [ 5330.045007] kthread+0xfb/0x130 [ 5330.045008] ? process_one_work+0x380/0x380 [ 5330.045009] ? kthread_park+0x80/0x80 [ 5330.045010] ret_from_fork+0x35/0x40 [ 5330.045012] ---[ end trace 7beee32e6101e37d ]--- [ 5330.358847] amdgpu: [powerplay] No response from smu [ 5330.673262] amdgpu: [powerplay] No response from smu [ 5330.673263] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0= x1, error code: 0x0 [ 5330.987579] amdgpu: [powerplay] No response from smu [ 5331.302073] amdgpu: [powerplay] No response from smu [ 5331.302074] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0= x3, error code: 0x0 [ 5331.616202] amdgpu: [powerplay] No response from smu [ 5331.929678] amdgpu: [powerplay] No response from smu [ 5331.929681] amdgpu: [powerplay] Failed message: 0x9, input parameter: 0x= f4, error code: 0x0 [ 5332.243534] amdgpu: [powerplay] No response from smu [ 5332.557383] amdgpu: [powerplay] No response from smu [ 5332.557384] amdgpu: [powerplay] Failed message: 0xa, input parameter: 0xa0b000, error code: 0x0 [ 5332.871126] amdgpu: [powerplay] No response from smu [ 5333.185009] amdgpu: [powerplay] No response from smu [ 5333.185011] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x= 0, error code: 0x0 [ 5333.498596] amdgpu: [powerplay] No response from smu [ 5333.812147] amdgpu: [powerplay] No response from smu [ 5333.812155] amdgpu: [powerplay] Failed message: 0x4, input parameter: 0x= 400, error code: 0x0 [ 5334.126013] amdgpu: [powerplay] No response from smu [ 5334.440194] amdgpu: [powerplay] No response from smu [ 5334.440197] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0= x1, error code: 0x0 [ 5334.753930] amdgpu: [powerplay] No response from smu [ 5335.067603] amdgpu: [powerplay] No response from smu [ 5335.067605] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0= x0, error code: 0x0 [ 5335.083579] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 5335.083589] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 5335.083599] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 5335.083603] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 5335.083694] pcieport 0000:00:03.0: AER: Device recovery failed [ 5335.101028] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 5335.101034] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 5335.101036] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 5335.101039] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 5335.101085] pcieport 0000:00:03.0: AER: Device recovery failed [ 5335.118568] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 5335.118573] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 5335.118575] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 5335.118577] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 5335.118621] pcieport 0000:00:03.0: AER: Device recovery failed [ 5335.136108] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 5335.136113] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 5335.136116] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 5335.136118] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 5335.136189] pcieport 0000:00:03.0: AER: Device recovery failed [ 5335.153649] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 5335.153654] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 5335.153656] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 5335.153658] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 5335.153702] pcieport 0000:00:03.0: AER: Device recovery failed [ 5335.171189] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 5335.171194] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 5335.171196] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 5335.171199] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 5335.171242] pcieport 0000:00:03.0: AER: Device recovery failed [ 5335.188769] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 5335.188774] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 5335.188776] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 5335.188778] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 5335.188819] pcieport 0000:00:03.0: AER: Device recovery failed [ 5335.206263] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 5335.206266] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 5335.206267] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 5335.206268] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 5335.206286] pcieport 0000:00:03.0: AER: Device recovery failed [ 5335.223806] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 5335.223809] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 5335.223811] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 5335.223812] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 5335.223837] pcieport 0000:00:03.0: AER: Device recovery failed [ 5335.241348] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 5335.469372] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 5335.469374] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 5335.469375] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 5335.469405] pcieport 0000:00:03.0: AER: Device recovery failed [ 5335.469406] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal) error received: 0000:00:03.0 > systemd logs output after the crash (If your system froze and you get logs > after reboot): Sep 14 20:52:48 ezra.blanchardmorris.net kernel: Command line: BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.13-200.fc30.x86_64 root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d= ebug=3D1 Sep 14 20:52:48 ezra.blanchardmorris.net kernel: Kernel command line: BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.13-200.fc30.x86_64 root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d= ebug=3D1 Sep 14 20:52:49 ezra.blanchardmorris.net dracut-cmdline[363]: Using kernel command line parameters: BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.13-200.fc30.x8= 6_64 root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d= ebug=3D1 Sep 14 20:52:49 ezra.blanchardmorris.net kernel: [drm] amdgpu kernel modesetting enabled. Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: remove_conflicting_pci_framebuffers: bar 0: 0xe0000000 -> 0xefffffff Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: remove_conflicting_pci_framebuffers: bar 2: 0xf0000000 -> 0xf01fffff Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: remove_conflicting_pci_framebuffers: bar 5: 0xfb600000 -> 0xfb67ffff Sep 14 20:52:49 ezra.blanchardmorris.net kernel: fb0: switching to amdgpudr= mfb from EFI VGA Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: vgaar= b: deactivate vga console Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: No mo= re image in the PCI ROM Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: VRAM: 8176M 0x000000F400000000 - 0x000000F5FEFFFFFF (8176M used) Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF Sep 14 20:52:49 ezra.blanchardmorris.net kernel: [drm] amdgpu: 8176M of VRAM memory ready Sep 14 20:52:49 ezra.blanchardmorris.net kernel: [drm] amdgpu: 8176M of GTT memory ready. Sep 14 20:52:50 ezra.blanchardmorris.net kernel: fbcon: amdgpudrmfb (fb0) is primary device Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: fb0: amdgpudrmfb frame buffer device Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring = gfx uses VM inv eng 0 on hub 0 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring sdma0 uses VM inv eng 0 on hub 1 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring page0 uses VM inv eng 1 on hub 1 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring sdma1 uses VM inv eng 4 on hub 1 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring page1 uses VM inv eng 5 on hub 1 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring uvd_0 uses VM inv eng 6 on hub 1 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring uvd_enc_0.0 uses VM inv eng 7 on hub 1 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring uvd_enc_0.1 uses VM inv eng 8 on hub 1 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring = vce0 uses VM inv eng 9 on hub 1 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring = vce1 uses VM inv eng 10 on hub 1 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring = vce2 uses VM inv eng 11 on hub 1 Sep 14 20:52:50 ezra.blanchardmorris.net kernel: [drm] Initialized amdgpu 3.32.0 20150101 for 0000:06:00.0 on minor 0 Sep 14 20:53:20 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1928]: Kernel command line: BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.13-200.fc30.x86_64 root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d= ebug=3D1 Sep 14 20:53:20 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1928]:= =20=20=20=20=20 loading driver: amdgpu Sep 14 20:53:20 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1928]: = (=3D=3D) Matched amdgpu as autoconfigured driver 0 Sep 14 20:53:20 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1928]: = (II) LoadModule: "amdgpu" Sep 14 20:53:20 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1928]: = (II) Loading /usr/lib64/xorg/modules/drivers/amdgpu_drv.so Sep 14 20:53:20 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1928]: = (II) Module amdgpu: vendor=3D"X.Org Foundation" Sep 14 20:53:20 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1928]:= =20=20=20=20=20 All GPUs supported by the amdgpu kernel driver Sep 14 22:21:05 ezra.blanchardmorris.net kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out or interrupted! Sep 14 22:21:05 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring page1 timeout, signaled seq=3D97861046, emitted seq=3D97861048 Sep 14 22:21:05 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 Sep 14 22:21:05 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: GPU r= eset begin! Sep 14 22:21:05 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D1321512, emitted seq=3D1= 321513 Sep 14 22:21:05 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process stellaris pid 5624 thread stellaris:cs0 pid 5625 Sep 14 22:21:05 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: GPU r= eset begin! Sep 14 22:21:15 ezra.blanchardmorris.net kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-0] hw_done or flip_done timed out Sep 14 22:21:36 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Sep 14 22:21:36 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x0, error code: 0x0 Sep 14 22:21:36 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Sep 14 22:21:37 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu --=20 You are receiving this mail because: You are the assignee for the bug.= --15685221431.26bed45A.8675 Date: Sun, 15 Sep 2019 04:35: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 # 102 on bug 10995= 5 from Rodney A Morris 
Created attachme=
nt 145367 [details]
Full dmesg from Stellaris crash

I had another crash and soft lockup tonight playing Stellaris through Steam=
.=20
Unfortunately, while I had the mesa debuginfo packages installed, I did not
have the debug kernel installed.

          /:-------------:\=20=20=20=20=20=20=20=20=20=20
       :-------------------::        --------------------------------=20
     :-----------/shhOHbmp---:\      OS: Fedora release 30 (Thirty) x86_64=
=20
   /-----------omMMMNNNMMD  ---:     Kernel: 5.2.13-200.fc30.x86_64=20
  :-----------sMMMMNMNMP.    ---:    Uptime: 25 mins=20
 :-----------:MMMdP-------    ---\   Packages: 2202 (rpm), 27 (flatpak)=20
,------------:MMMd--------    ---:   Shell: bash 5.0.7=20
:------------:MMMd-------    .---:   Resolution: 2560x1440=20
:----    oNMMMMMMMMMNho     .----:   DE: GNOME 3.32.2=20
:--     .+shhhMMMmhhy++   .------/   WM: GNOME Shell=20
:-    -------:MMMd--------------:    WM Theme: Adwaita=20
:-   --------/MMMd-------------;     Theme: Adapta-Nokto-Eta [GTK2/3]=20
:-    ------/hMMMy------------:      Icons: Adwaita [GTK2/3]=20
:-- :dMNdhhdNMMNo------------;       Terminal: tilix=20
:---:sdNMMMMNds:------------:        CPU: Intel i7-6850K (12) @ 4.000GH=
z=20
:------:://:-------------::          GPU: AMD ATI Radeon RX Vega 56/64=20
:---------------------://            Memory: 2478MiB / 32084MiB=20

OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6

> Game being played: 


Stellaris through Steam for Linux.  Like other times Discord is running.

> Native or Wine or Wine+DXVK:


Native

>=20
> Crash type: Game crash? Full System freeze? System freeze but still ca=
n drop
> to tty?


Screen goes black suddenly while music continues plays for less than a minu=
te;
music begins to loop; and computer reboots.

>=20
> DMESG output after the crash:
Below is the pertinent dmesg messages.  Full file attached.

[ 5292.563342] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting =
for
fences timed out or interrupted!
[ 5297.683350] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring page1 timeou=
t,
signaled seq=3D97861046, emitted seq=3D97861048
[ 5297.683465] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati=
on:
process  pid 0 thread  pid 0
[ 5297.683470] amdgpu 0000:06:00.0: GPU reset begin!
[ 5297.693302] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=3D1321512, emitted seq=3D1321513
[ 5297.693406] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati=
on:
process stellaris pid 5624 thread stellaris:cs0 pid 5625
[ 5297.693409] amdgpu 0000:06:00.0: GPU reset begin!
[ 5297.709624] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 5297.709631] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 5297.709634] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 5297.709637] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 5297.709706] pcieport 0000:00:03.0: AER: Device recovery failed
[ 5302.803236] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
*ERROR* [CRTC:47:crtc-0] flip_done timed out
[ 5307.923355] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-=
0]
hw_done or flip_done timed out
[ 5318.163235] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper=
]]
*ERROR* [CRTC:47:crtc-0] flip_done timed out
[ 5328.403235] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper=
]]
*ERROR* [PLANE:45:plane-5] flip_done timed out
[ 5328.717149] amdgpu: [powerplay] No response from smu
[ 5328.717151] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x=
0,
error code: 0x0
[ 5329.031482] amdgpu: [powerplay] No response from smu
[ 5329.345845] amdgpu: [powerplay] No response from smu
[ 5329.345847] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0=
x1,
error code: 0x0
[ 5329.659470] amdgpu: [powerplay] No response from smu
[ 5329.973320] amdgpu: [powerplay] No response from smu
[ 5329.973322] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0=
x0,
error code: 0x0
[ 5330.044255] [drm] REG_WAIT timeout 10us * 3500 tries - dce_mi_free_dmif
line:634
[ 5330.044255] ------------[ cut here ]------------
[ 5330.044355] WARNING: CPU: 9 PID: 7317 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:329
generic_reg_wait.cold+0x31/0x53 [amdgpu]
[ 5330.044356] Modules linked in: rfcomm xt_CHECKSUM xt_MASQUERADE tun brid=
ge
stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter
ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_n=
at
ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_=
nat
iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6
nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables
ip6table_filter ip6_tables iptable_filter ip_tables bnep nct6775 hwmon_vid
intel_rapl arc4 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel vf=
at
fat kvm fuse irqbypass iwlmvm iTCO_wdt iTCO_vendor_support mac80211
crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek ghash_clmulni_intel
intel_cstate btusb iwlwifi snd_hda_codec_generic btrtl btbcm btintel
ledtrig_audio snd_hda_codec_hdmi intel_uncore bluetooth snd_hda_intel
intel_rapl_perf snd_hda_codec cfg80211 snd_hda_core snd_hwdep mxm_wmi i2c_i=
801
joydev snd_seq snd_seq_device xpad ecdh_generic
[ 5330.044372]  ff_memless snd_pcm rfkill ecc snd_timer mei_me snd mei
soundcore lpc_ich pcc_cpufreq auth_rpcgss binfmt_misc sunrpc amdgpu
amd_iommu_v2 gpu_sched ttm drm_kms_helper drm mpt3sas igb crc32c_intel e100=
0e
nvme raid_class nvme_core dca i2c_algo_bit scsi_transport_sas wmi uas
usb_storage
[ 5330.044380] CPU: 9 PID: 7317 Comm: kworker/9:0 Not tainted
5.2.13-200.fc30.x86_64 #1
[ 5330.044381] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M.=
/X99
Taichi, BIOS P1.80 04/06/2018
[ 5330.044384] Workqueue: events drm_sched_job_timedout [gpu_sched]
[ 5330.044424] RIP: 0010:generic_reg_wait.cold+0x31/0x53 [amdgpu]
[ 5330.044425] Code: 4c 24 18 44 89 fa 89 ee 48 c7 c7 b8 e2 7b c0 e8 fb d4 =
a2
fc 83 7b 20 01 0f 84 8d 14 fe ff 48 c7 c7 28 e2 7b c0 e8 e5 d4 a2 fc <0f=
> 0b e9
7a 14 fe ff 48 c7 c7 28 e2 7b c0 89 54 24 04 e8 ce d4 a2
[ 5330.044426] RSP: 0000:ffffb980493f37b8 EFLAGS: 00010246
[ 5330.044426] RAX: 0000000000000024 RBX: ffff911f70720780 RCX:
0000000000000006
[ 5330.044427] RDX: 0000000000000000 RSI: 0000000000000086 RDI:
ffff911f7fa57900
[ 5330.044427] RBP: 000000000000000a R08: 0000000000000001 R09:
0000000000000737
[ 5330.044428] R10: 0000000000026ddc R11: 0000000000000003 R12:
00000000000035af
[ 5330.044428] R13: 0000000000000dad R14: 0000000000000001 R15:
0000000000000dac
[ 5330.044429] FS:  0000000000000000(0000) GS:ffff911f7fa40000(0000)
knlGS:0000000000000000
[ 5330.044429] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 5330.044430] CR2: 000006af3a9fb000 CR3: 00000007ab40a003 CR4:
00000000003606e0
[ 5330.044430] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 5330.044431] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
0000000000000400
[ 5330.044431] Call Trace:
[ 5330.044487]  dce_mi_free_dmif+0xef/0x150 [amdgpu]
[ 5330.044524]  dce110_reset_hw_ctx_wrap+0x14a/0x1e0 [amdgpu]
[ 5330.044562]  dce110_apply_ctx_to_hw+0x4a/0x490 [amdgpu]
[ 5330.044588]  ? amdgpu_pm_compute_clocks.part.0+0xcb/0x610 [amdgpu]
[ 5330.044590]  ? _cond_resched+0x15/0x30
[ 5330.044629]  ? dm_pp_apply_display_requirements+0x1a8/0x1c0 [amdgpu]
[ 5330.044666]  dc_commit_state+0x27b/0x5c0 [amdgpu]
[ 5330.044669]  ? number+0x31c/0x360
[ 5330.044707]  amdgpu_dm_atomic_commit_tail+0xc15/0x1930 [amdgpu]
[ 5330.044710]  ? va_format.isra.0+0x6e/0xa0
[ 5330.044713]  ? sched_clock+0x5/0x10
[ 5330.044716]  ? sched_clock_cpu+0xc/0xa0
[ 5330.044719]  ? up+0x12/0x60
[ 5330.044721]  ? __irq_work_queue_local+0x50/0x60
[ 5330.044722]  ? irq_work_queue+0x46/0x50
[ 5330.044725]  ? wake_up_klogd+0x30/0x40
[ 5330.044726]  ? vprintk_emit+0x17c/0x260
[ 5330.044727]  ? printk+0x58/0x6f
[ 5330.044728]  ? __next_timer_interrupt+0xd0/0xd0
[ 5330.044736]  ? drm_atomic_helper_wait_for_dependencies+0x1e4/0x1f0
[drm_kms_helper]
[ 5330.044748]  ? drm_err+0x72/0x90 [drm]
[ 5330.044749]  ? _cond_resched+0x15/0x30
[ 5330.044750]  ? wait_for_completion_timeout+0x38/0x170
[ 5330.044754]  ? commit_tail+0x3c/0x70 [drm_kms_helper]
[ 5330.044791]  ? amdgpu_dm_atomic_check+0x6d0/0x6d0 [amdgpu]
[ 5330.044795]  commit_tail+0x3c/0x70 [drm_kms_helper]
[ 5330.044799]  drm_atomic_helper_commit+0x108/0x110 [drm_kms_helper]
[ 5330.044803]  drm_atomic_helper_disable_all+0x144/0x160 [drm_kms_helper]
[ 5330.044807]  drm_atomic_helper_suspend+0x60/0xf0 [drm_kms_helper]
[ 5330.044844]  dm_suspend+0x20/0x60 [amdgpu]
[ 5330.044867]  amdgpu_device_ip_suspend_phase1+0x8b/0xc0 [amdgpu]
[ 5330.044890]  amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu]
[ 5330.044927]  amdgpu_device_pre_asic_reset+0x1f4/0x209 [amdgpu]
[ 5330.044965]  amdgpu_device_gpu_recover+0x77/0x785 [amdgpu]
[ 5330.044998]  amdgpu_job_timedout+0xf7/0x120 [amdgpu]
[ 5330.045000]  drm_sched_job_timedout+0x3a/0x70 [gpu_sched]
[ 5330.045003]  process_one_work+0x19d/0x380
[ 5330.045005]  worker_thread+0x50/0x3b0
[ 5330.045007]  kthread+0xfb/0x130
[ 5330.045008]  ? process_one_work+0x380/0x380
[ 5330.045009]  ? kthread_park+0x80/0x80
[ 5330.045010]  ret_from_fork+0x35/0x40
[ 5330.045012] ---[ end trace 7beee32e6101e37d ]---
[ 5330.358847] amdgpu: [powerplay] No response from smu
[ 5330.673262] amdgpu: [powerplay] No response from smu
[ 5330.673263] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0=
x1,
error code: 0x0
[ 5330.987579] amdgpu: [powerplay] No response from smu
[ 5331.302073] amdgpu: [powerplay] No response from smu
[ 5331.302074] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0=
x3,
error code: 0x0
[ 5331.616202] amdgpu: [powerplay] No response from smu
[ 5331.929678] amdgpu: [powerplay] No response from smu
[ 5331.929681] amdgpu: [powerplay] Failed message: 0x9, input parameter: 0x=
f4,
error code: 0x0
[ 5332.243534] amdgpu: [powerplay] No response from smu
[ 5332.557383] amdgpu: [powerplay] No response from smu
[ 5332.557384] amdgpu: [powerplay] Failed message: 0xa, input parameter:
0xa0b000, error code: 0x0
[ 5332.871126] amdgpu: [powerplay] No response from smu
[ 5333.185009] amdgpu: [powerplay] No response from smu
[ 5333.185011] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x=
0,
error code: 0x0
[ 5333.498596] amdgpu: [powerplay] No response from smu
[ 5333.812147] amdgpu: [powerplay] No response from smu
[ 5333.812155] amdgpu: [powerplay] Failed message: 0x4, input parameter: 0x=
400,
error code: 0x0
[ 5334.126013] amdgpu: [powerplay] No response from smu
[ 5334.440194] amdgpu: [powerplay] No response from smu
[ 5334.440197] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0=
x1,
error code: 0x0
[ 5334.753930] amdgpu: [powerplay] No response from smu
[ 5335.067603] amdgpu: [powerplay] No response from smu
[ 5335.067605] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0=
x0,
error code: 0x0
[ 5335.083579] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 5335.083589] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 5335.083599] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 5335.083603] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 5335.083694] pcieport 0000:00:03.0: AER: Device recovery failed
[ 5335.101028] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 5335.101034] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 5335.101036] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 5335.101039] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 5335.101085] pcieport 0000:00:03.0: AER: Device recovery failed
[ 5335.118568] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 5335.118573] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 5335.118575] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 5335.118577] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 5335.118621] pcieport 0000:00:03.0: AER: Device recovery failed
[ 5335.136108] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 5335.136113] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 5335.136116] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 5335.136118] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 5335.136189] pcieport 0000:00:03.0: AER: Device recovery failed
[ 5335.153649] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 5335.153654] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 5335.153656] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 5335.153658] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 5335.153702] pcieport 0000:00:03.0: AER: Device recovery failed
[ 5335.171189] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 5335.171194] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 5335.171196] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 5335.171199] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 5335.171242] pcieport 0000:00:03.0: AER: Device recovery failed
[ 5335.188769] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 5335.188774] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 5335.188776] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 5335.188778] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 5335.188819] pcieport 0000:00:03.0: AER: Device recovery failed
[ 5335.206263] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 5335.206266] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 5335.206267] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 5335.206268] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 5335.206286] pcieport 0000:00:03.0: AER: Device recovery failed
[ 5335.223806] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 5335.223809] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 5335.223811] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 5335.223812] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 5335.223837] pcieport 0000:00:03.0: AER: Device recovery failed
[ 5335.241348] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal)
error received: 0000:00:03.0
[ 5335.469372] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 5335.469374] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 5335.469375] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 5335.469405] pcieport 0000:00:03.0: AER: Device recovery failed
[ 5335.469406] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal)
error received: 0000:00:03.0

> systemd logs output after the crash (If your sys=
tem froze and you get logs
> after reboot):

Sep 14 20:52:48 ezra.blanchardmorris.net kernel: Command line:
BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.13-200.fc30.x86_64
root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro
resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d=
ebug=3D1
Sep 14 20:52:48 ezra.blanchardmorris.net kernel: Kernel command line:
BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.13-200.fc30.x86_64
root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro
resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d=
ebug=3D1
Sep 14 20:52:49 ezra.blanchardmorris.net dracut-cmdline[363]: Using kernel
command line parameters: BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.13-200.fc30.x8=
6_64
root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro
resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d=
ebug=3D1
Sep 14 20:52:49 ezra.blanchardmorris.net kernel: [drm] amdgpu kernel
modesetting enabled.
Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0:
remove_conflicting_pci_framebuffers: bar 0: 0xe0000000 -> 0xefffffff
Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0:
remove_conflicting_pci_framebuffers: bar 2: 0xf0000000 -> 0xf01fffff
Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0:
remove_conflicting_pci_framebuffers: bar 5: 0xfb600000 -> 0xfb67ffff
Sep 14 20:52:49 ezra.blanchardmorris.net kernel: fb0: switching to amdgpudr=
mfb
from EFI VGA
Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: vgaar=
b:
deactivate vga console
Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: No mo=
re
image in the PCI ROM
Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: VRAM:
8176M 0x000000F400000000 - 0x000000F5FEFFFFFF (8176M used)
Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: GART:
512M 0x0000000000000000 - 0x000000001FFFFFFF
Sep 14 20:52:49 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: AGP:
267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF
Sep 14 20:52:49 ezra.blanchardmorris.net kernel: [drm] amdgpu: 8176M of VRAM
memory ready
Sep 14 20:52:49 ezra.blanchardmorris.net kernel: [drm] amdgpu: 8176M of GTT
memory ready.
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: fbcon: amdgpudrmfb (fb0) is
primary device
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: fb0:
amdgpudrmfb frame buffer device
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring =
gfx
uses VM inv eng 0 on hub 0
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.0.0 uses VM inv eng 1 on hub 0
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.1.0 uses VM inv eng 4 on hub 0
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.2.0 uses VM inv eng 5 on hub 0
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.3.0 uses VM inv eng 6 on hub 0
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.0.1 uses VM inv eng 7 on hub 0
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.1.1 uses VM inv eng 8 on hub 0
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.2.1 uses VM inv eng 9 on hub 0
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
comp_1.3.1 uses VM inv eng 10 on hub 0
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
kiq_2.1.0 uses VM inv eng 11 on hub 0
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
sdma0 uses VM inv eng 0 on hub 1
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
page0 uses VM inv eng 1 on hub 1
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
sdma1 uses VM inv eng 4 on hub 1
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
page1 uses VM inv eng 5 on hub 1
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
uvd_0 uses VM inv eng 6 on hub 1
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
uvd_enc_0.0 uses VM inv eng 7 on hub 1
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring
uvd_enc_0.1 uses VM inv eng 8 on hub 1
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring =
vce0
uses VM inv eng 9 on hub 1
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring =
vce1
uses VM inv eng 10 on hub 1
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: ring =
vce2
uses VM inv eng 11 on hub 1
Sep 14 20:52:50 ezra.blanchardmorris.net kernel: [drm] Initialized amdgpu
3.32.0 20150101 for 0000:06:00.0 on minor 0
Sep 14 20:53:20 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1928]:
Kernel command line: BOOT_IMAGE=3D(hd4,gpt6)/vmlinuz-5.2.13-200.fc30.x86_64
root=3DUUID=3De7b8b34a-e17f-4c2b-b223-eaa636249d2d ro
resume=3DUUID=3D52cc8cd8-b06f-4613-8781-a105d0ebf44a rhgb quiet amdgpu.vm_d=
ebug=3D1
Sep 14 20:53:20 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1928]:=
=20=20=20=20=20
   loading driver: amdgpu
Sep 14 20:53:20 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1928]: =
(=3D=3D)
Matched amdgpu as autoconfigured driver 0
Sep 14 20:53:20 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1928]: =
(II)
LoadModule: "amdgpu"
Sep 14 20:53:20 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1928]: =
(II)
Loading /usr/lib64/xorg/modules/drivers/amdgpu_drv.so
Sep 14 20:53:20 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1928]: =
(II)
Module amdgpu: vendor=3D"X.Org Foundation"
Sep 14 20:53:20 ezra.blanchardmorris.net /usr/libexec/gdm-x-session[1928]:=
=20=20=20=20=20
   All GPUs supported by the amdgpu kernel driver
Sep 14 22:21:05 ezra.blanchardmorris.net kernel:
[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed
out or interrupted!
Sep 14 22:21:05 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout
[amdgpu]] *ERROR* ring page1 timeout, signaled seq=3D97861046, emitted
seq=3D97861048
Sep 14 22:21:05 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout
[amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
Sep 14 22:21:05 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: GPU r=
eset
begin!
Sep 14 22:21:05 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D1321512, emitted seq=3D1=
321513
Sep 14 22:21:05 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout
[amdgpu]] *ERROR* Process information: process stellaris pid 5624 thread
stellaris:cs0 pid 5625
Sep 14 22:21:05 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: GPU r=
eset
begin!
Sep 14 22:21:15 ezra.blanchardmorris.net kernel: [drm:amdgpu_dm_atomic_check
[amdgpu]] *ERROR* [CRTC:47:crtc-0] hw_done or flip_done timed out
Sep 14 22:21:36 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Sep 14 22:21:36 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed
message: 0xe, input parameter: 0x0, error code: 0x0
Sep 14 22:21:36 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Sep 14 22:21:37 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu

You are receiving this mail because:
  • You are the assignee for the bug.
= --15685221431.26bed45A.8675-- --===============0927999402== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0927999402==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 21 Sep 2019 02:05:52 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1779601911==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id DF6FC6E0A5 for ; Sat, 21 Sep 2019 06:55:15 +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 --===============1779601911== Content-Type: multipart/alternative; boundary="15690315520.cc4C3.4223" Content-Transfer-Encoding: 7bit --15690315520.cc4C3.4223 Date: Sat, 21 Sep 2019 02:05:52 +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=3D109955 --- Comment #103 from Mauro Gaspari --- (In reply to Rodney A Morris from comment #101) > (In reply to Rodney A Morris from comment #99) > > Created attachment 145366 [details] > > apitrace of Hearts of Iron IV hard lock > >=20 > > Apitrace from hard lock playing Hearts of Iron IV without Steam. The r= eplay > > from this trace will hard lock the computer, though inconsistently. I'= ve > > replayed the trace three times. The replay hard locked computer one tim= e. >=20 > neofetch from hardlock: >=20 > /:-------------:\=20=20=20=20=20=20=20=20=20=20 > :-------------------:: --------------------------------=20 > :-----------/shhOHbmp---:\ OS: Fedora release 30 (Thirty) x86_6= 4=20 > /-----------omMMMNNNMMD ---: Kernel: 5.2.13-200.fc30.x86_64=20 > :-----------sMMMMNMNMP. ---: Uptime: 25 mins=20 > :-----------:MMMdP------- ---\ Packages: 2202 (rpm), 27 (flatpak)=20 > ,------------:MMMd-------- ---: Shell: bash 5.0.7=20 > :------------:MMMd------- .---: Resolution: 2560x1440=20 > :---- oNMMMMMMMMMNho .----: DE: GNOME 3.32.2=20 > :-- .+shhhMMMmhhy++ .------/ WM: GNOME Shell=20 > :- -------:MMMd--------------: WM Theme: Adwaita=20 > :- --------/MMMd-------------; Theme: Adapta-Nokto-Eta [GTK2/3]=20 > :- ------/hMMMy------------: Icons: Adwaita [GTK2/3]=20 > :-- :dMNdhhdNMMNo------------; Terminal: tilix=20 > :---:sdNMMMMNds:------------: CPU: Intel i7-6850K (12) @ 4.000GHz= =20 > :------:://:-------------:: GPU: AMD ATI Radeon RX Vega 56/64=20 > :---------------------:// Memory: 2478MiB / 32084MiB=20 >=20 > OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6 >=20 > Note: hard lock replayed occurred when the Discord flatpak is also runni= ng. I also noticed some errors that pointed to discord in my logs. In my case discord was installed via .deb package.=20 Could you please try and disable hardware acceleration in discord settings - appearance menu? Please let me know if it helps or changes anything.=20 Thanks! --=20 You are receiving this mail because: You are the assignee for the bug.= --15690315520.cc4C3.4223 Date: Sat, 21 Sep 2019 02:05:52 +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 # 103 on bug 10995= 5 from = Mauro Gaspari 
(In reply to Rodney A Morris from comment #101)
> (In reply to Rodney A Morris from comment #99)
> > Created att=
achment 145366 [details]
> > apitrace of Hearts of Iron IV hard lock
> >=20
> > Apitrace from hard lock playing Hearts of Iron IV without Steam. =
 The replay
> > from this trace will hard lock the computer, though inconsistentl=
y.  I've
> > replayed the trace three times. The replay hard locked computer o=
ne time.
>=20
> neofetch from hardlock:
>=20
>           /:-------------:\=20=20=20=20=20=20=20=20=20=20
>        :-------------------::        --------------------------------=
=20
>      :-----------/shhOHbmp---:\      OS: Fedora release 30 (Thirty) x8=
6_64=20
>    /-----------omMMMNNNMMD  ---:     Kernel: 5.2.13-200.fc30.x86_64=20
>   :-----------sMMMMNMNMP.    ---:    Uptime: 25 mins=20
>  :-----------:MMMdP-------    ---\   Packages: 2202 (rpm), 27 (flatpak=
)=20
> ,------------:MMMd--------    ---:   Shell: bash 5.0.7=20
> :------------:MMMd-------    .---:   Resolution: 2560x1440=20
> :----    oNMMMMMMMMMNho     .----:   DE: GNOME 3.32.2=20
> :--     .+shhhMMMmhhy++   .------/   WM: GNOME Shell=20
> :-    -------:MMMd--------------:    WM Theme: Adwaita=20
> :-   --------/MMMd-------------;     Theme: Adapta-Nokto-Eta [GTK2/3]=
=20
> :-    ------/hMMMy------------:      Icons: Adwaita [GTK2/3]=20
> :-- :dMNdhhdNMMNo------------;       Terminal: tilix=20
> :---:sdNMMMMNds:------------:        CPU: Intel i7-6850K (12) @ 4.=
000GHz=20
> :------:://:-------------::          GPU: AMD ATI Radeon RX Vega 56/64=
=20
> :---------------------://            Memory: 2478MiB / 32084MiB=20
>=20
> OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6
>=20
> Note:  hard lock replayed occurred when the Discord flatpak is also ru=
nning.

I also noticed some errors that pointed to discord in my logs. In my case
discord was installed via .deb package.=20
Could you please try and disable hardware acceleration in discord settings -
appearance menu? Please let me know if it helps or changes anything.=20
Thanks!

You are receiving this mail because:
  • You are the assignee for the bug.
= --15690315520.cc4C3.4223-- --===============1779601911== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1779601911==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 23 Sep 2019 02:49:08 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1422372743==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id CA3D26E0EC for ; Mon, 23 Sep 2019 02:49:08 +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 --===============1422372743== Content-Type: multipart/alternative; boundary="15692069487.FfEAE27.19365" Content-Transfer-Encoding: 7bit --15692069487.FfEAE27.19365 Date: Mon, 23 Sep 2019 02:49:08 +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=3D109955 --- Comment #104 from Rodney A Morris --- (In reply to Mauro Gaspari from comment #103) > (In reply to Rodney A Morris from comment #101) > > (In reply to Rodney A Morris from comment #99) > > > Created attachment 145366 [details] > > > apitrace of Hearts of Iron IV hard lock > > >=20 > > > Apitrace from hard lock playing Hearts of Iron IV without Steam. The= replay > > > from this trace will hard lock the computer, though inconsistently. = I've > > > replayed the trace three times. The replay hard locked computer one t= ime. > >=20 > > neofetch from hardlock: > >=20 > > /:-------------:\=20=20=20=20=20=20=20=20=20=20 > > :-------------------:: --------------------------------=20 > > :-----------/shhOHbmp---:\ OS: Fedora release 30 (Thirty) x86= _64=20 > > /-----------omMMMNNNMMD ---: Kernel: 5.2.13-200.fc30.x86_64=20 > > :-----------sMMMMNMNMP. ---: Uptime: 25 mins=20 > > :-----------:MMMdP------- ---\ Packages: 2202 (rpm), 27 (flatpak)= =20 > > ,------------:MMMd-------- ---: Shell: bash 5.0.7=20 > > :------------:MMMd------- .---: Resolution: 2560x1440=20 > > :---- oNMMMMMMMMMNho .----: DE: GNOME 3.32.2=20 > > :-- .+shhhMMMmhhy++ .------/ WM: GNOME Shell=20 > > :- -------:MMMd--------------: WM Theme: Adwaita=20 > > :- --------/MMMd-------------; Theme: Adapta-Nokto-Eta [GTK2/3]=20 > > :- ------/hMMMy------------: Icons: Adwaita [GTK2/3]=20 > > :-- :dMNdhhdNMMNo------------; Terminal: tilix=20 > > :---:sdNMMMMNds:------------: CPU: Intel i7-6850K (12) @ 4.000GH= z=20 > > :------:://:-------------:: GPU: AMD ATI Radeon RX Vega 56/64= =20 > > :---------------------:// Memory: 2478MiB / 32084MiB=20 > >=20 > > OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6 > >=20 > > Note: hard lock replayed occurred when the Discord flatpak is also run= ning. >=20 > I also noticed some errors that pointed to discord in my logs. In my case > discord was installed via .deb package.=20 > Could you please try and disable hardware acceleration in discord setting= s - > appearance menu? Please let me know if it helps or changes anything.=20 > Thanks! I have disabled hardware acceleration in discord settings to see if that improves my experience and report back my results. I am doubtful that it w= ill help much. At least on the 5.2.11 kernel, I had lockups with or without discord running. Discord running just seemed to make the problem appear mo= re consistently. --=20 You are receiving this mail because: You are the assignee for the bug.= --15692069487.FfEAE27.19365 Date: Mon, 23 Sep 2019 02:49:08 +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 # 104 on bug 10995= 5 from Rodney A Morris 
(In reply to Mauro Gaspari from comment #103)
> (In reply to Rodney A Morris from comment #101)
> > (In reply to Rodney A Morris from comment #99)
> > > Created [details]
> > > apitrace of Hearts of Iron IV hard lock
> > >=20
> > > Apitrace from hard lock playing Hearts of Iron IV without St=
eam.  The replay
> > > from this trace will hard lock the computer, though inconsis=
tently.  I've
> > > replayed the trace three times. The replay hard locked compu=
ter one time.
> >=20
> > neofetch from hardlock:
> >=20
> >           /:-------------:\=20=20=20=20=20=20=20=20=20=20
> >        :-------------------::        ----------------------------=
----=20
> >      :-----------/shhOHbmp---:\      OS: Fedora release 30 (Thirt=
y) x86_64=20
> >    /-----------omMMMNNNMMD  ---:     Kernel: 5.2.13-200.fc30.x86_=
64=20
> >   :-----------sMMMMNMNMP.    ---:    Uptime: 25 mins=20
> >  :-----------:MMMdP-------    ---\   Packages: 2202 (rpm), 27 (fl=
atpak)=20
> > ,------------:MMMd--------    ---:   Shell: bash 5.0.7=20
> > :------------:MMMd-------    .---:   Resolution: 2560x1440=20
> > :----    oNMMMMMMMMMNho     .----:   DE: GNOME 3.32.2=20
> > :--     .+shhhMMMmhhy++   .------/   WM: GNOME Shell=20
> > :-    -------:MMMd--------------:    WM Theme: Adwaita=20
> > :-   --------/MMMd-------------;     Theme: Adapta-Nokto-Eta [GTK=
2/3]=20
> > :-    ------/hMMMy------------:      Icons: Adwaita [GTK2/3]=20
> > :-- :dMNdhhdNMMNo------------;       Terminal: tilix=20
> > :---:sdNMMMMNds:------------:        CPU: Intel i7-6850K (12) =
4; 4.000GHz=20
> > :------:://:-------------::          GPU: AMD ATI Radeon RX Vega =
56/64=20
> > :---------------------://            Memory: 2478MiB / 32084MiB=20
> >=20
> > OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6
> >=20
> > Note:  hard lock replayed occurred when the Discord flatpak is al=
so running.
>=20
> I also noticed some errors that pointed to discord in my logs. In my c=
ase
> discord was installed via .deb package.=20
> Could you please try and disable hardware acceleration in discord sett=
ings -
> appearance menu? Please let me know if it helps or changes anything.=20
> Thanks!

I have disabled hardware acceleration in discord settings to see if that
improves my experience and report back my results.  I am doubtful that it w=
ill
help much.  At least on the 5.2.11 kernel, I had lockups with or without
discord running.  Discord running just seemed to make the problem appear mo=
re
consistently.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15692069487.FfEAE27.19365-- --===============1422372743== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1422372743==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 23 Sep 2019 03:06:55 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1508033586==" 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 7F8106E0DD for ; Mon, 23 Sep 2019 03:06:56 +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 --===============1508033586== Content-Type: multipart/alternative; boundary="15692080164.636c0.22561" Content-Transfer-Encoding: 7bit --15692080164.636c0.22561 Date: Mon, 23 Sep 2019 03:06:56 +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=3D109955 --- Comment #105 from Rodney A Morris --- Created attachment 145462 --> https://bugs.freedesktop.org/attachment.cgi?id=3D145462&action=3Dedit dmesg from Stellaris crash 2019-09-20 I had another lockup on Friday while playing Stellaris again. This time I = had the debug kernel running and the mesa debug packages installed. I do not p= lan to post dmesg and journalctl dumps for future crashes unless the logs indi= cate a new problem, or I can obtain more information than I previously provided.= =20 Like the crash I reported for Hearts of Iron IV, this Stellaris crash seems= to be caused by a circular lock dependency. If someone believes my problems are caused by faulty hardware, please let me know. As an FYI, this problem does not seem to manifest under Windows 10, playing the same game. Card: Sapphire Radeon Vega 64 OS Info: /:-------------:\=20=20=20=20=20=20=20=20=20=20=20 :-------------------:: --------------------------------=20 :-----------/shhOHbmp---:\ OS: Fedora release 30 (Thirty) x86_64= =20 /-----------omMMMNNNMMD ---: Kernel: 5.2.15-200.fc30.x86_64=20 :-----------sMMMMNMNMP. ---: Uptime: 1 day, 22 hours, 37 mins=20 :-----------:MMMdP------- ---\ Packages: 2211 (rpm), 30 (flatpak)=20 ,------------:MMMd-------- ---: Shell: bash 5.0.7=20 :------------:MMMd------- .---: Resolution: 2560x1440=20 :---- oNMMMMMMMMMNho .----: DE: GNOME 3.32.2=20 :-- .+shhhMMMmhhy++ .------/ WM: Mutter=20 :- -------:MMMd--------------: WM Theme: Adwaita=20 :- --------/MMMd-------------; Theme: Adapta-Nokto-Eta [GTK2/3]=20 :- ------/hMMMy------------: Icons: Adwaita [GTK2/3]=20 :-- :dMNdhhdNMMNo------------; Terminal: tilix=20 :---:sdNMMMMNds:------------: CPU: Intel i7-6850K (12) @ 4.000GHz=20 :------:://:-------------:: GPU: AMD ATI Radeon RX Vega 56/64=20 :---------------------:// Memory: 3097MiB / 32084MiB=20 Mesa info: OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6 Game being played: Stellaris through steam for Linux Native or Wine: Native Crash Type: Screen goes black suddenly while music continues plays for less than a minu= te; music begins to loop; and computer reboots. Full dmesg attached. Pertinent part of dmesg with debug kernel: [ 2383.732727] perf: interrupt took too long (2502 > 2500), lowering kernel.perf_event_max_sample_rate to 79000 [ 2923.530873] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting = for fences timed out or interrupted! [ 2928.651952] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring page1 timeou= t, signaled seq=3D51954680, emitted seq=3D51954682 [ 2928.652090] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati= on: process pid 0 thread pid 0 [ 2928.652098] amdgpu 0000:06:00.0: GPU reset begin! [ 2928.661852] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D734676, emitted seq=3D734677 [ 2928.661898] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati= on: process stellaris pid 5395 thread stellaris:cs0 pid 5397 [ 2928.661901] amdgpu 0000:06:00.0: GPU reset begin! [ 2928.661997] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D [ 2928.661999] WARNING: possible circular locking dependency detected [ 2928.662003] 5.2.15-200.fc30.x86_64+debug #1 Not tainted [ 2928.662005] ------------------------------------------------------ [ 2928.662007] kworker/10:2/974 is trying to acquire lock: [ 2928.662010] 00000000d514cf70 (&(&ring->fence_drv.lock)->rlock){-.-.}, at: dma_fence_remove_callback+0x1a/0x60 [ 2928.662021]=20 but task is already holding lock: [ 2928.662023] 00000000e6ce7c0d (&(&sched->job_list_lock)->rlock){-.-.}, at: drm_sched_stop+0x34/0x130 [gpu_sched] [ 2928.662031]=20 which lock already depends on the new lock. [ 2928.662033]=20 the existing dependency chain (in reverse order) is: [ 2928.662035]=20 -> #1 (&(&sched->job_list_lock)->rlock){-.-.}: [ 2928.662044] _raw_spin_lock_irqsave+0x49/0x83 [ 2928.662049] drm_sched_process_job+0x4d/0x180 [gpu_sched] [ 2928.662052] dma_fence_signal+0x111/0x1a0 [ 2928.662128] amdgpu_fence_process+0xa3/0x100 [amdgpu] [ 2928.662223] sdma_v4_0_process_trap_irq+0x8d/0xa0 [amdgpu] [ 2928.662310] amdgpu_irq_dispatch+0xc0/0x250 [amdgpu] [ 2928.662398] amdgpu_ih_process+0x8d/0x110 [amdgpu] [ 2928.662482] amdgpu_irq_handler+0x1b/0x50 [amdgpu] [ 2928.662487] __handle_irq_event_percpu+0x3f/0x290 [ 2928.662491] handle_irq_event_percpu+0x31/0x80 [ 2928.662495] handle_irq_event+0x34/0x51 [ 2928.662498] handle_edge_irq+0x83/0x1a0 [ 2928.662502] handle_irq+0x1c/0x30 [ 2928.662507] do_IRQ+0x61/0x120 [ 2928.662511] ret_from_intr+0x0/0x22 [ 2928.662517] cpuidle_enter_state+0xc9/0x450 [ 2928.662519] cpuidle_enter+0x29/0x40 [ 2928.662524] do_idle+0x1ec/0x280 [ 2928.662528] cpu_startup_entry+0x19/0x20 [ 2928.662531] start_secondary+0x189/0x1e0 [ 2928.662537] secondary_startup_64+0xa4/0xb0 [ 2928.662539]=20 -> #0 (&(&ring->fence_drv.lock)->rlock){-.-.}: [ 2928.662548] lock_acquire+0xa2/0x1b0 [ 2928.662551] _raw_spin_lock_irqsave+0x49/0x83 [ 2928.662555] dma_fence_remove_callback+0x1a/0x60 [ 2928.662560] drm_sched_stop+0x59/0x130 [gpu_sched] [ 2928.662709] amdgpu_device_pre_asic_reset+0x41/0x20c [amdgpu] [ 2928.662866] amdgpu_device_gpu_recover+0x77/0x788 [amdgpu] [ 2928.663007] amdgpu_job_timedout+0x109/0x130 [amdgpu] [ 2928.663018] drm_sched_job_timedout+0x40/0x70 [gpu_sched] [ 2928.663024] process_one_work+0x272/0x5e0 [ 2928.663029] worker_thread+0x50/0x3b0 [ 2928.663037] kthread+0x108/0x140 [ 2928.663045] ret_from_fork+0x3a/0x50 [ 2928.663048]=20 other info that might help us debug this: [ 2928.663051] Possible unsafe locking scenario: [ 2928.663055] CPU0 CPU1 [ 2928.663059] ---- ---- [ 2928.663062] lock(&(&sched->job_list_lock)->rlock); [ 2928.663068]=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 lock(&(&ring->fence_drv.lock)->rlock); [ 2928.663072]=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 lock(&(&sched->job_list_lock)->rlock); [ 2928.663076] lock(&(&ring->fence_drv.lock)->rlock); [ 2928.663080]=20 *** DEADLOCK *** [ 2928.663085] 5 locks held by kworker/10:2/974: [ 2928.663090] #0: 0000000057c9a435 ((wq_completion)events){+.+.}, at: process_one_work+0x1e9/0x5e0 [ 2928.663100] #1: 00000000aadd5dda ((work_completion)(&(&sched->work_tdr)->work)){+.+.}, at: process_one_work+0x1e9/0x5e0 [ 2928.663108] #2: 0000000007db378b (&adev->lock_reset){+.+.}, at: amdgpu_device_lock_adev+0x17/0x39 [amdgpu] [ 2928.663261] #3: 000000001e0a2926 (&dqm->lock_hidden){+.+.}, at: kgd2kfd_pre_reset+0x30/0x60 [amdgpu] [ 2928.663392] #4: 00000000e6ce7c0d (&(&sched->job_list_lock)->rlock){-.-.= }, at: drm_sched_stop+0x34/0x130 [gpu_sched] [ 2928.663403]=20 stack backtrace: [ 2928.663409] CPU: 10 PID: 974 Comm: kworker/10:2 Not tainted 5.2.15-200.fc30.x86_64+debug #1 [ 2928.663413] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M.= /X99 Taichi, BIOS P1.80 04/06/2018 [ 2928.663423] Workqueue: events drm_sched_job_timedout [gpu_sched] [ 2928.663428] Call Trace: [ 2928.663442] dump_stack+0x85/0xc0 [ 2928.663453] print_circular_bug.cold+0x15c/0x195 [ 2928.663462] __lock_acquire+0x167c/0x1c90 [ 2928.663475] lock_acquire+0xa2/0x1b0 [ 2928.663482] ? dma_fence_remove_callback+0x1a/0x60 [ 2928.663494] _raw_spin_lock_irqsave+0x49/0x83 [ 2928.663499] ? dma_fence_remove_callback+0x1a/0x60 [ 2928.663506] dma_fence_remove_callback+0x1a/0x60 [ 2928.663515] drm_sched_stop+0x59/0x130 [gpu_sched] [ 2928.663663] amdgpu_device_pre_asic_reset+0x41/0x20c [amdgpu] [ 2928.663818] amdgpu_device_gpu_recover+0x77/0x788 [amdgpu] [ 2928.663960] amdgpu_job_timedout+0x109/0x130 [amdgpu] [ 2928.663974] drm_sched_job_timedout+0x40/0x70 [gpu_sched] [ 2928.663981] process_one_work+0x272/0x5e0 [ 2928.663991] worker_thread+0x50/0x3b0 [ 2928.664000] kthread+0x108/0x140 [ 2928.664005] ? process_one_work+0x5e0/0x5e0 [ 2928.664011] ? kthread_park+0x80/0x80 [ 2928.664021] ret_from_fork+0x3a/0x50 [ 2928.681831] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 2928.681846] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 2928.681851] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 2928.681857] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 2928.681963] pcieport 0000:00:03.0: AER: Device recovery failed [ 2933.771664] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out [ 2938.890758] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-= 0] hw_done or flip_done timed out [ 2939.118467] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 2939.118475] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 2939.118477] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 2939.118479] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 2939.118536] pcieport 0000:00:03.0: AER: Device recovery failed [ 2939.141034] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 2939.369014] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 2939.369018] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 2939.369021] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 2939.369072] pcieport 0000:00:03.0: AER: Device recovery failed [ 2939.369075] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 2939.597051] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 2939.597055] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 2939.597057] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 2939.597103] pcieport 0000:00:03.0: AER: Device recovery failed [ 2939.597106] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal) error received: 0000:00:03.0 systemd logs: Nothing interesting appears in the logs, not even the information from dmes= g.=20 I'm unsure if systemd captured anything from the crash. --=20 You are receiving this mail because: You are the assignee for the bug.= --15692080164.636c0.22561 Date: Mon, 23 Sep 2019 03:06:56 +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 # 105 on bug 10995= 5 from Rodney A Morris 
Created at=
tachment 145462 [details]
dmesg from Stellaris crash 2019-09-20

I had another lockup on Friday while playing Stellaris again.  This time I =
had
the debug kernel running and the mesa debug packages installed.  I do not p=
lan
to post dmesg and journalctl dumps for future crashes unless the logs  indi=
cate
a new problem, or I can obtain more information than I previously provided.=
=20
Like the crash I reported for Hearts of Iron IV, this Stellaris crash seems=
 to
be caused by a circular lock dependency.

If someone believes my problems are caused by faulty hardware, please let me
know.  As an FYI, this problem does not seem to manifest under Windows 10,
playing the same game.

Card:

Sapphire Radeon Vega 64

OS Info:

          /:-------------:\=20=20=20=20=20=20=20=20=20=20=20
       :-------------------::        --------------------------------=20
     :-----------/shhOHbmp---:\      OS: Fedora release 30 (Thirty) x86_64=
=20
   /-----------omMMMNNNMMD  ---:     Kernel: 5.2.15-200.fc30.x86_64=20
  :-----------sMMMMNMNMP.    ---:    Uptime: 1 day, 22 hours, 37 mins=20
 :-----------:MMMdP-------    ---\   Packages: 2211 (rpm), 30 (flatpak)=20
,------------:MMMd--------    ---:   Shell: bash 5.0.7=20
:------------:MMMd-------    .---:   Resolution: 2560x1440=20
:----    oNMMMMMMMMMNho     .----:   DE: GNOME 3.32.2=20
:--     .+shhhMMMmhhy++   .------/   WM: Mutter=20
:-    -------:MMMd--------------:    WM Theme: Adwaita=20
:-   --------/MMMd-------------;     Theme: Adapta-Nokto-Eta [GTK2/3]=20
:-    ------/hMMMy------------:      Icons: Adwaita [GTK2/3]=20
:-- :dMNdhhdNMMNo------------;       Terminal: tilix=20
:---:sdNMMMMNds:------------:        CPU: Intel i7-6850K (12) @ 4.000GH=
z=20
:------:://:-------------::          GPU: AMD ATI Radeon RX Vega 56/64=20
:---------------------://            Memory: 3097MiB / 32084MiB=20

Mesa info:

OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6

Game being played:

Stellaris through steam for Linux

Native or Wine:

Native

Crash Type:

Screen goes black suddenly while music continues plays for less than a minu=
te;
music begins to loop; and computer reboots.

Full dmesg attached.  Pertinent part of dmesg with debug kernel:

[ 2383.732727] perf: interrupt took too long (2502 > 2500), lowering
kernel.perf_event_max_sample_rate to 79000
[ 2923.530873] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting =
for
fences timed out or interrupted!
[ 2928.651952] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring page1 timeou=
t,
signaled seq=3D51954680, emitted seq=3D51954682
[ 2928.652090] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati=
on:
process  pid 0 thread  pid 0
[ 2928.652098] amdgpu 0000:06:00.0: GPU reset begin!
[ 2928.661852] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=3D734676, emitted seq=3D734677
[ 2928.661898] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati=
on:
process stellaris pid 5395 thread stellaris:cs0 pid 5397
[ 2928.661901] amdgpu 0000:06:00.0: GPU reset begin!

[ 2928.661997] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
[ 2928.661999] WARNING: possible circular locking dependency detected
[ 2928.662003] 5.2.15-200.fc30.x86_64+debug #1 Not tainted
[ 2928.662005] ------------------------------------------------------
[ 2928.662007] kworker/10:2/974 is trying to acquire lock:
[ 2928.662010] 00000000d514cf70 (&(&ring->fence_drv.lock)->rl=
ock){-.-.}, at:
dma_fence_remove_callback+0x1a/0x60
[ 2928.662021]=20
               but task is already holding lock:
[ 2928.662023] 00000000e6ce7c0d (&(&sched->job_list_lock)->rl=
ock){-.-.}, at:
drm_sched_stop+0x34/0x130 [gpu_sched]
[ 2928.662031]=20
               which lock already depends on the new lock.

[ 2928.662033]=20
               the existing dependency chain (in reverse order) is:
[ 2928.662035]=20
               -> #1 (&(&sched->job_list_lock)->rlock){-.-=
.}:
[ 2928.662044]        _raw_spin_lock_irqsave+0x49/0x83
[ 2928.662049]        drm_sched_process_job+0x4d/0x180 [gpu_sched]
[ 2928.662052]        dma_fence_signal+0x111/0x1a0
[ 2928.662128]        amdgpu_fence_process+0xa3/0x100 [amdgpu]
[ 2928.662223]        sdma_v4_0_process_trap_irq+0x8d/0xa0 [amdgpu]
[ 2928.662310]        amdgpu_irq_dispatch+0xc0/0x250 [amdgpu]
[ 2928.662398]        amdgpu_ih_process+0x8d/0x110 [amdgpu]
[ 2928.662482]        amdgpu_irq_handler+0x1b/0x50 [amdgpu]
[ 2928.662487]        __handle_irq_event_percpu+0x3f/0x290
[ 2928.662491]        handle_irq_event_percpu+0x31/0x80
[ 2928.662495]        handle_irq_event+0x34/0x51
[ 2928.662498]        handle_edge_irq+0x83/0x1a0
[ 2928.662502]        handle_irq+0x1c/0x30
[ 2928.662507]        do_IRQ+0x61/0x120
[ 2928.662511]        ret_from_intr+0x0/0x22
[ 2928.662517]        cpuidle_enter_state+0xc9/0x450
[ 2928.662519]        cpuidle_enter+0x29/0x40
[ 2928.662524]        do_idle+0x1ec/0x280
[ 2928.662528]        cpu_startup_entry+0x19/0x20
[ 2928.662531]        start_secondary+0x189/0x1e0
[ 2928.662537]        secondary_startup_64+0xa4/0xb0
[ 2928.662539]=20
               -> #0 (&(&ring->fence_drv.lock)->rlock){-.-=
.}:
[ 2928.662548]        lock_acquire+0xa2/0x1b0
[ 2928.662551]        _raw_spin_lock_irqsave+0x49/0x83
[ 2928.662555]        dma_fence_remove_callback+0x1a/0x60
[ 2928.662560]        drm_sched_stop+0x59/0x130 [gpu_sched]
[ 2928.662709]        amdgpu_device_pre_asic_reset+0x41/0x20c [amdgpu]
[ 2928.662866]        amdgpu_device_gpu_recover+0x77/0x788 [amdgpu]
[ 2928.663007]        amdgpu_job_timedout+0x109/0x130 [amdgpu]
[ 2928.663018]        drm_sched_job_timedout+0x40/0x70 [gpu_sched]
[ 2928.663024]        process_one_work+0x272/0x5e0
[ 2928.663029]        worker_thread+0x50/0x3b0
[ 2928.663037]        kthread+0x108/0x140
[ 2928.663045]        ret_from_fork+0x3a/0x50
[ 2928.663048]=20
               other info that might help us debug this:

[ 2928.663051]  Possible unsafe locking scenario:

[ 2928.663055]        CPU0                    CPU1
[ 2928.663059]        ----                    ----
[ 2928.663062]   lock(&(&sched->job_list_lock)->rlock);
[ 2928.663068]=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20
lock(&(&ring->fence_drv.lock)->rlock);
[ 2928.663072]=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20
lock(&(&sched->job_list_lock)->rlock);
[ 2928.663076]   lock(&(&ring->fence_drv.lock)->rlock);
[ 2928.663080]=20
                *** DEADLOCK ***

[ 2928.663085] 5 locks held by kworker/10:2/974:
[ 2928.663090]  #0: 0000000057c9a435 ((wq_completion)events){+.+.}, at:
process_one_work+0x1e9/0x5e0
[ 2928.663100]  #1: 00000000aadd5dda
((work_completion)(&(&sched->work_tdr)->work)){+.+.}, at:
process_one_work+0x1e9/0x5e0
[ 2928.663108]  #2: 0000000007db378b (&adev->lock_reset){+.+.}, at:
amdgpu_device_lock_adev+0x17/0x39 [amdgpu]
[ 2928.663261]  #3: 000000001e0a2926 (&dqm->lock_hidden){+.+.}, at:
kgd2kfd_pre_reset+0x30/0x60 [amdgpu]
[ 2928.663392]  #4: 00000000e6ce7c0d (&(&sched->job_list_lock)-&=
gt;rlock){-.-.},
at: drm_sched_stop+0x34/0x130 [gpu_sched]
[ 2928.663403]=20
               stack backtrace:
[ 2928.663409] CPU: 10 PID: 974 Comm: kworker/10:2 Not tainted
5.2.15-200.fc30.x86_64+debug #1
[ 2928.663413] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M.=
/X99
Taichi, BIOS P1.80 04/06/2018
[ 2928.663423] Workqueue: events drm_sched_job_timedout [gpu_sched]
[ 2928.663428] Call Trace:
[ 2928.663442]  dump_stack+0x85/0xc0
[ 2928.663453]  print_circular_bug.cold+0x15c/0x195
[ 2928.663462]  __lock_acquire+0x167c/0x1c90
[ 2928.663475]  lock_acquire+0xa2/0x1b0
[ 2928.663482]  ? dma_fence_remove_callback+0x1a/0x60
[ 2928.663494]  _raw_spin_lock_irqsave+0x49/0x83
[ 2928.663499]  ? dma_fence_remove_callback+0x1a/0x60
[ 2928.663506]  dma_fence_remove_callback+0x1a/0x60
[ 2928.663515]  drm_sched_stop+0x59/0x130 [gpu_sched]
[ 2928.663663]  amdgpu_device_pre_asic_reset+0x41/0x20c [amdgpu]
[ 2928.663818]  amdgpu_device_gpu_recover+0x77/0x788 [amdgpu]
[ 2928.663960]  amdgpu_job_timedout+0x109/0x130 [amdgpu]
[ 2928.663974]  drm_sched_job_timedout+0x40/0x70 [gpu_sched]
[ 2928.663981]  process_one_work+0x272/0x5e0
[ 2928.663991]  worker_thread+0x50/0x3b0
[ 2928.664000]  kthread+0x108/0x140
[ 2928.664005]  ? process_one_work+0x5e0/0x5e0
[ 2928.664011]  ? kthread_park+0x80/0x80
[ 2928.664021]  ret_from_fork+0x3a/0x50
[ 2928.681831] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 2928.681846] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 2928.681851] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 2928.681857] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 2928.681963] pcieport 0000:00:03.0: AER: Device recovery failed
[ 2933.771664] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
*ERROR* [CRTC:47:crtc-0] flip_done timed out
[ 2938.890758] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-=
0]
hw_done or flip_done timed out
[ 2939.118467] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 2939.118475] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 2939.118477] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 2939.118479] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 2939.118536] pcieport 0000:00:03.0: AER: Device recovery failed
[ 2939.141034] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal)
error received: 0000:00:03.0
[ 2939.369014] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 2939.369018] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 2939.369021] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 2939.369072] pcieport 0000:00:03.0: AER: Device recovery failed
[ 2939.369075] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal)
error received: 0000:00:03.0
[ 2939.597051] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 2939.597055] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 2939.597057] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 2939.597103] pcieport 0000:00:03.0: AER: Device recovery failed
[ 2939.597106] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal)
error received: 0000:00:03.0

systemd logs:

Nothing interesting appears in the logs, not even the information from dmes=
g.=20
I'm unsure if systemd captured anything from the crash.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15692080164.636c0.22561-- --===============1508033586== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1508033586==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 26 Sep 2019 10:37:39 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1783187068==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 371916ED0C for ; Thu, 26 Sep 2019 10:37:40 +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 --===============1783187068== Content-Type: multipart/alternative; boundary="15694942602.CeDa6D.20098" Content-Transfer-Encoding: 7bit --15694942602.CeDa6D.20098 Date: Thu, 26 Sep 2019 10:37:40 +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=3D109955 --- Comment #106 from jeroenimo --- This is quite a severe bug.=20 I have reasonable stable system with Mint 19.2 (runs hours without a crash uname -a Linux jeroenimo-amd 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux (X)ubuntu 18.04 LTS LTS crashes a lot faster (1 or 2 minutes) 5.0.0.29 kern= el I can reproduce the bug with glmark2 instantly 100% of the times (https://launchpad.net/glmark2) or sudo apt install glmark2 I'm not very good at debugging but this is what my dmesg looks like when I = ssh and run glmark2 [ 6619.587749] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:45:crtc-1] flip_done timed out And that's it, no more info. --=20 You are receiving this mail because: You are the assignee for the bug.= --15694942602.CeDa6D.20098 Date: Thu, 26 Sep 2019 10:37:40 +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 # 106 on bug 10995= 5 from jeroenimo 
This is quite a severe bug.=20
I have reasonable stable system with Mint 19.2 (runs hours without a crash
uname -a
Linux jeroenimo-amd 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux


(X)ubuntu 18.04 LTS LTS crashes a lot faster (1 or 2 minutes) 5.0.0.29 kern=
el

I can reproduce the bug with glmark2 instantly 100% of the times

(https://launchpad.net/glmark2) or sudo apt install glmark2

I'm not very good at debugging but this is what my dmesg looks like when I =
ssh
and run glmark2

[ 6619.587749] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
*ERROR* [CRTC:45:crtc-1] flip_done timed out

And that's it, no more info.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15694942602.CeDa6D.20098-- --===============1783187068== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1783187068==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 26 Sep 2019 12:56:08 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0075087960==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 489B16ED12 for ; Thu, 26 Sep 2019 12:56:08 +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 --===============0075087960== Content-Type: multipart/alternative; boundary="15695025681.f76bf4.14644" Content-Transfer-Encoding: 7bit --15695025681.f76bf4.14644 Date: Thu, 26 Sep 2019 12:56:08 +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=3D109955 --- Comment #107 from jeroenimo --- I have a workaround that at least makes the system workable. After some testing I managed to run glmark2 at the lowest and second lowest clock speed on my RX560 >>From root: echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_level echo 1 > /sys/class/drm/card0/device/pp_dpm_sclk giving me this cat /sys/class/drm/card0/device/pp_dpm_sclk=20 0: 214Mhz=20 1: 387Mhz * 2: 843Mhz=20 3: 995Mhz=20 4: 1062Mhz=20 5: 1108Mhz=20 6: 1149Mhz=20 7: 1176Mhz=20 Obviously this decreases performance big time, but I don't really game so it makes my system usable. Any clock speeds over 4: 1062Mhz crashes my system immediately.. --=20 You are receiving this mail because: You are the assignee for the bug.= --15695025681.f76bf4.14644 Date: Thu, 26 Sep 2019 12:56:08 +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 # 107 on bug 10995= 5 from jeroenimo 
I have a workaround that at least makes the system workable.

After some testing I managed to run glmark2 at the lowest and second lowest
clock speed on my RX560

>>From root:
echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_le=
vel
echo 1 > /sys/class/drm/card0/device/pp_dpm_sclk

giving me this
cat /sys/class/drm/card0/device/pp_dpm_sclk=20
0: 214Mhz=20
1: 387Mhz *
2: 843Mhz=20
3: 995Mhz=20
4: 1062Mhz=20
5: 1108Mhz=20
6: 1149Mhz=20
7: 1176Mhz=20

Obviously this decreases performance big time, but I don't really game so it
makes my system usable.

Any clock speeds over 4: 1062Mhz crashes my system immediately..

You are receiving this mail because:
  • You are the assignee for the bug.
= --15695025681.f76bf4.14644-- --===============0075087960== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0075087960==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 28 Sep 2019 07:02:48 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1816098538==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id D30286E0D5 for ; Sat, 28 Sep 2019 07:02:48 +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 --===============1816098538== Content-Type: multipart/alternative; boundary="15696541689.fBCc.367" Content-Transfer-Encoding: 7bit --15696541689.fBCc.367 Date: Sat, 28 Sep 2019 07:02:48 +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=3D109955 --- Comment #108 from Wilko Bartels --- Did u try the amdgpu-pro driver as well? i just did four runs of glmark and it just went through for me. going up to 1600mhz shader clock. tested both closed and opensource drivers. vega pulse here. mesa result: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D glmark2 2014.03 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D OpenGL Information GL_VENDOR: X.Org GL_RENDERER: Radeon RX Vega (VEGA10, DRM 3.33.0, 5.3.1-arch1-1-ARCH, = LLVM 8.0.1) GL_VERSION: 4.5 (Compatibility Profile) Mesa 19.1.7 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D [build] use-vbo=3Dfalse: FPS: 8617 FrameTime: 0.116 ms [build] use-vbo=3Dtrue: FPS: 10534 FrameTime: 0.095 ms [texture] texture-filter=3Dnearest: FPS: 11214 FrameTime: 0.089 ms [texture] texture-filter=3Dlinear: FPS: 11274 FrameTime: 0.089 ms [texture] texture-filter=3Dmipmap: FPS: 10197 FrameTime: 0.098 ms [shading] shading=3Dgouraud: FPS: 9790 FrameTime: 0.102 ms [shading] shading=3Dblinn-phong-inf: FPS: 10979 FrameTime: 0.091 ms [shading] shading=3Dphong: FPS: 10167 FrameTime: 0.098 ms [shading] shading=3Dcel: FPS: 9662 FrameTime: 0.103 ms [bump] bump-render=3Dhigh-poly: FPS: 9830 FrameTime: 0.102 ms [bump] bump-render=3Dnormals: FPS: 10151 FrameTime: 0.099 ms [bump] bump-render=3Dheight: FPS: 10870 FrameTime: 0.092 ms libpng warning: iCCP: known incorrect sRGB profile [effect2d] kernel=3D0,1,0;1,-4,1;0,1,0;: FPS: 12008 FrameTime: 0.083 ms libpng warning: iCCP: known incorrect sRGB profile [effect2d] kernel=3D1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 10876 FrameTime: 0= .092 ms [pulsar] light=3Dfalse:quads=3D5:texture=3Dfalse: FPS: 10232 FrameTime: 0.0= 98 ms libpng warning: iCCP: known incorrect sRGB profile [desktop] blur-radius=3D5:effect=3Dblur:passes=3D1:separable=3Dtrue:windows= =3D4: FPS: 6842 FrameTime: 0.146 ms libpng warning: iCCP: known incorrect sRGB profile [desktop] effect=3Dshadow:windows=3D4: FPS: 7934 FrameTime: 0.126 ms [buffer] columns=3D200:interleave=3Dfalse:update-dispersion=3D0.9:update-fraction=3D= 0.5:update-method=3Dmap: FPS: 1770 FrameTime: 0.565 ms [buffer] columns=3D200:interleave=3Dfalse:update-dispersion=3D0.9:update-fraction=3D= 0.5:update-method=3Dsubdata: FPS: 2308 FrameTime: 0.433 ms [buffer] columns=3D200:interleave=3Dtrue:update-dispersion=3D0.9:update-fraction=3D0= .5:update-method=3Dmap: FPS: 1875 FrameTime: 0.533 ms [ideas] speed=3Dduration: FPS: 4475 FrameTime: 0.223 ms [jellyfish] : FPS: 9499 FrameTime: 0.105 ms [terrain] : FPS: 2593 FrameTime: 0.386 ms [shadow] : FPS: 9423 FrameTime: 0.106 ms [refract] : FPS: 6008 FrameTime: 0.166 ms [conditionals] fragment-steps=3D0:vertex-steps=3D0: FPS: 11364 FrameTime: 0= .088 ms [conditionals] fragment-steps=3D5:vertex-steps=3D0: FPS: 10816 FrameTime: 0= .092 ms [conditionals] fragment-steps=3D0:vertex-steps=3D5: FPS: 12000 FrameTime: 0= .083 ms [function] fragment-complexity=3Dlow:fragment-steps=3D5: FPS: 10932 FrameTi= me: 0.091 ms [function] fragment-complexity=3Dmedium:fragment-steps=3D5: FPS: 11690 Fram= eTime: 0.086 ms [loop] fragment-loop=3Dfalse:fragment-steps=3D5:vertex-steps=3D5: FPS: 11119 FrameTime: 0.090 ms [loop] fragment-steps=3D5:fragment-uniform=3Dfalse:vertex-steps=3D5: FPS: 1= 1003 FrameTime: 0.091 ms [loop] fragment-steps=3D5:fragment-uniform=3Dtrue:vertex-steps=3D5: FPS: 12= 886 FrameTime: 0.078 ms =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D glmark2 Score: 9119=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D amdgpu-pro result: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D glmark2 2014.03 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D OpenGL Information GL_VENDOR: ATI Technologies Inc. GL_RENDERER: Radeon RX Vega GL_VERSION: 4.6.13572 Compatibility Profile Context =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D [build] use-vbo=3Dfalse: FPS: 3727 FrameTime: 0.268 ms [build] use-vbo=3Dtrue: FPS: 9516 FrameTime: 0.105 ms [texture] texture-filter=3Dnearest: FPS: 7346 FrameTime: 0.136 ms [texture] texture-filter=3Dlinear: FPS: 9236 FrameTime: 0.108 ms [texture] texture-filter=3Dmipmap: FPS: 9161 FrameTime: 0.109 ms [shading] shading=3Dgouraud: FPS: 9184 FrameTime: 0.109 ms [shading] shading=3Dblinn-phong-inf: FPS: 9363 FrameTime: 0.107 ms [shading] shading=3Dphong: FPS: 9424 FrameTime: 0.106 ms [shading] shading=3Dcel: FPS: 9060 FrameTime: 0.110 ms [bump] bump-render=3Dhigh-poly: FPS: 9047 FrameTime: 0.111 ms [bump] bump-render=3Dnormals: FPS: 8804 FrameTime: 0.114 ms [bump] bump-render=3Dheight: FPS: 9156 FrameTime: 0.109 ms libpng warning: iCCP: known incorrect sRGB profile [effect2d] kernel=3D0,1,0;1,-4,1;0,1,0;: FPS: 9121 FrameTime: 0.110 ms libpng warning: iCCP: known incorrect sRGB profile [effect2d] kernel=3D1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 8866 FrameTime: 0.= 113 ms [pulsar] light=3Dfalse:quads=3D5:texture=3Dfalse: FPS: 8286 FrameTime: 0.12= 1 ms libpng warning: iCCP: known incorrect sRGB profile [desktop] blur-radius=3D5:effect=3Dblur:passes=3D1:separable=3Dtrue:windows= =3D4: FPS: 3789 FrameTime: 0.264 ms libpng warning: iCCP: known incorrect sRGB profile [desktop] effect=3Dshadow:windows=3D4: FPS: 4491 FrameTime: 0.223 ms [buffer] columns=3D200:interleave=3Dfalse:update-dispersion=3D0.9:update-fraction=3D= 0.5:update-method=3Dmap: FPS: 1026 FrameTime: 0.975 ms [buffer] columns=3D200:interleave=3Dfalse:update-dispersion=3D0.9:update-fraction=3D= 0.5:update-method=3Dsubdata: FPS: 2228 FrameTime: 0.449 ms [buffer] columns=3D200:interleave=3Dtrue:update-dispersion=3D0.9:update-fraction=3D0= .5:update-method=3Dmap: FPS: 1275 FrameTime: 0.784 ms [ideas] speed=3Dduration: FPS: 4038 FrameTime: 0.248 ms [jellyfish] : FPS: 7342 FrameTime: 0.136 ms [terrain] : FPS: 790 FrameTime: 1.266 ms [shadow] : FPS: 6002 FrameTime: 0.167 ms [refract] : FPS: 4273 FrameTime: 0.234 ms [conditionals] fragment-steps=3D0:vertex-steps=3D0: FPS: 9208 FrameTime: 0.= 109 ms [conditionals] fragment-steps=3D5:vertex-steps=3D0: FPS: 8964 FrameTime: 0.= 112 ms [conditionals] fragment-steps=3D0:vertex-steps=3D5: FPS: 8984 FrameTime: 0.= 111 ms [function] fragment-complexity=3Dlow:fragment-steps=3D5: FPS: 9360 FrameTim= e: 0.107 ms [function] fragment-complexity=3Dmedium:fragment-steps=3D5: FPS: 9214 Frame= Time: 0.109 ms [loop] fragment-loop=3Dfalse:fragment-steps=3D5:vertex-steps=3D5: FPS: 8945 FrameTime: 0.112 ms [loop] fragment-steps=3D5:fragment-uniform=3Dfalse:vertex-steps=3D5: FPS: 9= 218 FrameTime: 0.108 ms [loop] fragment-steps=3D5:fragment-uniform=3Dtrue:vertex-steps=3D5: FPS: 90= 77 FrameTime: 0.110 ms =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D glmark2 Score: 7197=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D --=20 You are receiving this mail because: You are the assignee for the bug.= --15696541689.fBCc.367 Date: Sat, 28 Sep 2019 07:02:48 +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 # 108 on bug 10995= 5 from = Wilko Bartels 
Did u try the amdgpu-pro driver as well?
i just did four runs of glmark and it just went through for me. going up to
1600mhz shader clock. tested both closed and opensource drivers. vega pulse
here.

mesa result:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
    glmark2 2014.03
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
    OpenGL Information
    GL_VENDOR:     X.Org
    GL_RENDERER:   Radeon RX Vega (VEGA10, DRM 3.33.0, 5.3.1-arch1-1-ARCH, =
LLVM
8.0.1)
    GL_VERSION:    4.5 (Compatibility Profile) Mesa 19.1.7
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
[build] use-vbo=3Dfalse: FPS: 8617 FrameTime: 0.116 ms
[build] use-vbo=3Dtrue: FPS: 10534 FrameTime: 0.095 ms
[texture] texture-filter=3Dnearest: FPS: 11214 FrameTime: 0.089 ms
[texture] texture-filter=3Dlinear: FPS: 11274 FrameTime: 0.089 ms
[texture] texture-filter=3Dmipmap: FPS: 10197 FrameTime: 0.098 ms
[shading] shading=3Dgouraud: FPS: 9790 FrameTime: 0.102 ms
[shading] shading=3Dblinn-phong-inf: FPS: 10979 FrameTime: 0.091 ms
[shading] shading=3Dphong: FPS: 10167 FrameTime: 0.098 ms
[shading] shading=3Dcel: FPS: 9662 FrameTime: 0.103 ms
[bump] bump-render=3Dhigh-poly: FPS: 9830 FrameTime: 0.102 ms
[bump] bump-render=3Dnormals: FPS: 10151 FrameTime: 0.099 ms
[bump] bump-render=3Dheight: FPS: 10870 FrameTime: 0.092 ms
libpng warning: iCCP: known incorrect sRGB profile
[effect2d] kernel=3D0,1,0;1,-4,1;0,1,0;: FPS: 12008 FrameTime: 0.083 ms
libpng warning: iCCP: known incorrect sRGB profile
[effect2d] kernel=3D1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 10876 FrameTime: 0=
.092
ms
[pulsar] light=3Dfalse:quads=3D5:texture=3Dfalse: FPS: 10232 FrameTime: 0.0=
98 ms
libpng warning: iCCP: known incorrect sRGB profile
[desktop] blur-radius=3D5:effect=3Dblur:passes=3D1:separable=3Dtrue:windows=
=3D4: FPS:
6842 FrameTime: 0.146 ms
libpng warning: iCCP: known incorrect sRGB profile
[desktop] effect=3Dshadow:windows=3D4: FPS: 7934 FrameTime: 0.126 ms
[buffer]
columns=3D200:interleave=3Dfalse:update-dispersion=3D0.9:update-fraction=3D=
0.5:update-method=3Dmap:
FPS: 1770 FrameTime: 0.565 ms
[buffer]
columns=3D200:interleave=3Dfalse:update-dispersion=3D0.9:update-fraction=3D=
0.5:update-method=3Dsubdata:
FPS: 2308 FrameTime: 0.433 ms
[buffer]
columns=3D200:interleave=3Dtrue:update-dispersion=3D0.9:update-fraction=3D0=
.5:update-method=3Dmap:
FPS: 1875 FrameTime: 0.533 ms
[ideas] speed=3Dduration: FPS: 4475 FrameTime: 0.223 ms
[jellyfish] <default>: FPS: 9499 FrameTime: 0.105 ms
[terrain] <default>: FPS: 2593 FrameTime: 0.386 ms
[shadow] <default>: FPS: 9423 FrameTime: 0.106 ms
[refract] <default>: FPS: 6008 FrameTime: 0.166 ms
[conditionals] fragment-steps=3D0:vertex-steps=3D0: FPS: 11364 FrameTime: 0=
.088 ms
[conditionals] fragment-steps=3D5:vertex-steps=3D0: FPS: 10816 FrameTime: 0=
.092 ms
[conditionals] fragment-steps=3D0:vertex-steps=3D5: FPS: 12000 FrameTime: 0=
.083 ms
[function] fragment-complexity=3Dlow:fragment-steps=3D5: FPS: 10932 FrameTi=
me:
0.091 ms
[function] fragment-complexity=3Dmedium:fragment-steps=3D5: FPS: 11690 Fram=
eTime:
0.086 ms
[loop] fragment-loop=3Dfalse:fragment-steps=3D5:vertex-steps=3D5: FPS: 11119
FrameTime: 0.090 ms
[loop] fragment-steps=3D5:fragment-uniform=3Dfalse:vertex-steps=3D5: FPS: 1=
1003
FrameTime: 0.091 ms
[loop] fragment-steps=3D5:fragment-uniform=3Dtrue:vertex-steps=3D5: FPS: 12=
886
FrameTime: 0.078 ms
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
                                  glmark2 Score: 9119=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D

amdgpu-pro result:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
    glmark2 2014.03
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
    OpenGL Information
    GL_VENDOR:     ATI Technologies Inc.
    GL_RENDERER:   Radeon RX Vega
    GL_VERSION:    4.6.13572 Compatibility Profile Context
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
[build] use-vbo=3Dfalse: FPS: 3727 FrameTime: 0.268 ms
[build] use-vbo=3Dtrue: FPS: 9516 FrameTime: 0.105 ms
[texture] texture-filter=3Dnearest: FPS: 7346 FrameTime: 0.136 ms
[texture] texture-filter=3Dlinear: FPS: 9236 FrameTime: 0.108 ms
[texture] texture-filter=3Dmipmap: FPS: 9161 FrameTime: 0.109 ms
[shading] shading=3Dgouraud: FPS: 9184 FrameTime: 0.109 ms
[shading] shading=3Dblinn-phong-inf: FPS: 9363 FrameTime: 0.107 ms
[shading] shading=3Dphong: FPS: 9424 FrameTime: 0.106 ms
[shading] shading=3Dcel: FPS: 9060 FrameTime: 0.110 ms
[bump] bump-render=3Dhigh-poly: FPS: 9047 FrameTime: 0.111 ms
[bump] bump-render=3Dnormals: FPS: 8804 FrameTime: 0.114 ms
[bump] bump-render=3Dheight: FPS: 9156 FrameTime: 0.109 ms
libpng warning: iCCP: known incorrect sRGB profile
[effect2d] kernel=3D0,1,0;1,-4,1;0,1,0;: FPS: 9121 FrameTime: 0.110 ms
libpng warning: iCCP: known incorrect sRGB profile
[effect2d] kernel=3D1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 8866 FrameTime: 0.=
113 ms
[pulsar] light=3Dfalse:quads=3D5:texture=3Dfalse: FPS: 8286 FrameTime: 0.12=
1 ms
libpng warning: iCCP: known incorrect sRGB profile
[desktop] blur-radius=3D5:effect=3Dblur:passes=3D1:separable=3Dtrue:windows=
=3D4: FPS:
3789 FrameTime: 0.264 ms
libpng warning: iCCP: known incorrect sRGB profile
[desktop] effect=3Dshadow:windows=3D4: FPS: 4491 FrameTime: 0.223 ms
[buffer]
columns=3D200:interleave=3Dfalse:update-dispersion=3D0.9:update-fraction=3D=
0.5:update-method=3Dmap:
FPS: 1026 FrameTime: 0.975 ms
[buffer]
columns=3D200:interleave=3Dfalse:update-dispersion=3D0.9:update-fraction=3D=
0.5:update-method=3Dsubdata:
FPS: 2228 FrameTime: 0.449 ms
[buffer]
columns=3D200:interleave=3Dtrue:update-dispersion=3D0.9:update-fraction=3D0=
.5:update-method=3Dmap:
FPS: 1275 FrameTime: 0.784 ms
[ideas] speed=3Dduration: FPS: 4038 FrameTime: 0.248 ms
[jellyfish] <default>: FPS: 7342 FrameTime: 0.136 ms
[terrain] <default>: FPS: 790 FrameTime: 1.266 ms
[shadow] <default>: FPS: 6002 FrameTime: 0.167 ms
[refract] <default>: FPS: 4273 FrameTime: 0.234 ms
[conditionals] fragment-steps=3D0:vertex-steps=3D0: FPS: 9208 FrameTime: 0.=
109 ms
[conditionals] fragment-steps=3D5:vertex-steps=3D0: FPS: 8964 FrameTime: 0.=
112 ms
[conditionals] fragment-steps=3D0:vertex-steps=3D5: FPS: 8984 FrameTime: 0.=
111 ms
[function] fragment-complexity=3Dlow:fragment-steps=3D5: FPS: 9360 FrameTim=
e: 0.107
ms
[function] fragment-complexity=3Dmedium:fragment-steps=3D5: FPS: 9214 Frame=
Time:
0.109 ms
[loop] fragment-loop=3Dfalse:fragment-steps=3D5:vertex-steps=3D5: FPS: 8945
FrameTime: 0.112 ms
[loop] fragment-steps=3D5:fragment-uniform=3Dfalse:vertex-steps=3D5: FPS: 9=
218
FrameTime: 0.108 ms
[loop] fragment-steps=3D5:fragment-uniform=3Dtrue:vertex-steps=3D5: FPS: 90=
77
FrameTime: 0.110 ms
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
                                  glmark2 Score: 7197=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D

You are receiving this mail because:
  • You are the assignee for the bug.
= --15696541689.fBCc.367-- --===============1816098538== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1816098538==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 28 Sep 2019 11:05:09 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0721661142==" 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 BFFDD6E147 for ; Sat, 28 Sep 2019 11:05:09 +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 --===============0721661142== Content-Type: multipart/alternative; boundary="156966870912.A84D2.18955" Content-Transfer-Encoding: 7bit --156966870912.A84D2.18955 Date: Sat, 28 Sep 2019 11:05:09 +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=3D109955 --- Comment #109 from jeroenimo --- (In reply to Wilko Bartels from comment #108) > Did u try the amdgpu-pro driver as well? > i just did four runs of glmark and it just went through for me. going up = to > 1600mhz shader clock. tested both closed and opensource drivers. vega pul= se > here. >=20 Yes I did try all versions. I'm pretty sure it's not the driver, as all res= ults in the same. Any higher clockspeed just crashed. Ik have NVIDIA 1030 installed now, which is also buggy but at least it does= n't crash. --=20 You are receiving this mail because: You are the assignee for the bug.= --156966870912.A84D2.18955 Date: Sat, 28 Sep 2019 11:05:09 +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 # 109 on bug 10995= 5 from jeroenimo 
(In reply to Wilko Bartels from comment #108)
> Did u try the amdgpu-pro driver as well?
> i just did four runs of glmark and it just went through for me. going =
up to
> 1600mhz shader clock. tested both closed and opensource drivers. vega =
pulse
> here.
> 
Yes I did try all versions. I'm pretty sure it's not the driver, as all res=
ults
in the same. Any higher clockspeed just crashed.

Ik have NVIDIA 1030 installed now, which is also buggy but at least it does=
n't
crash.

You are receiving this mail because:
  • You are the assignee for the bug.
= --156966870912.A84D2.18955-- --===============0721661142== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0721661142==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 28 Sep 2019 12:25:32 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1849236026==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id EC04E6E141 for ; Sat, 28 Sep 2019 12:25:32 +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 --===============1849236026== Content-Type: multipart/alternative; boundary="156967353210.5BDD7F3Eb.4259" Content-Transfer-Encoding: 7bit --156967353210.5BDD7F3Eb.4259 Date: Sat, 28 Sep 2019 12:25:32 +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=3D109955 --- Comment #110 from Rodney A Morris --- (In reply to Rodney A Morris from comment #104) > (In reply to Mauro Gaspari from comment #103) > > (In reply to Rodney A Morris from comment #101) > > > (In reply to Rodney A Morris from comment #99) > > > > Created attachment 145366 [details] > > > > apitrace of Hearts of Iron IV hard lock > > > >=20 > > > > Apitrace from hard lock playing Hearts of Iron IV without Steam. T= he replay > > > > from this trace will hard lock the computer, though inconsistently.= I've > > > > replayed the trace three times. The replay hard locked computer one= time. > > >=20 > > > neofetch from hardlock: > > >=20 > > > /:-------------:\=20=20=20=20=20=20=20=20=20=20 > > > :-------------------:: --------------------------------= =20 > > > :-----------/shhOHbmp---:\ OS: Fedora release 30 (Thirty) x= 86_64=20 > > > /-----------omMMMNNNMMD ---: Kernel: 5.2.13-200.fc30.x86_64=20 > > > :-----------sMMMMNMNMP. ---: Uptime: 25 mins=20 > > > :-----------:MMMdP------- ---\ Packages: 2202 (rpm), 27 (flatpa= k)=20 > > > ,------------:MMMd-------- ---: Shell: bash 5.0.7=20 > > > :------------:MMMd------- .---: Resolution: 2560x1440=20 > > > :---- oNMMMMMMMMMNho .----: DE: GNOME 3.32.2=20 > > > :-- .+shhhMMMmhhy++ .------/ WM: GNOME Shell=20 > > > :- -------:MMMd--------------: WM Theme: Adwaita=20 > > > :- --------/MMMd-------------; Theme: Adapta-Nokto-Eta [GTK2/3]= =20 > > > :- ------/hMMMy------------: Icons: Adwaita [GTK2/3]=20 > > > :-- :dMNdhhdNMMNo------------; Terminal: tilix=20 > > > :---:sdNMMMMNds:------------: CPU: Intel i7-6850K (12) @ 4.000= GHz=20 > > > :------:://:-------------:: GPU: AMD ATI Radeon RX Vega 56/6= 4=20 > > > :---------------------:// Memory: 2478MiB / 32084MiB=20 > > >=20 > > > OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6 > > >=20 > > > Note: hard lock replayed occurred when the Discord flatpak is also r= unning. > >=20 > > I also noticed some errors that pointed to discord in my logs. In my ca= se > > discord was installed via .deb package.=20 > > Could you please try and disable hardware acceleration in discord setti= ngs - > > appearance menu? Please let me know if it helps or changes anything.=20 > > Thanks! >=20 > I have disabled hardware acceleration in discord settings to see if that > improves my experience and report back my results. I am doubtful that it > will help much. At least on the 5.2.11 kernel, I had lockups with or > without discord running. Discord running just seemed to make the problem > appear more consistently. Another lockup and crash last night of Stellaris with identical dmesg kernel information as comment 105. Kernel for this crash: 5.2.17. Unlike previous attempts, I also had cpupower configured to run the cpu in performance mode and was running feral gamemode. Although I still wonder i= f my hardware has an issue, I am able to run Stellaris without issue under Windo= ws. Final Note: Getting an apitrace of my crash under Stellaris is not feasible= for two reasons. First, the crash typically happens between 30 minutes and 40 minutes of game play, resulting in a monster trace file. Second, i cannot = get apitrace to run correctly with Steam and a 64-bit game, which is necessary since the crashes happen most frequently in multiplayer. I am happy to provide more data if someone can point me in the direction to capture it. Aside from trying the amdgpu-pro drivers, is there anything el= se I can try? --=20 You are receiving this mail because: You are the assignee for the bug.= --156967353210.5BDD7F3Eb.4259 Date: Sat, 28 Sep 2019 12:25:32 +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 # 110 on bug 10995= 5 from Rodney A Morris 
(In reply to Rodney A Morris from comment #104)
> (In reply to Mauro Gaspari from comment #103)
> > (In reply to Rodney A Morris from comment #101)
> > > (In reply to Rodney A Morris from comment #99)
> > > > Created attachment 145366 [details]
> > > > apitrace of Hearts of Iron IV hard lock
> > > >=20
> > > > Apitrace from hard lock playing Hearts of Iron IV witho=
ut Steam.  The replay
> > > > from this trace will hard lock the computer, though inc=
onsistently.  I've
> > > > replayed the trace three times. The replay hard locked =
computer one time.
> > >=20
> > > neofetch from hardlock:
> > >=20
> > >           /:-------------:\=20=20=20=20=20=20=20=20=20=20
> > >        :-------------------::        -----------------------=
---------=20
> > >      :-----------/shhOHbmp---:\      OS: Fedora release 30 (=
Thirty) x86_64=20
> > >    /-----------omMMMNNNMMD  ---:     Kernel: 5.2.13-200.fc30=
.x86_64=20
> > >   :-----------sMMMMNMNMP.    ---:    Uptime: 25 mins=20
> > >  :-----------:MMMdP-------    ---\   Packages: 2202 (rpm), 2=
7 (flatpak)=20
> > > ,------------:MMMd--------    ---:   Shell: bash 5.0.7=20
> > > :------------:MMMd-------    .---:   Resolution: 2560x1440=20
> > > :----    oNMMMMMMMMMNho     .----:   DE: GNOME 3.32.2=20
> > > :--     .+shhhMMMmhhy++   .------/   WM: GNOME Shell=20
> > > :-    -------:MMMd--------------:    WM Theme: Adwaita=20
> > > :-   --------/MMMd-------------;     Theme: Adapta-Nokto-Eta=
 [GTK2/3]=20
> > > :-    ------/hMMMy------------:      Icons: Adwaita [GTK2/3]=
=20
> > > :-- :dMNdhhdNMMNo------------;       Terminal: tilix=20
> > > :---:sdNMMMMNds:------------:        CPU: Intel i7-6850K (12=
) @ 4.000GHz=20
> > > :------:://:-------------::          GPU: AMD ATI Radeon RX =
Vega 56/64=20
> > > :---------------------://            Memory: 2478MiB / 32084=
MiB=20
> > >=20
> > > OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1=
.6
> > >=20
> > > Note:  hard lock replayed occurred when the Discord flatpak =
is also running.
> >=20
> > I also noticed some errors that pointed to discord in my logs. In=
 my case
> > discord was installed via .deb package.=20
> > Could you please try and disable hardware acceleration in discord=
 settings -
> > appearance menu? Please let me know if it helps or changes anythi=
ng.=20
> > Thanks!
>=20
> I have disabled hardware acceleration in discord settings to see if th=
at
> improves my experience and report back my results.  I am doubtful that=
 it
> will help much.  At least on the 5.2.11 kernel, I had lockups with or
> without discord running.  Discord running just seemed to make the prob=
lem
> appear more consistently.

Another lockup and crash last night of Stellaris with identical dmesg kernel
information as comment 105.

Kernel for this crash: 5.2.17.

  Unlike previous attempts, I also had cpupower configured to run the cpu in
performance mode and was running feral gamemode.  Although I still wonder i=
f my
hardware has an issue, I am able to run Stellaris without issue under Windo=
ws.

Final Note: Getting an apitrace of my crash under Stellaris is not feasible=
 for
two reasons.  First, the crash typically happens between 30 minutes and 40
minutes of game play, resulting in a monster trace file.  Second, i cannot =
get
apitrace to run correctly with Steam and a 64-bit game, which is necessary
since the crashes happen most frequently in multiplayer.

I am happy to provide more data if someone can point me in the direction to
capture it.  Aside from trying the amdgpu-pro drivers, is there anything el=
se I
can try?

You are receiving this mail because:
  • You are the assignee for the bug.
= --156967353210.5BDD7F3Eb.4259-- --===============1849236026== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1849236026==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 03 Oct 2019 09:57:41 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1070251733==" 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 9B5086E0EA for ; Thu, 3 Oct 2019 09:57:41 +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 --===============1070251733== Content-Type: multipart/alternative; boundary="15700966613.a4fb8.22936" Content-Transfer-Encoding: 7bit --15700966613.a4fb8.22936 Date: Thu, 3 Oct 2019 09:57:41 +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=3D109955 --- Comment #111 from Yury Zhuravlev --- Ok, it's many times was here: echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk this thing also helped me. Without it, many games make my PC is freeze even without anything in logs or working ssh.=20 Something wrong with the PowerPlay system on Vega cards. Can anybody open a ticket on the kernel bug tracker? --=20 You are receiving this mail because: You are the assignee for the bug.= --15700966613.a4fb8.22936 Date: Thu, 3 Oct 2019 09:57:41 +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 # 111 on bug 10995= 5 from Yury Zhuravlev 
Ok, it's many times was here:
echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk

this thing also helped me. Without it, many games make my PC is freeze even
without anything in logs or working ssh.=20

Something wrong with the PowerPlay system on Vega cards. Can anybody open a
ticket on the kernel bug tracker?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15700966613.a4fb8.22936-- --===============1070251733== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1070251733==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 05 Oct 2019 10:12:00 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1917862586==" 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 1B8B36E219 for ; Sat, 5 Oct 2019 10:12:07 +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 --===============1917862586== Content-Type: multipart/alternative; boundary="15702703261.FcDcDC0e9.24286" Content-Transfer-Encoding: 7bit --15702703261.FcDcDC0e9.24286 Date: Sat, 5 Oct 2019 10:12:06 +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=3D109955 --- Comment #112 from Jan Orsag --- screenfetch =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88= =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2= =96=88=E2=96=88 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2= =96=88=E2=96=88 johanides@johanides-manjaro =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88= =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2= =96=88=E2=96=88 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2= =96=88=E2=96=88 OS: Manjaro 18.1.0 Juhraya =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88= =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2= =96=88=E2=96=88 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2= =96=88=E2=96=88 Kernel: x86_64 Linux 4.19.69-1-MANJARO =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88= =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2= =96=88=E2=96=88 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2= =96=88=E2=96=88 Uptime: 18m =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88= =E2=96=88 Packages: 1186 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = Shell: bash =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = Resolution: 2560x1440 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = DE: GNOME 3.32.2 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = WM: Mutter =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = WM Theme: Adapta-Nokto-Eta-Maia =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = GTK Theme: Adapta-Nokto-Eta-Maia [GTK2/3] =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = Icon Theme: Papirus-Adapta-Nokto-Maia =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = Font: Noto Sans 10 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 = Disk: 565G / 1,2T (50%) CPU: AMD Ryzen 5 1600X Six-Core @ 12x 3.6= GHz GPU: Radeon RX Vega (VEGA10, DRM 3.27.0, 4.19.69-1-MANJARO, LLVM 8.0.1) RAM: 2320MiB / 16050MiB System hard freezes after some playtime in Civilization 6 (black/green/gray screen, music playing, need to use reset button) Errors in system logs: sep 19 16:39:13 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D7763335, emitted seq=3D7763337 sep 19 16:39:13 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdm= a1 timeout, signaled seq=3D7703731, emitted seq=3D7703733 sep 19 16:41:11 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdm= a0 timeout, signaled seq=3D374796, emitted seq=3D374798 On my computer however, the crash/freeze occurs sooner with kernels 5.x and higher than with kernel 4.19. Its approximately 1 hour playtime (kernel 5+)= vs. 8 hours (kernel 4.19). It doesnt matter what mesa I use- tried mesa-aco-git 19.3 and mesa 19.1. --=20 You are receiving this mail because: You are the assignee for the bug.= --15702703261.FcDcDC0e9.24286 Date: Sat, 5 Oct 2019 10:12:06 +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 # 112 on bug 10995= 5 from Jan Orsag 
screenfetch
 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=
=96=88=E2=96=88  =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=
=96=88=E2=96=88     johanides@johanides-manjaro
 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=
=96=88=E2=96=88  =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=
=96=88=E2=96=88     OS: Manjaro 18.1.0 Juhraya
 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=
=96=88=E2=96=88  =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=
=96=88=E2=96=88     Kernel: x86_64 Linux 4.19.69-1-MANJARO
 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=
=96=88=E2=96=88  =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=
=96=88=E2=96=88     Uptime: 18m
 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
          =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=
=E2=96=88     Packages: 1186
 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88   =
  Shell: bash
 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88   =
  Resolution: 2560x1440
 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88   =
  DE: GNOME 3.32.2
 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88   =
  WM: Mutter
 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88   =
  WM Theme: Adapta-Nokto-Eta-Maia
 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88   =
  GTK Theme: Adapta-Nokto-Eta-Maia [GTK2/3]
 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88   =
  Icon Theme: Papirus-Adapta-Nokto-Maia
 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88   =
  Font: Noto Sans 10
 =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88  =
=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88   =
  Disk: 565G / 1,2T (50%)
                                  CPU: AMD Ryzen 5 1600X Six-Core @ 12x=
 3.6GHz
                                  GPU: Radeon RX Vega (VEGA10, DRM 3.27.0,
4.19.69-1-MANJARO, LLVM 8.0.1)
                                  RAM: 2320MiB / 16050MiB

System hard freezes after some playtime in Civilization 6 (black/green/gray
screen, music playing, need to use reset button)

Errors in system logs:
sep 19 16:39:13 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, signaled seq=3D7763335, emitted seq=3D7763337
sep 19 16:39:13 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdm=
a1
timeout, signaled seq=3D7703731, emitted seq=3D7703733
sep 19 16:41:11 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdm=
a0
timeout, signaled seq=3D374796, emitted seq=3D374798

On my computer however, the crash/freeze occurs sooner with kernels 5.x and
higher than with kernel 4.19. Its approximately 1 hour playtime (kernel 5+)=
 vs.
8 hours (kernel 4.19). It doesnt matter what mesa I use- tried mesa-aco-git
19.3 and mesa 19.1.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15702703261.FcDcDC0e9.24286-- --===============1917862586== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1917862586==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 05 Oct 2019 12:02:13 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1683479049==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id C8D1D6E239 for ; Sat, 5 Oct 2019 12:02:12 +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 --===============1683479049== Content-Type: multipart/alternative; boundary="15702769320.2AF887F1.11540" Content-Transfer-Encoding: 7bit --15702769320.2AF887F1.11540 Date: Sat, 5 Oct 2019 12:02:12 +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=3D109955 --- Comment #113 from Jason Playne --- As others have noted, with powerplay doing its thing we get system freezes. Just had a successful 6+ hour gaming session on a kernel 5.3.2-050302-gener= ic with the following being done: * Forcing high perf state * Undervolt/Overclock * Higher fan curve (https://github.com/grmat/amdgpu-fancontrol) I know that I have been messing with all sorts here, but I think it suggests that PowerPlay may be at fault here when my system *does* crash (which is a= ll the time without the force high perf state) All details below: # Forcing High Perf echo high | sudo tee /sys/class/drm/card0/device/power_dpm_force_performance_level # Undervolt / Overclock I also have done some messing around with voltages/clocks $ cat /sys/class/drm/card0/device/pp_od_clk_voltage OD_SCLK: 0: 852Mhz 800mV 1: 991Mhz 900mV 2: 1084Mhz 940mV 3: 1138Mhz 990mV 4: 1200Mhz 1040mV 5: 1401Mhz 1090mV 6: 1536Mhz 1140mV 7: 1630Mhz 1190mV OD_MCLK: 0: 167Mhz 800mV 1: 500Mhz 800mV 2: 850Mhz 940mV 3: 1000Mhz 1100mV OD_RANGE: SCLK: 852MHz 2400MHz MCLK: 167MHz 1500MHz VDDC: 800mV 1200mV # Settings for AMDGPU Fancontrol TEMPS=3D( 35000 70000 80000 ) PWMS=3D( 70 180 255 ) --=20 You are receiving this mail because: You are the assignee for the bug.= --15702769320.2AF887F1.11540 Date: Sat, 5 Oct 2019 12:02:12 +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 # 113 on bug 10995= 5 from Jason Playne 
As others have noted, with powerplay doing its thing we get sy=
stem freezes.

Just had a successful 6+ hour gaming session on a kernel 5.3.2-050302-gener=
ic
with the following being done:
 * Forcing high perf state
 * Undervolt/Overclock
 * Higher fan curve (https://github.com/grmat/amdgpu-fancontrol)

I know that I have been messing with all sorts here, but I think it suggests
that PowerPlay may be at fault here when my system *does* crash (which is a=
ll
the time without the force high perf state)

All details below:

# Forcing High Perf
echo high | sudo tee
/sys/class/drm/card0/device/power_dpm_force_performance_level

# Undervolt / Overclock
I also have done some messing around with voltages/clocks

$ cat /sys/class/drm/card0/device/pp_od_clk_voltage
OD_SCLK:
0:        852Mhz        800mV
1:        991Mhz        900mV
2:       1084Mhz        940mV
3:       1138Mhz        990mV
4:       1200Mhz       1040mV
5:       1401Mhz       1090mV
6:       1536Mhz       1140mV
7:       1630Mhz       1190mV
OD_MCLK:
0:        167Mhz        800mV
1:        500Mhz        800mV
2:        850Mhz        940mV
3:       1000Mhz       1100mV
OD_RANGE:
SCLK:     852MHz       2400MHz
MCLK:     167MHz       1500MHz
VDDC:     800mV        1200mV


# Settings for AMDGPU Fancontrol
TEMPS=3D( 35000 70000 80000 )
PWMS=3D(     70   180   255 )

You are receiving this mail because:
  • You are the assignee for the bug.
= --15702769320.2AF887F1.11540-- --===============1683479049== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1683479049==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 19 Oct 2019 21:26:58 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0045920798==" 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 A1AD789D1D for ; Sat, 19 Oct 2019 21:26:59 +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 --===============0045920798== Content-Type: multipart/alternative; boundary="15715204195.Fba0e4b.6266" Content-Transfer-Encoding: 7bit --15715204195.Fba0e4b.6266 Date: Sat, 19 Oct 2019 21:26:59 +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=3D109955 --- Comment #114 from Rodney A Morris --- To rule out possible hardware issues, I purchased another Vega 64 card. Th= is time a factory overclocked card. Since installing the card, I have experie= nced three lock ups. Two playing Stellaris and one while playing a youtube vide= o.=20 After playing Stellaris without issue two weeks ago, the computer locked up twice last night. While my previous problems seemed to be, in part, linked= to a circular lock dependence, the last logs indicate something different. I'm seeing a lot of powerplay errors after the fence timeout. Hope this new information provides some insight into the problem. /:-------------:\ rmorris@ezra.blanchardmorris.net=20 :-------------------:: --------------------------------=20 :-----------/shhOHbmp---:\ OS: Fedora release 30 (Thirty) x86_64= =20 /-----------omMMMNNNMMD ---: Kernel: 5.3.6-200.fc30.x86_64=20 :-----------sMMMMNMNMP. ---: Uptime: 16 hours, 21 mins=20 :-----------:MMMdP------- ---\ Packages: 2214 (rpm), 36 (flatpak)=20 ,------------:MMMd-------- ---: Shell: bash 5.0.7=20 :------------:MMMd------- .---: Resolution: 2560x1440=20 :---- oNMMMMMMMMMNho .----: DE: GNOME 3.32.2=20 :-- .+shhhMMMmhhy++ .------/ WM: Mutter=20 :- -------:MMMd--------------: WM Theme: Adwaita=20 :- --------/MMMd-------------; Theme: Adapta-Nokto-Eta [GTK2/3]=20 :- ------/hMMMy------------: Icons: Adwaita [GTK2/3]=20 :-- :dMNdhhdNMMNo------------; Terminal: tilix=20 :---:sdNMMMMNds:------------: CPU: Intel i7-6850K (12) @ 4.000GHz=20 :------:://:-------------:: GPU: AMD ATI Radeon RX Vega 56/64=20 :---------------------:// Memory: 2814MiB / 32036MiB=20 Card: MSI Vega 64 OC (Card works fine under windows 10) Game being played: Stellaris Native Game Description of Event: Screen goes blank and music and sound continues to play before computer loc= ks up or reboots. relevant dmesg from crash: [ 4244.670269] perf: interrupt took too long (2502 > 2500), lowering kernel.perf_event_max_sample_rate to 79000 [ 4298.241156] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting = for fences timed out or interrupted! [ 4304.385587] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring page1 timeou= t, signaled seq=3D60549844, emitted seq=3D60549846 [ 4304.385634] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati= on: process pid 0 thread pid 0 [ 4304.385637] amdgpu 0000:06:00.0: GPU reset begin! [ 4304.402938] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 4304.402945] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 4304.402947] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 4304.402948] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 4304.404006] pcieport 0000:00:03.0: AER: Device recovery failed [ 4308.481068] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out [ 4314.625180] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-= 0] hw_done or flip_done timed out [ 4324.865057] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper= ]] *ERROR* [CRTC:47:crtc-0] flip_done timed out [ 4335.105035] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper= ]] *ERROR* [PLANE:45:plane-5] flip_done timed out [ 4336.695112] amdgpu: [powerplay] No response from smu [ 4336.695128] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x= 0, error code: 0x0 [ 4338.307125] amdgpu: [powerplay] No response from smu [ 4339.922039] amdgpu: [powerplay] No response from smu [ 4339.922043] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0= x1, error code: 0x0 [ 4341.541675] amdgpu: [powerplay] No response from smu [ 4343.162102] amdgpu: [powerplay] No response from smu [ 4343.162105] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0= x0, error code: 0x0 [ 4343.221953] [drm] REG_WAIT timeout 10us * 3500 tries - dce_mi_free_dmif line:634 [ 4343.221962] ------------[ cut here ]------------ [ 4343.222070] WARNING: CPU: 0 PID: 16500 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:332 generic_reg_wait.cold+0x31/0x53 [amdgpu] [ 4343.222072] Modules linked in: rfcomm xt_CHECKSUM xt_MASQUERADE tun brid= ge stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_n= at ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables cmac bnep nct6= 775 hwmon_vid intel_rapl_msr intel_rapl_common vfat fat fuse x86_pkg_temp_therm= al intel_powerclamp coretemp iwlmvm kvm_intel iTCO_wdt iTCO_vendor_support mac80211 kvm snd_hda_codec_realtek irqbypass snd_hda_codec_generic snd_hda_codec_hdmi libarc4 ledtrig_audio crct10dif_pclmul snd_hda_intel crc32_pclmul iwlwifi snd_hda_codec snd_hda_core btusb ghash_clmulni_intel b= trtl intel_cstate snd_hwdep btbcm btintel intel_uncore snd_seq snd_seq_device intel_rapl_perf bluetooth [ 4343.222099] mxm_wmi cfg80211 snd_pcm joydev ecdh_generic ecc mei_me snd_timer rfkill snd mei i2c_i801 soundcore lpc_ich binfmt_misc auth_rpcgss sunrpc amdgpu amd_iommu_v2 gpu_sched ttm drm_kms_helper crc32c_intel uas mpt3sas igb drm e1000e nvme usb_storage dca i2c_algo_bit raid_class nvme_co= re scsi_transport_sas wmi [ 4343.222114] CPU: 0 PID: 16500 Comm: kworker/0:1 Not tainted 5.3.6-200.fc30.x86_64+debug #1 [ 4343.222115] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M.= /X99 Taichi, BIOS P1.80 04/06/2018 [ 4343.222119] Workqueue: events drm_sched_job_timedout [gpu_sched] [ 4343.222167] RIP: 0010:generic_reg_wait.cold+0x31/0x53 [amdgpu] [ 4343.222169] Code: 4c 24 18 44 89 fa 89 ee 48 c7 c7 f8 9d 73 c0 e8 60 46 = b0 fa 83 7b 20 01 0f 84 02 ee fd ff 48 c7 c7 f0 9c 73 c0 e8 4a 46 b0 fa <0f> 0= b e9 ef ed fd ff 48 c7 c7 f0 9c 73 c0 89 54 24 04 e8 33 46 b0 [ 4343.222170] RSP: 0018:ffffabda8729b690 EFLAGS: 00010246 [ 4343.222172] RAX: 0000000000000024 RBX: ffff9ceeab58f700 RCX: 0000000000000006 [ 4343.222173] RDX: 0000000000000000 RSI: ffff9ceeb50c8e50 RDI: ffff9ceebe5d9e00 [ 4343.222174] RBP: 000000000000000a R08: 000003f33c33ca38 R09: 0000000000000000 [ 4343.222175] R10: 0000000000000000 R11: 0000000000000000 R12: 00000000000035af [ 4343.222176] R13: 0000000000000dad R14: 0000000000000001 R15: 0000000000000dac [ 4343.222178] FS: 0000000000000000(0000) GS:ffff9ceebe400000(0000) knlGS:0000000000000000 [ 4343.222179] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 4343.222180] CR2: 00007f1480ef70c0 CR3: 0000000703f30002 CR4: 00000000003606f0 [ 4343.222182] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 4343.222183] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 4343.222184] Call Trace: [ 4343.222237] dce_mi_free_dmif+0xef/0x150 [amdgpu] [ 4343.222285] dce110_reset_hw_ctx_wrap+0x15f/0x200 [amdgpu] [ 4343.222333] dce110_apply_ctx_to_hw+0x4b/0x530 [amdgpu] [ 4343.222365] ? amdgpu_pm_compute_clocks+0xc9/0x5f0 [amdgpu] [ 4343.222414] ? dm_pp_apply_display_requirements+0x1a8/0x1c0 [amdgpu] [ 4343.222461] dc_commit_state+0x26b/0x590 [amdgpu] [ 4343.222514] amdgpu_dm_atomic_commit_tail+0xd18/0x1cf0 [amdgpu] [ 4343.222521] ? __lock_acquire+0x247/0x1910 [ 4343.222525] ? find_held_lock+0x32/0x90 [ 4343.222529] ? find_held_lock+0x32/0x90 [ 4343.222533] ? sched_clock+0x5/0x10 [ 4343.222536] ? mark_held_locks+0x50/0x80 [ 4343.222540] ? __lock_acquire+0x247/0x1910 [ 4343.222545] ? wake_up_klogd+0x37/0x40 [ 4343.222549] ? find_held_lock+0x32/0x90 [ 4343.222552] ? mark_held_locks+0x50/0x80 [ 4343.222556] ? _raw_spin_unlock_irq+0x29/0x40 [ 4343.222559] ? lockdep_hardirqs_on+0xf0/0x180 [ 4343.222561] ? _raw_spin_unlock_irq+0x29/0x40 [ 4343.222564] ? wait_for_completion_timeout+0x75/0x190 [ 4343.222576] ? commit_tail+0x3c/0x70 [drm_kms_helper] [ 4343.222622] ? amdgpu_dm_audio_eld_notify+0x60/0x60 [amdgpu] [ 4343.222628] commit_tail+0x3c/0x70 [drm_kms_helper] [ 4343.222634] drm_atomic_helper_commit+0xe3/0x150 [drm_kms_helper] [ 4343.222640] drm_atomic_helper_disable_all+0x14c/0x160 [drm_kms_helper] [ 4343.222647] drm_atomic_helper_suspend+0x66/0x100 [drm_kms_helper] [ 4343.222698] dm_suspend+0x20/0x60 [amdgpu] [ 4343.222726] amdgpu_device_ip_suspend_phase1+0x91/0xc0 [amdgpu] [ 4343.222755] amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu] [ 4343.222801] amdgpu_device_pre_asic_reset+0x191/0x1a4 [amdgpu] [ 4343.222849] amdgpu_device_gpu_recover+0x260/0x934 [amdgpu] [ 4343.222893] amdgpu_job_timedout+0x115/0x140 [amdgpu] [ 4343.222899] drm_sched_job_timedout+0x44/0xa0 [gpu_sched] [ 4343.222903] process_one_work+0x272/0x5a0 [ 4343.222908] worker_thread+0x50/0x3b0 [ 4343.222915] kthread+0x108/0x140 [ 4343.222916] ? process_one_work+0x5a0/0x5a0 [ 4343.222918] ? kthread_park+0x80/0x80 [ 4343.222921] ret_from_fork+0x3a/0x50 [ 4343.222929] irq event stamp: 82808 [ 4343.222931] hardirqs last enabled at (82807): [] console_unlock+0x46b/0x5d0 [ 4343.222935] hardirqs last disabled at (82808): [] trace_hardirqs_off_thunk+0x1a/0x20 [ 4343.222938] softirqs last enabled at (82794): [] __do_softirq+0x35d/0x45d [ 4343.222942] softirqs last disabled at (82787): [] irq_exit+0xf7/0x100 [ 4343.222943] ---[ end trace 71731c9cc205c24d ]--- [ 4344.758203] amdgpu: [powerplay] No response from smu [ 4346.363061] amdgpu: [powerplay] No response from smu [ 4346.363065] amdgpu: [powerplay] Failed to send message: 0x26, ret value:= 0x0 [ 4347.973948] amdgpu: [powerplay] No response from smu [ 4349.588168] amdgpu: [powerplay] No response from smu [ 4349.588173] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0= x1, error code: 0x0 [ 4351.152764] amdgpu: [powerplay] No response from smu [ 4352.722063] amdgpu: [powerplay] No response from smu [ 4352.722068] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0= x3, error code: 0x0 [ 4354.325541] amdgpu: [powerplay] No response from smu [ 4355.924138] amdgpu: [powerplay] No response from smu [ 4355.924141] amdgpu: [powerplay] Failed to send message: 0x63, ret value:= 0x0 [ 4357.537736] amdgpu: [powerplay] No response from smu [ 4359.154141] amdgpu: [powerplay] No response from smu [ 4359.154146] amdgpu: [powerplay] Failed message: 0x9, input parameter: 0x= f4, error code: 0x0 [ 4360.760856] amdgpu: [powerplay] No response from smu [ 4362.372410] amdgpu: [powerplay] No response from smu [ 4362.372414] amdgpu: [powerplay] Failed message: 0xa, input parameter: 0xa0b000, error code: 0x0 [ 4363.985961] amdgpu: [powerplay] No response from smu [ 4365.599325] amdgpu: [powerplay] No response from smu [ 4365.599331] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x= 0, error code: 0x0 [ 4367.214945] amdgpu: [powerplay] No response from smu [ 4368.829650] amdgpu: [powerplay] No response from smu [ 4368.829655] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0= x1, error code: 0x0 [ 4370.443783] amdgpu: [powerplay] No response from smu [ 4372.057288] amdgpu: [powerplay] No response from smu [ 4372.057293] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0= x0, error code: 0x0 [ 4372.074301] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 4372.074308] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 4372.074310] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 4372.074312] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 4372.074569] pcieport 0000:00:03.0: AER: Device recovery failed [ 4372.091832] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 4372.091837] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 4372.091839] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 4372.091840] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 4372.091889] pcieport 0000:00:03.0: AER: Device recovery failed [ 4372.109371] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 4372.109376] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 4372.109378] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 4372.109380] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 4372.126998] pcieport 0000:00:03.0: AER: Device recovery failed [ 4372.127002] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 4372.127009] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 4372.127021] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 4372.127024] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 4372.127083] pcieport 0000:00:03.0: AER: Device recovery failed [ 4372.144452] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 4372.144457] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 4372.144458] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 4372.144460] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 4372.144514] pcieport 0000:00:03.0: AER: Device recovery failed [ 4372.161992] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 4372.161997] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 4372.161999] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 4372.162001] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 4372.162086] pcieport 0000:00:03.0: AER: Device recovery failed [ 4372.179534] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 4372.179538] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 4372.179540] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 4372.179542] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 4372.179674] pcieport 0000:00:03.0: AER: Device recovery failed [ 4372.197074] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 4372.197079] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [ 4372.197081] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [ 4372.197082] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [ 4372.197131] pcieport 0000:00:03.0: AER: Device recovery failed [ 4372.214616] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal) error received: 0000:00:03.0 [ 4372.267239] amdgpu: [powerplay] Failed to send message: 0x61, ret value: 0xffffffff Relevant journalctl messages: Oct 18 21:49:47 ezra.blanchardmorris.net kernel: perf: interrupt took too l= ong (2502 > 2500), lowering kernel.perf_event_max_sample_rate to 79000 Oct 18 21:50:47 ezra.blanchardmorris.net kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out or interrupted! Oct 18 21:50:47 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring page1 timeout, signaled seq=3D60549844, emitted seq=3D60549846 Oct 18 21:50:47 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 Oct 18 21:50:47 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: GPU r= eset begin! Oct 18 21:50:47 ezra.blanchardmorris.net kernel: pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 Oct 18 21:50:47 ezra.blanchardmorris.net kernel: pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncorrected (Non-Fatal), type=3DTransaction Laye= r, (Requester ID) Oct 18 21:50:47 ezra.blanchardmorris.net kernel: pcieport 0000:00:03.0: AER= :=20=20 device [8086:6f08] error status/mask=3D00004000/00000000 Oct 18 21:50:47 ezra.blanchardmorris.net kernel: pcieport 0000:00:03.0: AER= :=20=20=20 [14] CmpltTO (First) Oct 18 21:50:47 ezra.blanchardmorris.net kernel: pcieport 0000:00:03.0: AER: Device recovery failed Oct 18 21:50:51 ezra.blanchardmorris.net kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out Oct 18 21:50:57 ezra.blanchardmorris.net kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-0] hw_done or flip_done timed out Oct 18 21:51:07 ezra.blanchardmorris.net kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out Oct 18 21:51:18 ezra.blanchardmorris.net kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:45:plane-5] flip_done timed out Oct 18 21:51:19 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:19 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x0, error code: 0x0 Oct 18 21:51:21 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:22 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:22 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed message: 0x42, input parameter: 0x1, error code: 0x0 Oct 18 21:51:24 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:26 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:26 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed message: 0x24, input parameter: 0x0, error code: 0x0 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: [drm] REG_WAIT timeout 10u= s * 3500 tries - dce_mi_free_dmif line:634 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ------------[ cut here ]------------ Oct 18 21:51:26 ezra.blanchardmorris.net kernel: WARNING: CPU: 0 PID: 16500= at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:332 generic_reg_wait.cold+0x31/0x53 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel: Modules linked in: rfcomm xt_CHECKSUM xt_MASQUERADE tun bridge stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_= nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables cmac bnep nct6775 hwmon= _vid intel_rapl_msr intel_rapl_common vfat fat fuse x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel iTCO_wdt iTCO_vendor_support mac80211 kvm snd_hda_codec_realtek irqbypass snd_hda_codec_generic snd_hda_codec_hdmi libarc4 ledtrig_audio crct10dif_pclmul snd_hda_intel crc32_pclmul iwlwifi snd_hda_codec snd_hda_core btusb ghash_clmulni_intel b= trtl intel_cstate snd_hwdep btbcm btintel intel_uncore snd_seq snd_seq_device intel_rapl_perf bluetooth Oct 18 21:51:26 ezra.blanchardmorris.net kernel: mxm_wmi cfg80211 snd_pcm joydev ecdh_generic ecc mei_me snd_timer rfkill snd mei i2c_i801 soundcore lpc_ich binfmt_misc auth_rpcgss sunrpc amdgpu amd_iommu_v2 gpu_sched ttm drm_kms_helper crc32c_intel uas mpt3sas igb drm e1000e nvme usb_storage dca i2c_algo_bit raid_class nvme_core scsi_transport_sas wmi Oct 18 21:51:26 ezra.blanchardmorris.net kernel: CPU: 0 PID: 16500 Comm: kworker/0:1 Not tainted 5.3.6-200.fc30.x86_64+debug #1 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: Hardware name: To Be Fille= d By O.E.M. To Be Filled By O.E.M./X99 Taichi, BIOS P1.80 04/06/2018 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] Oct 18 21:51:26 ezra.blanchardmorris.net kernel: RIP: 0010:generic_reg_wait.cold+0x31/0x53 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel: Code: 4c 24 18 44 89 fa 89= ee 48 c7 c7 f8 9d 73 c0 e8 60 46 b0 fa 83 7b 20 01 0f 84 02 ee fd ff 48 c7 c7 = f0 9c 73 c0 e8 4a 46 b0 fa <0f> 0b e9 ef ed fd ff 48 c7 c7 f0 9c 73 c0 89 54 2= 4 04 e8 33 46 b0 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: RSP: 0018:ffffabda8729b690 EFLAGS: 00010246 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: RAX: 0000000000000024 RBX: ffff9ceeab58f700 RCX: 0000000000000006 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: RDX: 0000000000000000 RSI: ffff9ceeb50c8e50 RDI: ffff9ceebe5d9e00 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: RBP: 000000000000000a R08: 000003f33c33ca38 R09: 0000000000000000 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 00000000000035af Oct 18 21:51:26 ezra.blanchardmorris.net kernel: R13: 0000000000000dad R14: 0000000000000001 R15: 0000000000000dac Oct 18 21:51:26 ezra.blanchardmorris.net kernel: FS: 0000000000000000(0000) GS:ffff9ceebe400000(0000) knlGS:0000000000000000 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: CR2: 00007f1480ef70c0 CR3: 0000000703f30002 CR4: 00000000003606f0 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: Call Trace: Oct 18 21:51:26 ezra.blanchardmorris.net kernel: dce_mi_free_dmif+0xef/0x1= 50 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20 dce110_reset_hw_ctx_wrap+0x15f/0x200 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20 dce110_apply_ctx_to_hw+0x4b/0x530 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? amdgpu_pm_compute_clocks+0xc9/0x5f0 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? dm_pp_apply_display_requirements+0x1a8/0x1c0 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel: dc_commit_state+0x26b/0x5= 90 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20 amdgpu_dm_atomic_commit_tail+0xd18/0x1cf0 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? __lock_acquire+0x247/0x= 1910 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? find_held_lock+0x32/0x90 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? find_held_lock+0x32/0x90 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? sched_clock+0x5/0x10 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? mark_held_locks+0x50/0x= 80 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? __lock_acquire+0x247/0x= 1910 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? wake_up_klogd+0x37/0x40 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? find_held_lock+0x32/0x90 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? mark_held_locks+0x50/0x= 80 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? _raw_spin_unlock_irq+0x29/0x40 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? lockdep_hardirqs_on+0xf0/0x180 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? _raw_spin_unlock_irq+0x29/0x40 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? wait_for_completion_timeout+0x75/0x190 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? commit_tail+0x3c/0x70 [drm_kms_helper] Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? amdgpu_dm_audio_eld_notify+0x60/0x60 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel: commit_tail+0x3c/0x70 [drm_kms_helper] Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20 drm_atomic_helper_commit+0xe3/0x150 [drm_kms_helper] Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20 drm_atomic_helper_disable_all+0x14c/0x160 [drm_kms_helper] Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20 drm_atomic_helper_suspend+0x66/0x100 [drm_kms_helper] Oct 18 21:51:26 ezra.blanchardmorris.net kernel: dm_suspend+0x20/0x60 [amd= gpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20 amdgpu_device_ip_suspend_phase1+0x91/0xc0 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20 amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20 amdgpu_device_pre_asic_reset+0x191/0x1a4 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20 amdgpu_device_gpu_recover+0x260/0x934 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20 amdgpu_job_timedout+0x115/0x140 [amdgpu] Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20 drm_sched_job_timedout+0x44/0xa0 [gpu_sched] Oct 18 21:51:26 ezra.blanchardmorris.net kernel: process_one_work+0x272/0x= 5a0 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: worker_thread+0x50/0x3b0 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: kthread+0x108/0x140 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? process_one_work+0x5a0/0x5a0 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ? kthread_park+0x80/0x80 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ret_from_fork+0x3a/0x50 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: irq event stamp: 82808 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: hardirqs last enabled at (82807): [] console_unlock+0x46b/0x5d0 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: hardirqs last disabled at (82808): [] trace_hardirqs_off_thunk+0x1a/0x20 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: softirqs last enabled at (82794): [] __do_softirq+0x35d/0x45d Oct 18 21:51:26 ezra.blanchardmorris.net kernel: softirqs last disabled at (82787): [] irq_exit+0xf7/0x100 Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ---[ end trace 71731c9cc205c24d ]--- Oct 18 21:51:27 ezra.blanchardmorris.net abrt-dump-journal-oops[1493]: abrt-dump-journal-oops: Found oopses: 1 Oct 18 21:51:27 ezra.blanchardmorris.net abrt-dump-journal-oops[1493]: abrt-dump-journal-oops: Creating problem directories Oct 18 21:51:27 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:28 ezra.blanchardmorris.net abrt-dump-journal-oops[1493]: Repo= rted 1 kernel oopses to Abrt Oct 18 21:51:29 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:29 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed= to send message: 0x26, ret value: 0x0 Oct 18 21:51:30 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:32 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:32 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0x1, error code: 0x0 Oct 18 21:51:34 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:35 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:35 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0x3, error code: 0x0 Oct 18 21:51:37 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:38 ezra.blanchardmorris.net abrt-server[16691]: Can't find a meaningful backtrace for hashing in '.' Oct 18 21:51:38 ezra.blanchardmorris.net abrt-server[16691]: Option 'DropNotReportableOopses' is not configured Oct 18 21:51:38 ezra.blanchardmorris.net abrt-server[16691]: Preserving oops '.' because DropNotReportableOopses is 'no' Oct 18 21:51:38 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:38 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed= to send message: 0x63, ret value: 0x0 Oct 18 21:51:40 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:42 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:42 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed message: 0x9, input parameter: 0xf4, error code: 0x0 Oct 18 21:51:42 ezra.blanchardmorris.net abrt-notification[16713]: System encountered a non-fatal error in ??() Oct 18 21:51:43 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu Oct 18 21:51:45 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No response from smu --=20 You are receiving this mail because: You are the assignee for the bug.= --15715204195.Fba0e4b.6266 Date: Sat, 19 Oct 2019 21:26:59 +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 # 114 on bug 10995= 5 from Rodney A Morris 
To rule out possible hardware issues, I purchased another Vega=
 64 card.  This
time a factory overclocked card.  Since installing the card, I have experie=
nced
three lock ups.  Two playing Stellaris and one while playing a youtube vide=
o.=20
After playing Stellaris without issue two weeks ago, the computer locked up
twice last night.  While my previous problems seemed to be, in part, linked=
 to
a circular lock dependence, the last logs indicate something different.  I'm
seeing a lot of powerplay errors after the fence timeout.  Hope this new
information provides some insight into the problem.

         /:-------------:\          rmorris@ezra.blanchardmorris.net=20
       :-------------------::        --------------------------------=20
     :-----------/shhOHbmp---:\      OS: Fedora release 30 (Thirty) x86_64=
=20
   /-----------omMMMNNNMMD  ---:     Kernel: 5.3.6-200.fc30.x86_64=20
  :-----------sMMMMNMNMP.    ---:    Uptime: 16 hours, 21 mins=20
 :-----------:MMMdP-------    ---\   Packages: 2214 (rpm), 36 (flatpak)=20
,------------:MMMd--------    ---:   Shell: bash 5.0.7=20
:------------:MMMd-------    .---:   Resolution: 2560x1440=20
:----    oNMMMMMMMMMNho     .----:   DE: GNOME 3.32.2=20
:--     .+shhhMMMmhhy++   .------/   WM: Mutter=20
:-    -------:MMMd--------------:    WM Theme: Adwaita=20
:-   --------/MMMd-------------;     Theme: Adapta-Nokto-Eta [GTK2/3]=20
:-    ------/hMMMy------------:      Icons: Adwaita [GTK2/3]=20
:-- :dMNdhhdNMMNo------------;       Terminal: tilix=20
:---:sdNMMMMNds:------------:        CPU: Intel i7-6850K (12) @ 4.000GH=
z=20
:------:://:-------------::          GPU: AMD ATI Radeon RX Vega 56/64=20
:---------------------://            Memory: 2814MiB / 32036MiB=20


Card:

MSI Vega 64 OC (Card works fine under windows 10)

Game being played:

Stellaris

Native Game

Description of Event:
Screen goes blank and music and sound continues to play before computer loc=
ks
up or reboots.

relevant dmesg from crash:
[ 4244.670269] perf: interrupt took too long (2502 > 2500), lowering
kernel.perf_event_max_sample_rate to 79000
[ 4298.241156] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting =
for
fences timed out or interrupted!
[ 4304.385587] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring page1 timeou=
t,
signaled seq=3D60549844, emitted seq=3D60549846
[ 4304.385634] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati=
on:
process  pid 0 thread  pid 0
[ 4304.385637] amdgpu 0000:06:00.0: GPU reset begin!
[ 4304.402938] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 4304.402945] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 4304.402947] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 4304.402948] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 4304.404006] pcieport 0000:00:03.0: AER: Device recovery failed
[ 4308.481068] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
*ERROR* [CRTC:47:crtc-0] flip_done timed out
[ 4314.625180] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-=
0]
hw_done or flip_done timed out
[ 4324.865057] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper=
]]
*ERROR* [CRTC:47:crtc-0] flip_done timed out
[ 4335.105035] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper=
]]
*ERROR* [PLANE:45:plane-5] flip_done timed out
[ 4336.695112] amdgpu: [powerplay] No response from smu
[ 4336.695128] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x=
0,
error code: 0x0
[ 4338.307125] amdgpu: [powerplay] No response from smu
[ 4339.922039] amdgpu: [powerplay] No response from smu
[ 4339.922043] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0=
x1,
error code: 0x0
[ 4341.541675] amdgpu: [powerplay] No response from smu
[ 4343.162102] amdgpu: [powerplay] No response from smu
[ 4343.162105] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0=
x0,
error code: 0x0
[ 4343.221953] [drm] REG_WAIT timeout 10us * 3500 tries - dce_mi_free_dmif
line:634
[ 4343.221962] ------------[ cut here ]------------
[ 4343.222070] WARNING: CPU: 0 PID: 16500 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:332
generic_reg_wait.cold+0x31/0x53 [amdgpu]
[ 4343.222072] Modules linked in: rfcomm xt_CHECKSUM xt_MASQUERADE tun brid=
ge
stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter
ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_n=
at
ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security
iptable_nat nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter
ebtables ip6table_filter ip6_tables iptable_filter ip_tables cmac bnep nct6=
775
hwmon_vid intel_rapl_msr intel_rapl_common vfat fat fuse x86_pkg_temp_therm=
al
intel_powerclamp coretemp iwlmvm kvm_intel iTCO_wdt iTCO_vendor_support
mac80211 kvm snd_hda_codec_realtek irqbypass snd_hda_codec_generic
snd_hda_codec_hdmi libarc4 ledtrig_audio crct10dif_pclmul snd_hda_intel
crc32_pclmul iwlwifi snd_hda_codec snd_hda_core btusb ghash_clmulni_intel b=
trtl
intel_cstate snd_hwdep btbcm btintel intel_uncore snd_seq snd_seq_device
intel_rapl_perf bluetooth
[ 4343.222099]  mxm_wmi cfg80211 snd_pcm joydev ecdh_generic ecc mei_me
snd_timer rfkill snd mei i2c_i801 soundcore lpc_ich binfmt_misc auth_rpcgss
sunrpc amdgpu amd_iommu_v2 gpu_sched ttm drm_kms_helper crc32c_intel uas
mpt3sas igb drm e1000e nvme usb_storage dca i2c_algo_bit raid_class nvme_co=
re
scsi_transport_sas wmi
[ 4343.222114] CPU: 0 PID: 16500 Comm: kworker/0:1 Not tainted
5.3.6-200.fc30.x86_64+debug #1
[ 4343.222115] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M.=
/X99
Taichi, BIOS P1.80 04/06/2018
[ 4343.222119] Workqueue: events drm_sched_job_timedout [gpu_sched]
[ 4343.222167] RIP: 0010:generic_reg_wait.cold+0x31/0x53 [amdgpu]
[ 4343.222169] Code: 4c 24 18 44 89 fa 89 ee 48 c7 c7 f8 9d 73 c0 e8 60 46 =
b0
fa 83 7b 20 01 0f 84 02 ee fd ff 48 c7 c7 f0 9c 73 c0 e8 4a 46 b0 fa <0f=
> 0b e9
ef ed fd ff 48 c7 c7 f0 9c 73 c0 89 54 24 04 e8 33 46 b0
[ 4343.222170] RSP: 0018:ffffabda8729b690 EFLAGS: 00010246
[ 4343.222172] RAX: 0000000000000024 RBX: ffff9ceeab58f700 RCX:
0000000000000006
[ 4343.222173] RDX: 0000000000000000 RSI: ffff9ceeb50c8e50 RDI:
ffff9ceebe5d9e00
[ 4343.222174] RBP: 000000000000000a R08: 000003f33c33ca38 R09:
0000000000000000
[ 4343.222175] R10: 0000000000000000 R11: 0000000000000000 R12:
00000000000035af
[ 4343.222176] R13: 0000000000000dad R14: 0000000000000001 R15:
0000000000000dac
[ 4343.222178] FS:  0000000000000000(0000) GS:ffff9ceebe400000(0000)
knlGS:0000000000000000
[ 4343.222179] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 4343.222180] CR2: 00007f1480ef70c0 CR3: 0000000703f30002 CR4:
00000000003606f0
[ 4343.222182] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 4343.222183] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
0000000000000400
[ 4343.222184] Call Trace:
[ 4343.222237]  dce_mi_free_dmif+0xef/0x150 [amdgpu]
[ 4343.222285]  dce110_reset_hw_ctx_wrap+0x15f/0x200 [amdgpu]
[ 4343.222333]  dce110_apply_ctx_to_hw+0x4b/0x530 [amdgpu]
[ 4343.222365]  ? amdgpu_pm_compute_clocks+0xc9/0x5f0 [amdgpu]
[ 4343.222414]  ? dm_pp_apply_display_requirements+0x1a8/0x1c0 [amdgpu]
[ 4343.222461]  dc_commit_state+0x26b/0x590 [amdgpu]
[ 4343.222514]  amdgpu_dm_atomic_commit_tail+0xd18/0x1cf0 [amdgpu]
[ 4343.222521]  ? __lock_acquire+0x247/0x1910
[ 4343.222525]  ? find_held_lock+0x32/0x90
[ 4343.222529]  ? find_held_lock+0x32/0x90
[ 4343.222533]  ? sched_clock+0x5/0x10
[ 4343.222536]  ? mark_held_locks+0x50/0x80
[ 4343.222540]  ? __lock_acquire+0x247/0x1910
[ 4343.222545]  ? wake_up_klogd+0x37/0x40
[ 4343.222549]  ? find_held_lock+0x32/0x90
[ 4343.222552]  ? mark_held_locks+0x50/0x80
[ 4343.222556]  ? _raw_spin_unlock_irq+0x29/0x40
[ 4343.222559]  ? lockdep_hardirqs_on+0xf0/0x180
[ 4343.222561]  ? _raw_spin_unlock_irq+0x29/0x40
[ 4343.222564]  ? wait_for_completion_timeout+0x75/0x190
[ 4343.222576]  ? commit_tail+0x3c/0x70 [drm_kms_helper]
[ 4343.222622]  ? amdgpu_dm_audio_eld_notify+0x60/0x60 [amdgpu]
[ 4343.222628]  commit_tail+0x3c/0x70 [drm_kms_helper]
[ 4343.222634]  drm_atomic_helper_commit+0xe3/0x150 [drm_kms_helper]
[ 4343.222640]  drm_atomic_helper_disable_all+0x14c/0x160 [drm_kms_helper]
[ 4343.222647]  drm_atomic_helper_suspend+0x66/0x100 [drm_kms_helper]
[ 4343.222698]  dm_suspend+0x20/0x60 [amdgpu]
[ 4343.222726]  amdgpu_device_ip_suspend_phase1+0x91/0xc0 [amdgpu]
[ 4343.222755]  amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu]
[ 4343.222801]  amdgpu_device_pre_asic_reset+0x191/0x1a4 [amdgpu]
[ 4343.222849]  amdgpu_device_gpu_recover+0x260/0x934 [amdgpu]
[ 4343.222893]  amdgpu_job_timedout+0x115/0x140 [amdgpu]
[ 4343.222899]  drm_sched_job_timedout+0x44/0xa0 [gpu_sched]
[ 4343.222903]  process_one_work+0x272/0x5a0
[ 4343.222908]  worker_thread+0x50/0x3b0
[ 4343.222915]  kthread+0x108/0x140
[ 4343.222916]  ? process_one_work+0x5a0/0x5a0
[ 4343.222918]  ? kthread_park+0x80/0x80
[ 4343.222921]  ret_from_fork+0x3a/0x50
[ 4343.222929] irq event stamp: 82808
[ 4343.222931] hardirqs last  enabled at (82807): [<ffffffffbb1716eb>]
console_unlock+0x46b/0x5d0
[ 4343.222935] hardirqs last disabled at (82808): [<ffffffffbb0038da>]
trace_hardirqs_off_thunk+0x1a/0x20
[ 4343.222938] softirqs last  enabled at (82794): [<ffffffffbbe0035d>]
__do_softirq+0x35d/0x45d
[ 4343.222942] softirqs last disabled at (82787): [<ffffffffbb0f2077>]
irq_exit+0xf7/0x100
[ 4343.222943] ---[ end trace 71731c9cc205c24d ]---
[ 4344.758203] amdgpu: [powerplay] No response from smu
[ 4346.363061] amdgpu: [powerplay] No response from smu
[ 4346.363065] amdgpu: [powerplay] Failed to send message: 0x26, ret value:=
 0x0
[ 4347.973948] amdgpu: [powerplay] No response from smu
[ 4349.588168] amdgpu: [powerplay] No response from smu
[ 4349.588173] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0=
x1,
error code: 0x0
[ 4351.152764] amdgpu: [powerplay] No response from smu
[ 4352.722063] amdgpu: [powerplay] No response from smu
[ 4352.722068] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0=
x3,
error code: 0x0
[ 4354.325541] amdgpu: [powerplay] No response from smu
[ 4355.924138] amdgpu: [powerplay] No response from smu
[ 4355.924141] amdgpu: [powerplay] Failed to send message: 0x63, ret value:=
 0x0
[ 4357.537736] amdgpu: [powerplay] No response from smu
[ 4359.154141] amdgpu: [powerplay] No response from smu
[ 4359.154146] amdgpu: [powerplay] Failed message: 0x9, input parameter: 0x=
f4,
error code: 0x0
[ 4360.760856] amdgpu: [powerplay] No response from smu
[ 4362.372410] amdgpu: [powerplay] No response from smu
[ 4362.372414] amdgpu: [powerplay] Failed message: 0xa, input parameter:
0xa0b000, error code: 0x0
[ 4363.985961] amdgpu: [powerplay] No response from smu
[ 4365.599325] amdgpu: [powerplay] No response from smu
[ 4365.599331] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x=
0,
error code: 0x0
[ 4367.214945] amdgpu: [powerplay] No response from smu
[ 4368.829650] amdgpu: [powerplay] No response from smu
[ 4368.829655] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0=
x1,
error code: 0x0
[ 4370.443783] amdgpu: [powerplay] No response from smu
[ 4372.057288] amdgpu: [powerplay] No response from smu
[ 4372.057293] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0=
x0,
error code: 0x0
[ 4372.074301] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 4372.074308] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 4372.074310] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 4372.074312] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 4372.074569] pcieport 0000:00:03.0: AER: Device recovery failed
[ 4372.091832] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 4372.091837] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 4372.091839] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 4372.091840] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 4372.091889] pcieport 0000:00:03.0: AER: Device recovery failed
[ 4372.109371] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 4372.109376] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 4372.109378] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 4372.109380] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 4372.126998] pcieport 0000:00:03.0: AER: Device recovery failed
[ 4372.127002] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 4372.127009] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 4372.127021] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 4372.127024] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 4372.127083] pcieport 0000:00:03.0: AER: Device recovery failed
[ 4372.144452] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 4372.144457] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 4372.144458] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 4372.144460] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 4372.144514] pcieport 0000:00:03.0: AER: Device recovery failed
[ 4372.161992] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 4372.161997] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 4372.161999] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 4372.162001] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 4372.162086] pcieport 0000:00:03.0: AER: Device recovery failed
[ 4372.179534] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 4372.179538] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 4372.179540] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 4372.179542] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 4372.179674] pcieport 0000:00:03.0: AER: Device recovery failed
[ 4372.197074] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[ 4372.197079] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[ 4372.197081] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[ 4372.197082] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[ 4372.197131] pcieport 0000:00:03.0: AER: Device recovery failed
[ 4372.214616] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal)
error received: 0000:00:03.0
[ 4372.267239] amdgpu: [powerplay] Failed to send message: 0x61, ret value:
0xffffffff

Relevant journalctl messages:

Oct 18 21:49:47 ezra.blanchardmorris.net kernel: perf: interrupt took too l=
ong
(2502 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
Oct 18 21:50:47 ezra.blanchardmorris.net kernel:
[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed
out or interrupted!
Oct 18 21:50:47 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout
[amdgpu]] *ERROR* ring page1 timeout, signaled seq=3D60549844, emitted
seq=3D60549846
Oct 18 21:50:47 ezra.blanchardmorris.net kernel: [drm:amdgpu_job_timedout
[amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
Oct 18 21:50:47 ezra.blanchardmorris.net kernel: amdgpu 0000:06:00.0: GPU r=
eset
begin!
Oct 18 21:50:47 ezra.blanchardmorris.net kernel: pcieport 0000:00:03.0: AER:
Uncorrected (Non-Fatal) error received: 0000:00:03.0
Oct 18 21:50:47 ezra.blanchardmorris.net kernel: pcieport 0000:00:03.0: AER:
PCIe Bus Error: severity=3DUncorrected (Non-Fatal), type=3DTransaction Laye=
r,
(Requester ID)
Oct 18 21:50:47 ezra.blanchardmorris.net kernel: pcieport 0000:00:03.0: AER=
:=20=20
device [8086:6f08] error status/mask=3D00004000/00000000
Oct 18 21:50:47 ezra.blanchardmorris.net kernel: pcieport 0000:00:03.0: AER=
:=20=20=20
[14] CmpltTO                (First)
Oct 18 21:50:47 ezra.blanchardmorris.net kernel: pcieport 0000:00:03.0: AER:
Device recovery failed
Oct 18 21:50:51 ezra.blanchardmorris.net kernel:
[drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR*
[CRTC:47:crtc-0] flip_done timed out
Oct 18 21:50:57 ezra.blanchardmorris.net kernel: [drm:amdgpu_dm_atomic_check
[amdgpu]] *ERROR* [CRTC:47:crtc-0] hw_done or flip_done timed out
Oct 18 21:51:07 ezra.blanchardmorris.net kernel:
[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR*
[CRTC:47:crtc-0] flip_done timed out
Oct 18 21:51:18 ezra.blanchardmorris.net kernel:
[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR*
[PLANE:45:plane-5] flip_done timed out
Oct 18 21:51:19 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:19 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed
message: 0xe, input parameter: 0x0, error code: 0x0
Oct 18 21:51:21 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:22 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:22 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed
message: 0x42, input parameter: 0x1, error code: 0x0
Oct 18 21:51:24 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed
message: 0x24, input parameter: 0x0, error code: 0x0
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: [drm] REG_WAIT timeout 10u=
s *
3500 tries - dce_mi_free_dmif line:634
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ------------[ cut here
]------------
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: WARNING: CPU: 0 PID: 16500=
 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:332
generic_reg_wait.cold+0x31/0x53 [amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: Modules linked in: rfcomm
xt_CHECKSUM xt_MASQUERADE tun bridge stp llc nf_conntrack_netbios_ns
nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6
ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_=
nat
ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat
iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6
nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables
ip6table_filter ip6_tables iptable_filter ip_tables cmac bnep nct6775 hwmon=
_vid
intel_rapl_msr intel_rapl_common vfat fat fuse x86_pkg_temp_thermal
intel_powerclamp coretemp iwlmvm kvm_intel iTCO_wdt iTCO_vendor_support
mac80211 kvm snd_hda_codec_realtek irqbypass snd_hda_codec_generic
snd_hda_codec_hdmi libarc4 ledtrig_audio crct10dif_pclmul snd_hda_intel
crc32_pclmul iwlwifi snd_hda_codec snd_hda_core btusb ghash_clmulni_intel b=
trtl
intel_cstate snd_hwdep btbcm btintel intel_uncore snd_seq snd_seq_device
intel_rapl_perf bluetooth
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  mxm_wmi cfg80211 snd_pcm
joydev ecdh_generic ecc mei_me snd_timer rfkill snd mei i2c_i801 soundcore
lpc_ich binfmt_misc auth_rpcgss sunrpc amdgpu amd_iommu_v2 gpu_sched ttm
drm_kms_helper crc32c_intel uas mpt3sas igb drm e1000e nvme usb_storage dca
i2c_algo_bit raid_class nvme_core scsi_transport_sas wmi
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: CPU: 0 PID: 16500 Comm:
kworker/0:1 Not tainted 5.3.6-200.fc30.x86_64+debug #1
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: Hardware name: To Be Fille=
d By
O.E.M. To Be Filled By O.E.M./X99 Taichi, BIOS P1.80 04/06/2018
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: Workqueue: events
drm_sched_job_timedout [gpu_sched]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: RIP:
0010:generic_reg_wait.cold+0x31/0x53 [amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: Code: 4c 24 18 44 89 fa 89=
 ee
48 c7 c7 f8 9d 73 c0 e8 60 46 b0 fa 83 7b 20 01 0f 84 02 ee fd ff 48 c7 c7 =
f0
9c 73 c0 e8 4a 46 b0 fa <0f> 0b e9 ef ed fd ff 48 c7 c7 f0 9c 73 c0 8=
9 54 24 04
e8 33 46 b0
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: RSP: 0018:ffffabda8729b690
EFLAGS: 00010246
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: RAX: 0000000000000024 RBX:
ffff9ceeab58f700 RCX: 0000000000000006
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: RDX: 0000000000000000 RSI:
ffff9ceeb50c8e50 RDI: ffff9ceebe5d9e00
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: RBP: 000000000000000a R08:
000003f33c33ca38 R09: 0000000000000000
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: R10: 0000000000000000 R11:
0000000000000000 R12: 00000000000035af
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: R13: 0000000000000dad R14:
0000000000000001 R15: 0000000000000dac
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: FS:  0000000000000000(0000)
GS:ffff9ceebe400000(0000) knlGS:0000000000000000
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: CS:  0010 DS: 0000 ES: 0000
CR0: 0000000080050033
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: CR2: 00007f1480ef70c0 CR3:
0000000703f30002 CR4: 00000000003606f0
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: DR3: 0000000000000000 DR6:
00000000fffe0ff0 DR7: 0000000000000400
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: Call Trace:
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  dce_mi_free_dmif+0xef/0x1=
50
[amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20
dce110_reset_hw_ctx_wrap+0x15f/0x200 [amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20
dce110_apply_ctx_to_hw+0x4b/0x530 [amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ?
amdgpu_pm_compute_clocks+0xc9/0x5f0 [amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ?
dm_pp_apply_display_requirements+0x1a8/0x1c0 [amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  dc_commit_state+0x26b/0x5=
90
[amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20
amdgpu_dm_atomic_commit_tail+0xd18/0x1cf0 [amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ? __lock_acquire+0x247/0x=
1910
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ? find_held_lock+0x32/0x90
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ? find_held_lock+0x32/0x90
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ? sched_clock+0x5/0x10
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ? mark_held_locks+0x50/0x=
80
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ? __lock_acquire+0x247/0x=
1910
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ? wake_up_klogd+0x37/0x40
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ? find_held_lock+0x32/0x90
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ? mark_held_locks+0x50/0x=
80
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ?
_raw_spin_unlock_irq+0x29/0x40
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ?
lockdep_hardirqs_on+0xf0/0x180
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ?
_raw_spin_unlock_irq+0x29/0x40
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ?
wait_for_completion_timeout+0x75/0x190
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ? commit_tail+0x3c/0x70
[drm_kms_helper]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ?
amdgpu_dm_audio_eld_notify+0x60/0x60 [amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  commit_tail+0x3c/0x70
[drm_kms_helper]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20
drm_atomic_helper_commit+0xe3/0x150 [drm_kms_helper]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20
drm_atomic_helper_disable_all+0x14c/0x160 [drm_kms_helper]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20
drm_atomic_helper_suspend+0x66/0x100 [drm_kms_helper]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  dm_suspend+0x20/0x60 [amd=
gpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20
amdgpu_device_ip_suspend_phase1+0x91/0xc0 [amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20
amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20
amdgpu_device_pre_asic_reset+0x191/0x1a4 [amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20
amdgpu_device_gpu_recover+0x260/0x934 [amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20
amdgpu_job_timedout+0x115/0x140 [amdgpu]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:=20
drm_sched_job_timedout+0x44/0xa0 [gpu_sched]
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  process_one_work+0x272/0x=
5a0
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  worker_thread+0x50/0x3b0
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  kthread+0x108/0x140
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ?
process_one_work+0x5a0/0x5a0
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ? kthread_park+0x80/0x80
Oct 18 21:51:26 ezra.blanchardmorris.net kernel:  ret_from_fork+0x3a/0x50
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: irq event stamp: 82808
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: hardirqs last  enabled at
(82807): [<ffffffffbb1716eb>] console_unlock+0x46b/0x5d0
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: hardirqs last disabled at
(82808): [<ffffffffbb0038da>] trace_hardirqs_off_thunk+0x1a/0x20
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: softirqs last  enabled at
(82794): [<ffffffffbbe0035d>] __do_softirq+0x35d/0x45d
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: softirqs last disabled at
(82787): [<ffffffffbb0f2077>] irq_exit+0xf7/0x100
Oct 18 21:51:26 ezra.blanchardmorris.net kernel: ---[ end trace
71731c9cc205c24d ]---
Oct 18 21:51:27 ezra.blanchardmorris.net abrt-dump-journal-oops[1493]:
abrt-dump-journal-oops: Found oopses: 1
Oct 18 21:51:27 ezra.blanchardmorris.net abrt-dump-journal-oops[1493]:
abrt-dump-journal-oops: Creating problem directories
Oct 18 21:51:27 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:28 ezra.blanchardmorris.net abrt-dump-journal-oops[1493]: Repo=
rted
1 kernel oopses to Abrt
Oct 18 21:51:29 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:29 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed=
 to
send message: 0x26, ret value: 0x0
Oct 18 21:51:30 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:32 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:32 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed
message: 0x4c, input parameter: 0x1, error code: 0x0
Oct 18 21:51:34 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:35 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:35 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed
message: 0x4c, input parameter: 0x3, error code: 0x0
Oct 18 21:51:37 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:38 ezra.blanchardmorris.net abrt-server[16691]: Can't find a
meaningful backtrace for hashing in '.'
Oct 18 21:51:38 ezra.blanchardmorris.net abrt-server[16691]: Option
'DropNotReportableOopses' is not configured
Oct 18 21:51:38 ezra.blanchardmorris.net abrt-server[16691]: Preserving oops
'.' because DropNotReportableOopses is 'no'
Oct 18 21:51:38 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:38 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed=
 to
send message: 0x63, ret value: 0x0
Oct 18 21:51:40 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:42 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:42 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] Failed
message: 0x9, input parameter: 0xf4, error code: 0x0
Oct 18 21:51:42 ezra.blanchardmorris.net abrt-notification[16713]: System
encountered a non-fatal error in ??()
Oct 18 21:51:43 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu
Oct 18 21:51:45 ezra.blanchardmorris.net kernel: amdgpu: [powerplay] No
response from smu

You are receiving this mail because:
  • You are the assignee for the bug.
= --15715204195.Fba0e4b.6266-- --===============0045920798== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0045920798==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 19 Oct 2019 21:27:39 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0112879793==" 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 380E889C1B for ; Sat, 19 Oct 2019 21:27:40 +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 --===============0112879793== Content-Type: multipart/alternative; boundary="15715204603.cD40.6650" Content-Transfer-Encoding: 7bit --15715204603.cD40.6650 Date: Sat, 19 Oct 2019 21:27:40 +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=3D109955 --- Comment #115 from Rodney A Morris --- Created attachment 145776 --> https://bugs.freedesktop.org/attachment.cgi?id=3D145776&action=3Dedit Full dmesg from crash Full dmesg from crash --=20 You are receiving this mail because: You are the assignee for the bug.= --15715204603.cD40.6650 Date: Sat, 19 Oct 2019 21:27:40 +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 # 115 on bug 10995= 5 from Rodney A Morris 
Created attachment 145776<=
/a> [details]
Full dmesg from crash

Full dmesg from crash

You are receiving this mail because:
  • You are the assignee for the bug.
= --15715204603.cD40.6650-- --===============0112879793== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0112879793==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sat, 19 Oct 2019 21:28:18 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0092529806==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 1714489C3F for ; Sat, 19 Oct 2019 21:28:19 +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 --===============0092529806== Content-Type: multipart/alternative; boundary="15715204991.eC69606E.6628" Content-Transfer-Encoding: 7bit --15715204991.eC69606E.6628 Date: Sat, 19 Oct 2019 21:28:19 +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=3D109955 --- Comment #116 from Rodney A Morris --- Created attachment 145777 --> https://bugs.freedesktop.org/attachment.cgi?id=3D145777&action=3Dedit Full journal from start to crash Full journalctl from start to crash. --=20 You are receiving this mail because: You are the assignee for the bug.= --15715204991.eC69606E.6628 Date: Sat, 19 Oct 2019 21:28:19 +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 # 116 on bug 10995= 5 from Rodney A Morris 
Created attachm=
ent 145777 [details]
Full journal from start to crash

Full journalctl from start to crash.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15715204991.eC69606E.6628-- --===============0092529806== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0092529806==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Mon, 21 Oct 2019 16:24:35 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1743228681==" 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 16B746E180 for ; Mon, 21 Oct 2019 16:24:35 +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 --===============1743228681== Content-Type: multipart/alternative; boundary="15716750750.c25d.15198" Content-Transfer-Encoding: 7bit --15716750750.c25d.15198 Date: Mon, 21 Oct 2019 16:24:35 +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=3D109955 --- Comment #117 from haro41@gmx.de --- ...are this craches more frequently with VSYNC enabled? If yes, it could be the same thing like this bug: https://bugs.freedesktop.org/show_bug.cgi?id=3D110777 --=20 You are receiving this mail because: You are the assignee for the bug.= --15716750750.c25d.15198 Date: Mon, 21 Oct 2019 16:24:35 +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 10995= 5 from haro41@gmx.de 
...are this craches more frequently with VSYNC enabled?

If yes, it could be the same thing like this bug:

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

You are receiving this mail because:
  • You are the assignee for the bug.
= --15716750750.c25d.15198-- --===============1743228681== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1743228681==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 23 Oct 2019 01:52:58 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0012655307==" 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 9555D6E94B for ; Wed, 23 Oct 2019 01:52:59 +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 --===============0012655307== Content-Type: multipart/alternative; boundary="15717955797.9D5Ce13E.32387" Content-Transfer-Encoding: 7bit --15717955797.9D5Ce13E.32387 Date: Wed, 23 Oct 2019 01:52:59 +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=3D109955 --- Comment #118 from Rodney A Morris --- (In reply to haro41 from comment #117) > ...are this craches more frequently with VSYNC enabled? >=20 > If yes, it could be the same thing like this bug: >=20 > https://bugs.freedesktop.org/show_bug.cgi?id=3D110777 vsync is defintely on for both Stellaris and Hearts of Iron. I looked over the bug report you linked to. It is very interesting and I w= ill follow with interest. The next time I play Stellaris or Hearts of Iron IV,= I will have to see if I can record my memory frequency values to see if they = are indeed not moving off the base frequency under low load with v-sync enabled= .=20 The problem manifesting under low load would explain why I cannot replicate= the problem while running Unigine Superposition. I began to wonder if powerplay and the frequency at which the chip and memo= ry were operating were not the problem after reading the following bug report = for Vega 20: https://bugs.freedesktop.org/show_bug.cgi?id=3D110674 Last Friday, I attempted to capture the operating frequency and temps, but = my attempt utterly failed. I will disable v-sync and see if that improves and report back here. If I manage to capture frequency data, I will report back here and may be your thread. --=20 You are receiving this mail because: You are the assignee for the bug.= --15717955797.9D5Ce13E.32387 Date: Wed, 23 Oct 2019 01:52:59 +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 # 118 on bug 10995= 5 from Rodney A Morris 
(In reply to haro41 from comment #117)
> ...are this craches more frequently with VSYNC e=
nabled?
>=20
> If yes, it could be the same thing like this bug:
>=20
> https://bugs.freedesktop.org/show_bug.=
cgi?id=3D110777

vsync is defintely on for both Stellaris and Hearts of Iron.

I looked over the bug report you linked to.  It is very interesting and I w=
ill
follow with interest.  The next time I play Stellaris or Hearts of Iron IV,=
 I
will have to see if I can record my memory frequency values to see if they =
are
indeed not moving off the base frequency under low load with v-sync enabled=
.=20
The problem manifesting under low load would explain why I cannot replicate=
 the
problem while running Unigine Superposition.

I began to wonder if powerplay and the frequency at which the chip and memo=
ry
were operating were not the problem after reading the following bug report =
for
Vega 20:

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

Last Friday, I attempted to capture the operating frequency and temps, but =
my
attempt utterly failed.

I will disable v-sync and see if that improves and report back here.  If I
manage to capture frequency data, I will report back here and may be your
thread.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15717955797.9D5Ce13E.32387-- --===============0012655307== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0012655307==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 23 Oct 2019 08:51:29 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1908157518==" 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 7B04C6E9F2 for ; Wed, 23 Oct 2019 08:51:29 +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 --===============1908157518== Content-Type: multipart/alternative; boundary="15718206896.da3e5.29017" Content-Transfer-Encoding: 7bit --15718206896.da3e5.29017 Date: Wed, 23 Oct 2019 08:51:29 +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=3D109955 --- Comment #119 from haro41@gmx.de --- bellow is a simple script, i use to record dpm data in the background: ###################################################### #!/bin/bash # adapt this sample inverval (seconds) SLEEP_INTERVAL=3D0.05 # adapt the paths to your need FILE_SCLK=3D/sys/class/drm/card0/device/hwmon/hwmon0/freq1_input FILE_MCLK=3D/sys/class/drm/card0/device/hwmon/hwmon0/freq2_input FILE_PWM=3D/sys/class/drm/card0/device/hwmon/hwmon0/pwm1 FILE_TEMP=3D/sys/class/drm/card0/device/hwmon/hwmon0/temp1_input FILE_FAN=3D/sys/class/drm/card0/device/hwmon/hwmon0/fan1_input FILE_GFXVDD=3D/sys/class/drm/card0/device/hwmon/hwmon0/in0_input FILE_POW=3D/sys/class/drm/card0/device/hwmon/hwmon0/power1_average FILE_BUS=3D/sys/class/drm/card0/device/gpu_busy_percent # checking for privileges if [ $UID -ne 0 ] then echo "Writing to sysfs requires privileges, relaunch as root" exit 1 fi function read_output { SCLK=3D$(cat $FILE_SCLK) MCLK=3D$(cat $FILE_MCLK) TEMP=3D$(cat $FILE_TEMP) FAN=3D$(cat $FILE_FAN) GFXVDD=3D$(cat $FILE_GFXVDD) POW=3D$(cat $FILE_POW) BUS=3D$(cat $FILE_BUS) # echo "sclk: $SCLK mclk: $MCLK gfx_vdd: $GFXVDD" echo "sclk: $SCLK mclk: $MCLK temp: $TEMP fan: $FAN gfx_vdd: $GFXVDD pow: $POW bus: $BUS" } function run_daemon { while :; do read_output sleep $SLEEP_INTERVAL done } # finally start the loop run_daemon ###################################################### --=20 You are receiving this mail because: You are the assignee for the bug.= --15718206896.da3e5.29017 Date: Wed, 23 Oct 2019 08:51:29 +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 # 119 on bug 10995= 5 from haro41@gmx.de 
bellow is a simple script, i use to record dpm data in the bac=
kground:

######################################################
#!/bin/bash

# adapt this sample inverval (seconds)
SLEEP_INTERVAL=3D0.05

# adapt the paths to your need
FILE_SCLK=3D/sys/class/drm/card0/device/hwmon/hwmon0/freq1_input
FILE_MCLK=3D/sys/class/drm/card0/device/hwmon/hwmon0/freq2_input
FILE_PWM=3D/sys/class/drm/card0/device/hwmon/hwmon0/pwm1
FILE_TEMP=3D/sys/class/drm/card0/device/hwmon/hwmon0/temp1_input
FILE_FAN=3D/sys/class/drm/card0/device/hwmon/hwmon0/fan1_input
FILE_GFXVDD=3D/sys/class/drm/card0/device/hwmon/hwmon0/in0_input
FILE_POW=3D/sys/class/drm/card0/device/hwmon/hwmon0/power1_average
FILE_BUS=3D/sys/class/drm/card0/device/gpu_busy_percent

# checking for privileges
if [ $UID -ne 0 ]
then
  echo "Writing to sysfs requires privileges, relaunch as root"
  exit 1
fi

function read_output {

  SCLK=3D$(cat $FILE_SCLK)
  MCLK=3D$(cat $FILE_MCLK)
  TEMP=3D$(cat $FILE_TEMP)
  FAN=3D$(cat $FILE_FAN)
  GFXVDD=3D$(cat $FILE_GFXVDD)
  POW=3D$(cat $FILE_POW)
  BUS=3D$(cat $FILE_BUS)

#  echo "sclk: $SCLK mclk: $MCLK gfx_vdd: $GFXVDD"
  echo "sclk: $SCLK mclk: $MCLK temp: $TEMP fan: $FAN gfx_vdd: $GFXVDD=
 pow:
$POW bus: $BUS"
}

function run_daemon {
  while :; do
    read_output
    sleep $SLEEP_INTERVAL
  done
}

# finally start the loop
run_daemon

######################################################

You are receiving this mail because:
  • You are the assignee for the bug.
= --15718206896.da3e5.29017-- --===============1908157518== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1908157518==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 24 Oct 2019 03:12:28 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1058609190==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 80D326E08C for ; Thu, 24 Oct 2019 03:12:28 +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 --===============1058609190== Content-Type: multipart/alternative; boundary="15718867487.2AC07E45a.13918" Content-Transfer-Encoding: 7bit --15718867487.2AC07E45a.13918 Date: Thu, 24 Oct 2019 03:12:28 +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=3D109955 --- Comment #120 from blppt@yahoo.com --- I dont have anything to attach here, but same issue here, ubuntu 19.04, ker= nel 5.4-rc3, vega64 W/C, Mesa 19.3.0 -- it only seems to occur with DXVK and not D9VK for some reason. Example: GW2 (DX9 game) will work perfectly under heavy load in WvW with massive zergs for hours with no crash, but FFXIV (DX11) will always lock the entire system up after a time. That being said, when you force the top clock using echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_level and echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk FFXIV no longer locks the system at all. It does eat up a good deal more wa= tts according to my UPS meter though, so resetting to auto is necessary IMHO. So, it sounds like you guys are on the right track with the whole "power management" thing being the culprit. Just wanted to add my experience to th= is. (and yes, echoing the guy above, the exact same system is stable in windows= 10, so its not a hardware issue). --=20 You are receiving this mail because: You are the assignee for the bug.= --15718867487.2AC07E45a.13918 Date: Thu, 24 Oct 2019 03:12:28 +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 # 120 on bug 10995= 5 from blppt@yahoo.com 
I dont have anything to attach here, but same issue here, ubun=
tu 19.04, kernel
5.4-rc3, vega64 W/C, Mesa 19.3.0 -- it only seems to occur with DXVK and not
D9VK for some reason.

Example: GW2 (DX9 game) will work perfectly under heavy load in WvW with
massive zergs for hours with no crash, but FFXIV (DX11) will always lock the
entire system up after a time.

That being said, when you force the top clock using

echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_le=
vel

and

echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk

FFXIV no longer locks the system at all. It does eat up a good deal more wa=
tts
according to my UPS meter though, so resetting to auto is necessary IMHO.

So, it sounds like you guys are on the right track with the whole "pow=
er
management" thing being the culprit. Just wanted to add my experience =
to this.

(and yes, echoing the guy above, the exact same system is stable in windows=
 10,
so its not a hardware issue).

You are receiving this mail because:
  • You are the assignee for the bug.
= --15718867487.2AC07E45a.13918-- --===============1058609190== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1058609190==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 24 Oct 2019 04:58:21 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1050342244==" 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 97CE96E0DF for ; Thu, 24 Oct 2019 04:58:21 +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 --===============1050342244== Content-Type: multipart/alternative; boundary="15718931019.dDC18.2092" Content-Transfer-Encoding: 7bit --15718931019.dDC18.2092 Date: Thu, 24 Oct 2019 04:58:21 +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=3D109955 --- Comment #121 from Mauro Gaspari --- (In reply to blppt from comment #120) > I dont have anything to attach here, but same issue here, ubuntu 19.04, > kernel 5.4-rc3, vega64 W/C, Mesa 19.3.0 -- it only seems to occur with DX= VK > and not D9VK for some reason. >=20 > Example: GW2 (DX9 game) will work perfectly under heavy load in WvW with > massive zergs for hours with no crash, but FFXIV (DX11) will always lock = the > entire system up after a time. >=20 > That being said, when you force the top clock using >=20 > echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_lev= el >=20 > and >=20 > echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk >=20 > FFXIV no longer locks the system at all. It does eat up a good deal more > watts according to my UPS meter though, so resetting to auto is necessary > IMHO. >=20 > So, it sounds like you guys are on the right track with the whole "power > management" thing being the culprit. Just wanted to add my experience to > this. >=20 > (and yes, echoing the guy above, the exact same system is stable in windo= ws > 10, so its not a hardware issue). I agree with this. I am having much better experience myself even without commands to force the power performance level by doing: - change game to windowed or full-screen borderless (fixed window) - disable vsync - disable frame limiter by doing the above 3, it seems that GPU is forced into max power state all = the time while playing. I have been using this method for a few days with DXVK games and I had no freeze so far. But again this is just a temporary workaround. So is the command to manually force high power performance level. Hopefully a permanent fix comes with AMDGPU/Kernel updates. --=20 You are receiving this mail because: You are the assignee for the bug.= --15718931019.dDC18.2092 Date: Thu, 24 Oct 2019 04:58:21 +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 # 121 on bug 10995= 5 from = Mauro Gaspari 
(In reply to blppt from comment #120)
> I dont have anything to attach here, but same is=
sue here, ubuntu 19.04,
> kernel 5.4-rc3, vega64 W/C, Mesa 19.3.0 -- it only seems to occur with=
 DXVK
> and not D9VK for some reason.
>=20
> Example: GW2 (DX9 game) will work perfectly under heavy load in WvW wi=
th
> massive zergs for hours with no crash, but FFXIV (DX11) will always lo=
ck the
> entire system up after a time.
>=20
> That being said, when you force the top clock using
>=20
> echo manual > /sys/class/drm/card0/device/power_dpm_force_performan=
ce_level
>=20
> and
>=20
> echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk
>=20
> FFXIV no longer locks the system at all. It does eat up a good deal mo=
re
> watts according to my UPS meter though, so resetting to auto is necess=
ary
> IMHO.
>=20
> So, it sounds like you guys are on the right track with the whole &quo=
t;power
> management" thing being the culprit. Just wanted to add my experi=
ence to
> this.
>=20
> (and yes, echoing the guy above, the exact same system is stable in wi=
ndows
> 10, so its not a hardware issue).

I agree with this. I am having much better experience myself even without
commands to force the power performance level by doing:
- change game to windowed or full-screen borderless (fixed window)
- disable vsync
- disable frame limiter

by doing the above 3, it seems that GPU is forced into max power state all =
the
time while playing. I have been using this method for a few days with DXVK
games and I had no freeze so far.

But again this is just a temporary workaround. So is the command to manually
force high power performance level. Hopefully a permanent fix comes with
AMDGPU/Kernel updates.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15718931019.dDC18.2092-- --===============1050342244== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1050342244==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 24 Oct 2019 09:09:14 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0267802517==" 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 514206E1BD for ; Thu, 24 Oct 2019 09:09:15 +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 --===============0267802517== Content-Type: multipart/alternative; boundary="15719081555.Fc0406c1.21555" Content-Transfer-Encoding: 7bit --15719081555.Fc0406c1.21555 Date: Thu, 24 Oct 2019 09:09:15 +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=3D109955 --- Comment #122 from haro41@gmx.de --- In my experience, this issue is related to mclk switching and it affects the lowest mclk level only. So you guy's can save a lot of power, if you, insteed of switching to highe= st gfxlevel or to disable vsync, just disable the lowest mclk level by: echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_lev= el echo "1 2 3" > /sys/class/drm/card0/device/pp_dpm_mclk If you are building your kernel locally, look in this thread for a driver c= ode modification that works, without disabling the lowest mclk level (saves a f= ew watt on idle). --=20 You are receiving this mail because: You are the assignee for the bug.= --15719081555.Fc0406c1.21555 Date: Thu, 24 Oct 2019 09:09:15 +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 # 122 on bug 10995= 5 from haro41@gmx.de 
In my experience, this issue is related to mclk switching and =
it affects the
lowest mclk level only.

So you guy's can save a lot of power, if you, insteed of switching to highe=
st
gfxlevel or to disable vsync, just disable the lowest mclk level by:

echo "manual" > /sys/class/drm/card0/device/power_dpm_force_pe=
rformance_level
echo "1 2 3" > /sys/class/drm/card0/device/pp_dpm_mclk

If you are building your kernel locally, look in this thread for a driver c=
ode
modification that works, without disabling the lowest mclk level (saves a f=
ew
watt on idle).

You are receiving this mail because:
  • You are the assignee for the bug.
= --15719081555.Fc0406c1.21555-- --===============0267802517== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0267802517==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 24 Oct 2019 09:10:34 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1731723715==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 70F996E1A4 for ; Thu, 24 Oct 2019 09:10:34 +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 --===============1731723715== Content-Type: multipart/alternative; boundary="15719082342.BEca20704.22816" Content-Transfer-Encoding: 7bit --15719082342.BEca20704.22816 Date: Thu, 24 Oct 2019 09:10:34 +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=3D109955 --- Comment #123 from haro41@gmx.de --- ... i forgot the link to a related thread: https://bugs.freedesktop.org/show_bug.cgi?id=3D110777 --=20 You are receiving this mail because: You are the assignee for the bug.= --15719082342.BEca20704.22816 Date: Thu, 24 Oct 2019 09:10:34 +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

You are receiving this mail because:
  • You are the assignee for the bug.
= --15719082342.BEca20704.22816-- --===============1731723715== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1731723715==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 29 Oct 2019 19:00:25 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0938435068==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id C43CB6E5D1 for ; Tue, 29 Oct 2019 19:00:27 +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 --===============0938435068== Content-Type: multipart/alternative; boundary="15723756276.1DACdf.27528" Content-Transfer-Encoding: 7bit --15723756276.1DACdf.27528 Date: Tue, 29 Oct 2019 19:00:27 +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=3D109955 --- Comment #124 from blppt@yahoo.com --- (In reply to haro41 from comment #122) > In my experience, this issue is related to mclk switching and it affects = the > lowest mclk level only. >=20 > So you guy's can save a lot of power, if you, insteed of switching to > highest gfxlevel or to disable vsync, just disable the lowest mclk level = by: >=20 > echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_l= evel > echo "1 2 3" > /sys/class/drm/card0/device/pp_dpm_mclk >=20 > If you are building your kernel locally, look in this thread for a driver > code modification that works, without disabling the lowest mclk level (sa= ves > a few watt on idle). Ooh, that seems to have solved it. Haven't had a crash yet, ran The Outer Worlds for hours (addicting game!), ran FFXIV, ran GW2, no lockups. And, if there is much of a difference at idle in watt usage, I don't see it on the = UPS meter. Thanks a million! (also of note, when using the valve ACO, as others have noted, you don't ev= en have to do the above to (apparently) solve the problem. unfortunately, that= has other issues, my V64 wont clock up high enough when using ACO for some reas= on, so i dont use it). --=20 You are receiving this mail because: You are the assignee for the bug.= --15723756276.1DACdf.27528 Date: Tue, 29 Oct 2019 19:00:27 +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 # 124 on bug 10995= 5 from blppt@yahoo.com 
(In reply to haro41 from comment #122)
> In my experience, this issue is related to mclk =
switching and it affects the
> lowest mclk level only.
>=20
> So you guy's can save a lot of power, if you, insteed of switching to
> highest gfxlevel or to disable vsync, just disable the lowest mclk lev=
el by:
>=20
> echo "manual" > /sys/class/drm/card0/device/power_dpm_for=
ce_performance_level
> echo "1 2 3" > /sys/class/drm/card0/device/pp_dpm_mclk
>=20
> If you are building your kernel locally, look in this thread for a dri=
ver
> code modification that works, without disabling the lowest mclk level =
(saves
> a few watt on idle).

Ooh, that seems to have solved it. Haven't had a crash yet, ran The Outer
Worlds for hours (addicting game!), ran FFXIV, ran GW2, no lockups. And, if
there is much of a difference at idle in watt usage, I don't see it on the =
UPS
meter.

Thanks a million!

(also of note, when using the valve ACO, as others have noted, you don't ev=
en
have to do the above to (apparently) solve the problem. unfortunately, that=
 has
other issues, my V64 wont clock up high enough when using ACO for some reas=
on,
so i dont use it).

You are receiving this mail because:
  • You are the assignee for the bug.
= --15723756276.1DACdf.27528-- --===============0938435068== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0938435068==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 05 Nov 2019 18:01:08 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0344874924==" 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 B729B6EB43 for ; Tue, 5 Nov 2019 18:01:08 +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 --===============0344874924== Content-Type: multipart/alternative; boundary="15729768686.B8Fd.26158" Content-Transfer-Encoding: 7bit --15729768686.B8Fd.26158 Date: Tue, 5 Nov 2019 18:01:08 +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=3D109955 --- Comment #125 from haro41@gmx.de --- ... thanks for your feedback, so it seems we are faced with the same bug ... Btw, i got crashes with at least one vulkan game and ACO compiler backend enabled too. I think it really depends of the load pattern. And enabled vsync is trigger= ing the typical load pattern, with at least one transient (from high to low loa= d) per frame. Is someone affected with this bug here, usually building the kernel from so= urce locally? --=20 You are receiving this mail because: You are the assignee for the bug.= --15729768686.B8Fd.26158 Date: Tue, 5 Nov 2019 18:01:08 +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 # 125 on bug 10995= 5 from haro41@gmx.de 
... thanks for your feedback, so it seems we are faced with th=
e same bug ...

Btw, i got crashes with at least one vulkan game and ACO compiler backend
enabled too.
I think it really depends of the load pattern. And enabled vsync is trigger=
ing
the typical load pattern, with at least one transient (from high to low loa=
d)
per frame.

Is someone affected with this bug here, usually building the kernel from so=
urce
locally?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15729768686.B8Fd.26158-- --===============0344874924== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0344874924==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 06 Nov 2019 02:46:02 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1750861756==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id D2BF86EBD5 for ; Wed, 6 Nov 2019 02:46:03 +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 --===============1750861756== Content-Type: multipart/alternative; boundary="157300836310.5934f1E.22508" Content-Transfer-Encoding: 7bit --157300836310.5934f1E.22508 Date: Wed, 6 Nov 2019 02:46:03 +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=3D109955 --- Comment #126 from Rodney A Morris --- (In reply to haro41 from comment #125) > ... thanks for your feedback, so it seems we are faced with the same bug = ... >=20 > Btw, i got crashes with at least one vulkan game and ACO compiler backend > enabled too. > I think it really depends of the load pattern. And enabled vsync is > triggering the typical load pattern, with at least one transient (from hi= gh > to low load) per frame. >=20 > Is someone affected with this bug here, usually building the kernel from > source locally? If you want someone to apply your changes in bug report no. 110777 to the kernel for testing, I can so but will not be to it until this weekend.=20 As a side note, I've had great success manually limiting the memory clock to level 1,2,3 on my Vega 64. I've played over 7 hours of Stellaris without a crash. --=20 You are receiving this mail because: You are the assignee for the bug.= --157300836310.5934f1E.22508 Date: Wed, 6 Nov 2019 02:46:03 +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 # 126 on bug 10995= 5 from Rodney A Morris 
(In reply to haro41 from comment #125)
> ... thanks for your feedback, so it seems we are=
 faced with the same bug ...
>=20
> Btw, i got crashes with at least one vulkan game and ACO compiler back=
end
> enabled too.
> I think it really depends of the load pattern. And enabled vsync is
> triggering the typical load pattern, with at least one transient (from=
 high
> to low load) per frame.
>=20
> Is someone affected with this bug here, usually building the kernel fr=
om
> source locally?

If you want someone to apply your changes in bug report no. 110777 to the
kernel for testing, I can so but will not be to it until this weekend.=20

As a side note, I've had great success manually limiting the memory clock to
level 1,2,3 on my Vega 64.  I've played over 7 hours of Stellaris without a
crash.

You are receiving this mail because:
  • You are the assignee for the bug.
= --157300836310.5934f1E.22508-- --===============1750861756== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1750861756==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 06 Nov 2019 09:49:49 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0422265974==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 0F71A6EC91 for ; Wed, 6 Nov 2019 09:49:49 +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 --===============0422265974== Content-Type: multipart/alternative; boundary="15730337890.7Ee330.2955" Content-Transfer-Encoding: 7bit --15730337890.7Ee330.2955 Date: Wed, 6 Nov 2019 09:49:49 +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=3D109955 --- Comment #127 from haro41@gmx.de --- (In reply to Rodney A Morris from comment #126) > If you want someone to apply your changes in bug report no. 110777 to the > kernel for testing, I can so but will not be to it until this weekend.=20 ... thanks for you reply. Yes, that was the idea and would be very nice... Since i thing the proposed fix is more relevant to this very thread, let me repeat the proposed patch here: in 'drivers/gpu/drm/amd/powerplay/hwmgr/vega10_hwmgr.c': static void vega10_notify_smc_display_change(struct pp_hwmgr *hwmgr, bool has_disp) { smum_send_msg_to_smc_with_parameter(hwmgr, PPSMC_MSG_SetUclkFastSwitch, has_disp ? 1 : 0); /* proposed fix for crashes because of frequently mclk level 0/1 switching = */ smum_send_msg_to_smc_with_parameter(hwmgr, PPSMC_MSG_SetUclkDownHys= t, 1); } Only module 'amdgpu.ko' needs to be rebuild and copied, like this: $ cd /home/user/linux-5.x.x && make -j8 -C . M=3Ddrivers/gpu/drm/amd/amdgpu # cp /home/user/linux-5.x.x/drivers/gpu/drm/amd/amdgpu/amdgpu.ko /lib/modules/5.x.x/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko && update-initramfs -u ... 'user' and 'x.x' have to be adapted, most likely ... --=20 You are receiving this mail because: You are the assignee for the bug.= --15730337890.7Ee330.2955 Date: Wed, 6 Nov 2019 09:49:49 +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 # 127 on bug 10995= 5 from haro41@gmx.de 
(In reply to Rodney A Morris from comment #126)
> If you want someone to apply your changes in bug=
 report no. 110777 to the
> kernel for testing, I can so but will not be to it until this weekend.=
 

... thanks for you reply. Yes, that was the idea and would be very nice...

Since i thing the proposed fix is more relevant to this very thread, let me
repeat the proposed patch here:

in 'drivers/gpu/drm/amd/powerplay/hwmgr/vega10_hwmgr.c':

static void vega10_notify_smc_display_change(struct pp_hwmgr *hwmgr,
                bool has_disp)
{
        smum_send_msg_to_smc_with_parameter(hwmgr,
                                            PPSMC_MSG_SetUclkFastSwitch,
                                            has_disp ? 1 : 0);
/* proposed fix for crashes because of frequently mclk level 0/1 switching =
*/
        smum_send_msg_to_smc_with_parameter(hwmgr, PPSMC_MSG_SetUclkDownHys=
t,
1);
}

Only module 'amdgpu.ko' needs to be rebuild and copied, like this:

$ cd /home/user/linux-5.x.x && make -j8 -C . M=3Ddrivers/gpu/drm/am=
d/amdgpu

# cp /home/user/linux-5.x.x/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
/lib/modules/5.x.x/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko &&
update-initramfs -u

... 'user' and 'x.x' have to be adapted, most likely ...

You are receiving this mail because:
  • You are the assignee for the bug.
= --15730337890.7Ee330.2955-- --===============0422265974== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0422265974==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 06 Nov 2019 10:23:39 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0933960504==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id B9DD86ECBA for ; Wed, 6 Nov 2019 10:23:39 +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 --===============0933960504== Content-Type: multipart/alternative; boundary="157303581911.bB185.9526" Content-Transfer-Encoding: 7bit --157303581911.bB185.9526 Date: Wed, 6 Nov 2019 10:23:39 +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=3D109955 --- Comment #128 from haro41@gmx.de --- Created attachment 145901 --> https://bugs.freedesktop.org/attachment.cgi?id=3D145901&action=3Dedit proposed fix for crashes, caused by frequent mclk level 0/1 switches At least one of the causes for crashes, are more frequently, if vsync is enabled.=20 In this case, memory clock levels are switched usually more frequently. By experiments i found, that especially the transient betweeen level 1 and level 0 is critical. The fact, that disabling memory level 0, helps as a workaround, confirms: this approach points in the right direction. Result of further experiments: By sending a 'PPSMC_MSG_SetUclkDownHyst' message to smc (enabling a hystere= se feature ?), the crashes can be avoided, even with enabled mclk level 0 and vsync activated. --=20 You are receiving this mail because: You are the assignee for the bug.= --157303581911.bB185.9526 Date: Wed, 6 Nov 2019 10:23:39 +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 # 128 on bug 10995= 5 from haro41@gmx.de 
Created attachment 145901 [details] [review]
proposed fix for crashes, caused by frequent mclk level 0/1 switches

At least one of the causes for crashes, are more frequently, if vsync is
enabled.=20

In this case, memory clock levels are switched usually more frequently.
By experiments i found, that especially the transient betweeen level 1 and
level 0 is critical. The fact, that disabling memory level 0, helps as a
workaround, confirms: this approach points in the right direction.

Result of further experiments:
By sending a 'PPSMC_MSG_SetUclkDownHyst' message to smc (enabling a hystere=
se
feature ?), the crashes can be avoided, even with enabled mclk level 0 and
vsync activated.

You are receiving this mail because:
  • You are the assignee for the bug.
= --157303581911.bB185.9526-- --===============0933960504== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0933960504==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 06 Nov 2019 17:32:50 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1087314700==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 1976A6EE20 for ; Wed, 6 Nov 2019 17:32:51 +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 --===============1087314700== Content-Type: multipart/alternative; boundary="15730615711.008425.29393" Content-Transfer-Encoding: 7bit --15730615711.008425.29393 Date: Wed, 6 Nov 2019 17:32:51 +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=3D109955 --- Comment #129 from Wilko Bartels --- (In reply to haro41 from comment #122) > In my experience, this issue is related to mclk switching and it affects = the > lowest mclk level only. >=20 > So you guy's can save a lot of power, if you, insteed of switching to > highest gfxlevel or to disable vsync, just disable the lowest mclk level = by: >=20 > echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_l= evel > echo "1 2 3" > /sys/class/drm/card0/device/pp_dpm_mclk >=20 > If you are building your kernel locally, look in this thread for a driver > code modification that works, without disabling the lowest mclk level (sa= ves > a few watt on idle). do you have any suggestion to automate this? so far i can strictly run these commands after su. not even sudo works with scripts running these commands.= or systemd files. --=20 You are receiving this mail because: You are the assignee for the bug.= --15730615711.008425.29393 Date: Wed, 6 Nov 2019 17:32:51 +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 # 129 on bug 10995= 5 from = Wilko Bartels 
(In reply to haro41 from comment #122)
> In my experience, this issue is related to mclk =
switching and it affects the
> lowest mclk level only.
>=20
> So you guy's can save a lot of power, if you, insteed of switching to
> highest gfxlevel or to disable vsync, just disable the lowest mclk lev=
el by:
>=20
> echo "manual" > /sys/class/drm/card0/device/power_dpm_for=
ce_performance_level
> echo "1 2 3" > /sys/class/drm/card0/device/pp_dpm_mclk
>=20
> If you are building your kernel locally, look in this thread for a dri=
ver
> code modification that works, without disabling the lowest mclk level =
(saves
> a few watt on idle).

do you have any suggestion to automate this? so far i can strictly run these
commands after su. not even sudo works with scripts running these commands.=
 or
systemd files.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15730615711.008425.29393-- --===============1087314700== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1087314700==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 06 Nov 2019 18:32:31 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0896081434==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 3DBCF6ECCD for ; Wed, 6 Nov 2019 18:32:32 +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 --===============0896081434== Content-Type: multipart/alternative; boundary="15730651523.aEE9bf.8137" Content-Transfer-Encoding: 7bit --15730651523.aEE9bf.8137 Date: Wed, 6 Nov 2019 18:32:32 +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=3D109955 --- Comment #130 from haro41@gmx.de --- > >=20 > > echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance= _level > > echo "1 2 3" > /sys/class/drm/card0/device/pp_dpm_mclk > >=20 >=20 > do you have any suggestion to automate this? so far i can strictly run th= ese > commands after su. not even sudo works with scripts running these command= s. > or systemd files. Currently i use my patch (see above) to workaround the crashes. If you prefer not to touch your kernel, you could create a systemd service:= =20 # cat /etc/systemd/system/amd-pp.service:=20 [Unit] Description=3DAMD PP adjust service [Service] User=3Droot Group=3Droot GuessMainPID=3Dno ExecStart=3D/srv/amdgpu-pp.sh [Install] WantedBy=3Dmulti-user.target --------------------------------------------------------------- # cat /srv/amdgpu-pp.sh: #!/bin/bash echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_lev= el echo "1 2 3" > /sys/class/drm/card0/device/pp_dpm_mclk --------------------------------------------------------------- #systemctl enable amd-pp.service #systemctl start amd-pp.service --------------------------------------------------------------- ... assuming you have 'amdgpu.ppfeaturemask=3D0xffffffff' set ... --=20 You are receiving this mail because: You are the assignee for the bug.= --15730651523.aEE9bf.8137 Date: Wed, 6 Nov 2019 18:32:32 +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 # 130 on bug 10995= 5 from haro41@gmx.de 
> >=20
> > echo "manual" > /sys/class/drm/card0/device/power_dp=
m_force_performance_level
> > echo "1 2 3" > /sys/class/drm/card0/device/pp_dpm_mc=
lk
> >=20
>=20
> do you have any suggestion to automate this? so far i can strictly run=
 these
> commands after su. not even sudo works with scripts running these comm=
ands.
> or systemd files.

Currently i use my patch (see above) to workaround the crashes.
If you prefer not to touch your kernel, you could create a systemd service:=
=20

# cat /etc/systemd/system/amd-pp.service:=20

[Unit]
Description=3DAMD PP adjust service
[Service]
User=3Droot
Group=3Droot
GuessMainPID=3Dno
ExecStart=3D/srv/amdgpu-pp.sh
[Install]
WantedBy=3Dmulti-user.target
---------------------------------------------------------------
# cat /srv/amdgpu-pp.sh:

#!/bin/bash
echo "manual" > /sys/class/drm/card0/device/power_dpm_force_pe=
rformance_level
echo "1 2 3" > /sys/class/drm/card0/device/pp_dpm_mclk
---------------------------------------------------------------
#systemctl enable amd-pp.service
#systemctl start amd-pp.service
---------------------------------------------------------------

... assuming you have 'amdgpu.ppfeaturemask=3D0xffffffff' set ...

You are receiving this mail because:
  • You are the assignee for the bug.
= --15730651523.aEE9bf.8137-- --===============0896081434== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0896081434==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Wed, 06 Nov 2019 19:26:11 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0493811637==" 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 001D56EE2A for ; Wed, 6 Nov 2019 19:26:11 +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 --===============0493811637== Content-Type: multipart/alternative; boundary="157306837111.4eADc.19882" Content-Transfer-Encoding: 7bit --157306837111.4eADc.19882 Date: Wed, 6 Nov 2019 19:26:11 +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=3D109955 --- Comment #131 from Wilko Bartels --- (In reply to haro41 from comment #130) > > >=20 > > > echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performan= ce_level > > > echo "1 2 3" > /sys/class/drm/card0/device/pp_dpm_mclk > > >=20 > >=20 > > do you have any suggestion to automate this? so far i can strictly run = these > > commands after su. not even sudo works with scripts running these comma= nds. > > or systemd files. >=20 > Currently i use my patch (see above) to workaround the crashes. > If you prefer not to touch your kernel, you could create a systemd servic= e:=20 >=20 > # cat /etc/systemd/system/amd-pp.service:=20 >=20 > [Unit] > Description=3DAMD PP adjust service > [Service] > User=3Droot > Group=3Droot > GuessMainPID=3Dno > ExecStart=3D/srv/amdgpu-pp.sh > [Install] > WantedBy=3Dmulti-user.target > --------------------------------------------------------------- > # cat /srv/amdgpu-pp.sh: >=20 > #!/bin/bash > echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_l= evel > echo "1 2 3" > /sys/class/drm/card0/device/pp_dpm_mclk > --------------------------------------------------------------- > #systemctl enable amd-pp.service > #systemctl start amd-pp.service > --------------------------------------------------------------- >=20 > ... assuming you have 'amdgpu.ppfeaturemask=3D0xffffffff' set ... Thank you. I already tried exactly that. And the unit unable to autostart (permission denied). Only manual systemctl start works. Dont know why.=20 I would try to patch the kernel instead if i had any clue how to do the ste= ps. --=20 You are receiving this mail because: You are the assignee for the bug.= --157306837111.4eADc.19882 Date: Wed, 6 Nov 2019 19:26:11 +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 # 131 on bug 10995= 5 from = Wilko Bartels 
(In reply to haro41 from comment #130)
> > >=20
> > > echo "manual" > /sys/class/drm/card0/device/pow=
er_dpm_force_performance_level
> > > echo "1 2 3" > /sys/class/drm/card0/device/pp_d=
pm_mclk
> > >=20
> >=20
> > do you have any suggestion to automate this? so far i can strictl=
y run these
> > commands after su. not even sudo works with scripts running these=
 commands.
> > or systemd files.
>=20
> Currently i use my patch (see above) to workaround the crashes.
> If you prefer not to touch your kernel, you could create a systemd ser=
vice:=20
>=20
> # cat /etc/systemd/system/amd-pp.service:=20
>=20
> [Unit]
> Description=3DAMD PP adjust service
> [Service]
> User=3Droot
> Group=3Droot
> GuessMainPID=3Dno
> ExecStart=3D/srv/amdgpu-pp.sh
> [Install]
> WantedBy=3Dmulti-user.target
> ---------------------------------------------------------------
> # cat /srv/amdgpu-pp.sh:
>=20
> #!/bin/bash
> echo "manual" > /sys/class/drm/card0/device/power_dpm_for=
ce_performance_level
> echo "1 2 3" > /sys/class/drm/card0/device/pp_dpm_mclk
> ---------------------------------------------------------------
> #systemctl enable amd-pp.service
> #systemctl start amd-pp.service
> ---------------------------------------------------------------
>=20
> ... assuming you have 'amdgpu.ppfeaturemask=3D0xffffffff' set ...

Thank you. I already tried exactly that. And the unit unable to autostart
(permission denied). Only manual systemctl start works. Dont know why.=20

I would try to patch the kernel instead if i had any clue how to do the ste=
ps.

You are receiving this mail because:
  • You are the assignee for the bug.
= --157306837111.4eADc.19882-- --===============0493811637== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0493811637==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 07 Nov 2019 10:25:58 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1840517743==" 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 670716F5A1 for ; Thu, 7 Nov 2019 10:25:58 +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 --===============1840517743== Content-Type: multipart/alternative; boundary="15731223586.A193.1744" Content-Transfer-Encoding: 7bit --15731223586.A193.1744 Date: Thu, 7 Nov 2019 10:25:58 +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=3D109955 --- Comment #132 from haro41@gmx.de --- (In reply to Wilko Bartels from comment #131) > Thank you. I already tried exactly that. And the unit unable to autostart > (permission denied). Only manual systemctl start works. Dont know why.=20 If you double checked the permissions of both, the .service and the .sh fil= es, you could try delay the automatic service start, for example by replacing: 'WantedBy=3Dmulti-user.target' with 'WantedBy=3Dgraphical.target' and maybe insert a line in the [Unit] section: 'After=3Dmulti-user.target' --=20 You are receiving this mail because: You are the assignee for the bug.= --15731223586.A193.1744 Date: Thu, 7 Nov 2019 10:25:58 +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 # 132 on bug 10995= 5 from haro41@gmx.de 
(In reply to Wilko Bartels from comment #131)
> Thank you. I already tried exactly that. And the=
 unit unable to autostart
> (permission denied). Only manual systemctl start works. Dont know why.=
 

If you double checked the permissions of both, the .service and the .sh fil=
es,
you could try delay the automatic service start, for example by replacing:

'WantedBy=3Dmulti-user.target' with 'WantedBy=3Dgraphical.target'

and maybe insert a line in the [Unit] section: 'After=3Dmulti-user.target'<=
/pre>

You are receiving this mail because:
  • You are the assignee for the bug.
= --15731223586.A193.1744-- --===============1840517743== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1840517743==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Thu, 07 Nov 2019 16:50:10 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1156723184==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 8CC9A6F74E for ; Thu, 7 Nov 2019 16:50:10 +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 --===============1156723184== Content-Type: multipart/alternative; boundary="15731454105.DfEd164.30551" Content-Transfer-Encoding: 7bit --15731454105.DfEd164.30551 Date: Thu, 7 Nov 2019 16:50:10 +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=3D109955 --- Comment #133 from Wilko Bartels --- (In reply to haro41 from comment #132) > (In reply to Wilko Bartels from comment #131) > > Thank you. I already tried exactly that. And the unit unable to autosta= rt > > (permission denied). Only manual systemctl start works. Dont know why.= =20 >=20 > If you double checked the permissions of both, the .service and the .sh > files, > you could try delay the automatic service start, for example by replacing: >=20 > 'WantedBy=3Dmulti-user.target' with 'WantedBy=3Dgraphical.target' >=20 > and maybe insert a line in the [Unit] section: 'After=3Dmulti-user.target' sadly that doesnt change a thing line 2: /sys/class/drm/card0/device/power_dpm_force_performance_level: Permission denied line 3: /sys/class/drm/card0/device/pp_dpm_mclk: Permission denied amd-pp.service: Main process exited, code=3Dexited, status=3D1/FAILURE -rw-r--r-- 1 root root 4,0K 7. Nov 17:45 /sys/class/drm/card0/device/power_dpm_force_performance_level -rw-r--r-- 1 root root 4,0K 7. Nov 17:45 /sys/class/drm/card0/device/pp_dpm_mclk again after logging (i3/xinit or plasma/sddm i have no errors with systemctl start and it works [jason@behemoth ~]$ cat /sys/class/drm/card0/device/pp_dpm_mclk 0: 167Mhz=20 1: 500Mhz * 2: 700Mhz=20 3: 800Mhz --=20 You are receiving this mail because: You are the assignee for the bug.= --15731454105.DfEd164.30551 Date: Thu, 7 Nov 2019 16:50:10 +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 # 133 on bug 10995= 5 from = Wilko Bartels 
(In reply to haro41 from comment #132)
> (In reply to Wilko Bartels from comment #131)
> > Thank you. I already tried exactly that. And the unit unable to a=
utostart
> > (permission denied). Only manual systemctl start works. Dont know=
 why.=20
>=20
> If you double checked the permissions of both, the .service and the .sh
> files,
> you could try delay the automatic service start, for example by replac=
ing:
>=20
> 'WantedBy=3Dmulti-user.target' with 'WantedBy=3Dgraphical.target'
>=20
> and maybe insert a line in the [Unit] section: 'After=3Dmulti-user.tar=
get'

sadly that doesnt change a thing
line 2: /sys/class/drm/card0/device/power_dpm_force_performance_level:
Permission denied

line 3: /sys/class/drm/card0/device/pp_dpm_mclk: Permission denied
amd-pp.service: Main process exited, code=3Dexited, status=3D1/FAILURE

-rw-r--r-- 1 root root 4,0K  7. Nov 17:45
/sys/class/drm/card0/device/power_dpm_force_performance_level

-rw-r--r-- 1 root root 4,0K  7. Nov 17:45
/sys/class/drm/card0/device/pp_dpm_mclk

again after logging (i3/xinit or plasma/sddm i have no errors with systemctl
start and it works

[jason@behemoth ~]$ cat /sys/class/drm/card0/device/pp_dpm_mclk
0: 167Mhz=20
1: 500Mhz *
2: 700Mhz=20
3: 800Mhz

You are receiving this mail because:
  • You are the assignee for the bug.
= --15731454105.DfEd164.30551-- --===============1156723184== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1156723184==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Tue, 12 Nov 2019 11:03:54 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0903644302==" 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 689596E22A for ; Tue, 12 Nov 2019 11:03:54 +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 --===============0903644302== Content-Type: multipart/alternative; boundary="15735566340.205EbEBA.27870" Content-Transfer-Encoding: 7bit --15735566340.205EbEBA.27870 Date: Tue, 12 Nov 2019 11:03:54 +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=3D109955 --- Comment #134 from Wilko Bartels --- (In reply to Wilko Bartels from comment #133) > (In reply to haro41 from comment #132) > > (In reply to Wilko Bartels from comment #131) > > > Thank you. I already tried exactly that. And the unit unable to autos= tart > > > (permission denied). Only manual systemctl start works. Dont know why= .=20 > >=20 > > If you double checked the permissions of both, the .service and the .sh > > files, > > you could try delay the automatic service start, for example by replaci= ng: > >=20 > > 'WantedBy=3Dmulti-user.target' with 'WantedBy=3Dgraphical.target' > >=20 > > and maybe insert a line in the [Unit] section: 'After=3Dmulti-user.targ= et' >=20 > sadly that doesnt change a thing > line 2: /sys/class/drm/card0/device/power_dpm_force_performance_level: > Permission denied >=20 > line 3: /sys/class/drm/card0/device/pp_dpm_mclk: Permission denied > amd-pp.service: Main process exited, code=3Dexited, status=3D1/FAILURE >=20 > -rw-r--r-- 1 root root 4,0K 7. Nov 17:45 > /sys/class/drm/card0/device/power_dpm_force_performance_level >=20 > -rw-r--r-- 1 root root 4,0K 7. Nov 17:45 > /sys/class/drm/card0/device/pp_dpm_mclk >=20 > again after logging (i3/xinit or plasma/sddm i have no errors with system= ctl > start and it works >=20 > [jason@behemoth ~]$ cat /sys/class/drm/card0/device/pp_dpm_mclk > 0: 167Mhz=20 > 1: 500Mhz * > 2: 700Mhz=20 > 3: 800Mhz running a script at plasma login now. with no password for that command in sudoers. also after sleep. --=20 You are receiving this mail because: You are the assignee for the bug.= --15735566340.205EbEBA.27870 Date: Tue, 12 Nov 2019 11:03:54 +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 # 134 on bug 10995= 5 from = Wilko Bartels 
(In reply to Wilko Bartels from comment #133)
> (In reply to haro41 from comment #132)
> > (In reply to Wilko Bartels from comment #131)
> > > Thank you. I already tried exactly that. And the unit unable=
 to autostart
> > > (permission denied). Only manual systemctl start works. Dont=
 know why.=20
> >=20
> > If you double checked the permissions of both, the .service and t=
he .sh
> > files,
> > you could try delay the automatic service start, for example by r=
eplacing:
> >=20
> > 'WantedBy=3Dmulti-user.target' with 'WantedBy=3Dgraphical.target'
> >=20
> > and maybe insert a line in the [Unit] section: 'After=3Dmulti-use=
r.target'
>=20
> sadly that doesnt change a thing
> line 2: /sys/class/drm/card0/device/power_dpm_force_performance_level:
> Permission denied
>=20
> line 3: /sys/class/drm/card0/device/pp_dpm_mclk: Permission denied
> amd-pp.service: Main process exited, code=3Dexited, status=3D1/FAILURE
>=20
> -rw-r--r-- 1 root root 4,0K  7. Nov 17:45
> /sys/class/drm/card0/device/power_dpm_force_performance_level
>=20
> -rw-r--r-- 1 root root 4,0K  7. Nov 17:45
> /sys/class/drm/card0/device/pp_dpm_mclk
>=20
> again after logging (i3/xinit or plasma/sddm i have no errors with sys=
temctl
> start and it works
>=20
> [jason@behemoth ~]$ cat /sys/class/drm/card0/device/pp_dpm_mclk
> 0: 167Mhz=20
> 1: 500Mhz *
> 2: 700Mhz=20
> 3: 800Mhz

running a script at plasma login now. with no password for that command in
sudoers. also after sleep.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15735566340.205EbEBA.27870-- --===============0903644302== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0903644302==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 17 Nov 2019 14:24:39 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0792946836==" 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 EA75389FD9 for ; Sun, 17 Nov 2019 14:24:39 +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 --===============0792946836== Content-Type: multipart/alternative; boundary="15740006793.f0F24F.25556" Content-Transfer-Encoding: 7bit --15740006793.f0F24F.25556 Date: Sun, 17 Nov 2019 14:24:39 +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=3D109955 --- Comment #135 from Rodney A Morris --- (In reply to haro41 from comment #127) > (In reply to Rodney A Morris from comment #126) > > If you want someone to apply your changes in bug report no. 110777 to t= he > > kernel for testing, I can so but will not be to it until this weekend.= =20 >=20=20 > ... thanks for you reply. Yes, that was the idea and would be very nice... >=20 > Since i thing the proposed fix is more relevant to this very thread, let = me > repeat the proposed patch here: >=20 > in 'drivers/gpu/drm/amd/powerplay/hwmgr/vega10_hwmgr.c': >=20 > static void vega10_notify_smc_display_change(struct pp_hwmgr *hwmgr, > bool has_disp) > { > smum_send_msg_to_smc_with_parameter(hwmgr, > PPSMC_MSG_SetUclkFastSwitch, > has_disp ? 1 : 0); > /* proposed fix for crashes because of frequently mclk level 0/1 switchin= g */ > smum_send_msg_to_smc_with_parameter(hwmgr, PPSMC_MSG_SetUclkDownHyst, 1); > } >=20 > Only module 'amdgpu.ko' needs to be rebuild and copied, like this: >=20 > $ cd /home/user/linux-5.x.x && make -j8 -C . M=3Ddrivers/gpu/drm/amd/amdg= pu >=20 > # cp /home/user/linux-5.x.x/drivers/gpu/drm/amd/amdgpu/amdgpu.ko > /lib/modules/5.x.x/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko && > update-initramfs -u >=20 > ... 'user' and 'x.x' have to be adapted, most likely ... I applied the patch and recompiled the kernel with the modified amdgpu driv= er.=20 Unfortunately, the patch did not resolve my issues. I experienced a crash = with the same symptoms as before within 20 minutes of playing Battletech and wit= hin 40 minutes of playing Stellaris. Again, limiting the HMB memory clock to levels 1,2, and 3 prevents the system from crashing, indicating that someth= ing with the switching of the memory clock between level 0 and 1, 2, and 3 are causing the crash. Interestingly, the debug output indicates a possible problem in amdgpu/../display/dc/dc_helper.c at, I am guessing, line 332. If I have ti= me later this week, I may take a look at the code in that file. Here are the pertinent details from the Stellaris crash. Distro: Fedora Kernel: 5.3.11 dmesg crash output: [19792.781681] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D3875204, emitted seq=3D3875205 [19792.781727] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati= on: process stellaris pid 13309 thread stellaris:cs0 pid 13310 [19792.781731] amdgpu 0000:06:00.0: GPU reset begin! [19792.798997] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19792.799004] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19792.799006] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19792.799007] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19792.800004] pcieport 0000:00:03.0: AER: Device recovery failed [19794.419525] amdgpu: [powerplay] No response from smu [19794.419542] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x= 0, error code: 0x0 [19796.043441] amdgpu: [powerplay] No response from smu [19797.665903] amdgpu: [powerplay] No response from smu [19797.665907] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0= x1, error code: 0x0 [19799.287749] amdgpu: [powerplay] No response from smu [19800.910845] amdgpu: [powerplay] No response from smu [19800.910850] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0= x0, error code: 0x0 [19800.977846] [drm] REG_WAIT timeout 10us * 3500 tries - dce_mi_free_dmif line:634 [19800.977855] ------------[ cut here ]------------ [19800.977967] WARNING: CPU: 10 PID: 15123 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:332 generic_reg_wait.cold+0x31/0x53 [amdgpu] [19800.977968] Modules linked in: rfcomm xt_CHECKSUM xt_MASQUERADE nf_nat_t= ftp nf_conntrack_tftp tun bridge stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_= nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter cmac bnep nct6775 hwmon_vid vfat = fat intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp core= temp kvm_intel kvm iTCO_wdt iTCO_vendor_support irqbypass iwlmvm crct10dif_pclmul snd_hda_codec_realtek crc32_pclmul snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi ghash_clmulni_intel mac80211 snd_hda_intel intel_cstate snd_hda_codec libarc4 intel_uncore snd_hda_core btusb snd_hwdep btrtl intel_rapl_perf btbcm iwlwifi snd_seq btintel snd_seq_device [19800.977994] bluetooth joydev mxm_wmi snd_pcm cfg80211 snd_timer ecdh_generic ecc rfkill snd mei_me soundcore i2c_i801 lpc_ich mei binfmt_mi= sc auth_rpcgss sunrpc ip_tables amdgpu amd_iommu_v2 gpu_sched ttm drm_kms_help= er drm crc32c_intel mpt3sas igb nvme e1000e dca raid_class i2c_algo_bit scsi_transport_sas nvme_core wmi usb_storage fuse [19800.978009] CPU: 10 PID: 15123 Comm: kworker/10:1 Not tainted 5.3.11-300.RAM.local.fc31.x86_64+debug #1 [19800.978011] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M.= /X99 Taichi, BIOS P1.80 04/06/2018 [19800.978014] Workqueue: events drm_sched_job_timedout [gpu_sched] [19800.978082] RIP: 0010:generic_reg_wait.cold+0x31/0x53 [amdgpu] [19800.978084] Code: 4c 24 18 44 89 fa 89 ee 48 c7 c7 a8 ee 7e c0 e8 82 00 = a5 fa 83 7b 20 01 0f 84 94 ee fd ff 48 c7 c7 a0 ed 7e c0 e8 6c 00 a5 fa <0f> 0= b e9 81 ee fd ff 48 c7 c7 a0 ed 7e c0 89 54 24 04 e8 55 00 a5 [19800.978086] RSP: 0018:ffff957a0520f690 EFLAGS: 00010246 [19800.978087] RAX: 0000000000000024 RBX: ffff88d6a8030780 RCX: 0000000000000006 [19800.978089] RDX: 0000000000000000 RSI: ffff88d645a10e50 RDI: ffff88d6bf9d9e00 [19800.978090] RBP: 000000000000000a R08: 0000120246405906 R09: 0000000000000000 [19800.978091] R10: 0000000000000000 R11: 0000000000000000 R12: 00000000000035af [19800.978092] R13: 0000000000000dad R14: 0000000000000001 R15: 0000000000000dac [19800.978093] FS: 0000000000000000(0000) GS:ffff88d6bf800000(0000) knlGS:0000000000000000 [19800.978095] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [19800.978096] CR2: 0000289e30054000 CR3: 0000000278612003 CR4: 00000000003606e0 [19800.978097] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [19800.978098] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [19800.978100] Call Trace: [19800.978152] dce_mi_free_dmif+0xef/0x150 [amdgpu] [19800.978200] dce110_reset_hw_ctx_wrap+0x15f/0x200 [amdgpu] [19800.978261] dce110_apply_ctx_to_hw+0x4b/0x530 [amdgpu] [19800.978316] ? amdgpu_pm_compute_clocks+0xc9/0x5f0 [amdgpu] [19800.978383] ? dm_pp_apply_display_requirements+0x1a8/0x1c0 [amdgpu] [19800.978429] dc_commit_state+0x26b/0x590 [amdgpu] [19800.978479] amdgpu_dm_atomic_commit_tail+0xd18/0x1cf0 [amdgpu] [19800.978486] ? check_irq_usage+0xa7/0x460 [19800.978488] ? find_held_lock+0x32/0x90 [19800.978494] ? check_path+0x22/0x40 [19800.978496] ? check_noncircular+0xaf/0x1b0 [19800.978501] ? __lock_acquire+0x247/0x1910 [19800.978507] ? find_held_lock+0x32/0x90 [19800.978511] ? mark_held_locks+0x50/0x80 [19800.978513] ? _raw_spin_unlock_irq+0x29/0x40 [19800.978516] ? lockdep_hardirqs_on+0xf0/0x180 [19800.978518] ? _raw_spin_unlock_irq+0x29/0x40 [19800.978521] ? wait_for_completion_timeout+0x75/0x190 [19800.978534] ? commit_tail+0x3c/0x70 [drm_kms_helper] [19800.978578] ? amdgpu_dm_audio_eld_notify+0x60/0x60 [amdgpu] [19800.978583] commit_tail+0x3c/0x70 [drm_kms_helper] [19800.978588] drm_atomic_helper_commit+0xe3/0x150 [drm_kms_helper] [19800.978595] drm_atomic_helper_disable_all+0x14c/0x160 [drm_kms_helper] [19800.978601] drm_atomic_helper_suspend+0x66/0x100 [drm_kms_helper] [19800.978652] dm_suspend+0x20/0x60 [amdgpu] [19800.978679] amdgpu_device_ip_suspend_phase1+0x91/0xc0 [amdgpu] [19800.978707] amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu] [19800.978753] amdgpu_device_pre_asic_reset+0x191/0x1a4 [amdgpu] [19800.978799] amdgpu_device_gpu_recover+0x260/0x934 [amdgpu] [19800.978843] amdgpu_job_timedout+0x115/0x140 [amdgpu] [19800.978848] drm_sched_job_timedout+0x44/0xa0 [gpu_sched] [19800.978852] process_one_work+0x272/0x5a0 [19800.978858] worker_thread+0x50/0x3b0 [19800.978863] kthread+0x108/0x140 [19800.978865] ? process_one_work+0x5a0/0x5a0 [19800.978867] ? kthread_park+0x80/0x80 [19800.978870] ret_from_fork+0x3a/0x50 [19800.978878] irq event stamp: 211500 [19800.978881] hardirqs last enabled at (211499): [] console_unlock+0x46b/0x5d0 [19800.978885] hardirqs last disabled at (211500): [] trace_hardirqs_off_thunk+0x1a/0x20 [19800.978887] softirqs last enabled at (211486): [] __do_softirq+0x35d/0x45d [19800.978889] softirqs last disabled at (211479): [] irq_exit+0xf7/0x100 [19800.978891] ---[ end trace 722d34fe8b4d4012 ]--- [19802.595549] amdgpu: [powerplay] No response from smu [19804.214995] amdgpu: [powerplay] No response from smu [19804.215000] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0= x1, error code: 0x0 [19805.837985] amdgpu: [powerplay] No response from smu [19807.458610] amdgpu: [powerplay] No response from smu [19807.458614] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0= x3, error code: 0x0 [19809.078189] amdgpu: [powerplay] No response from smu [19810.698831] amdgpu: [powerplay] No response from smu [19810.698835] amdgpu: [powerplay] Failed message: 0x9, input parameter: 0x= f4, error code: 0x0 [19812.321202] amdgpu: [powerplay] No response from smu [19813.938039] amdgpu: [powerplay] No response from smu [19813.938043] amdgpu: [powerplay] Failed message: 0xa, input parameter: 0xa0b000, error code: 0x0 [19815.558461] amdgpu: [powerplay] No response from smu [19817.179965] amdgpu: [powerplay] No response from smu [19817.179969] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x= 0, error code: 0x0 [19818.790507] amdgpu: [powerplay] No response from smu [19820.409551] amdgpu: [powerplay] No response from smu [19820.409555] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0= x1, error code: 0x0 [19822.030397] amdgpu: [powerplay] No response from smu [19823.648860] amdgpu: [powerplay] No response from smu [19823.648864] amdgpu: [powerplay] Failed message: 0x43, input parameter: 0= x1, error code: 0x0 [19825.269615] amdgpu: [powerplay] No response from smu [19826.890755] amdgpu: [powerplay] No response from smu [19826.890760] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0= x0, error code: 0x0 [19826.907783] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19826.907789] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19826.907791] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19826.907793] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19826.907853] pcieport 0000:00:03.0: AER: Device recovery failed [19826.925319] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19826.925325] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19826.925326] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19826.925328] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19826.925371] pcieport 0000:00:03.0: AER: Device recovery failed [19826.942858] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19826.942863] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19826.942865] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19826.942867] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19826.942922] pcieport 0000:00:03.0: AER: Device recovery failed [19826.960471] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19826.960477] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19826.960480] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19826.960483] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19826.960532] pcieport 0000:00:03.0: AER: Device recovery failed [19826.977940] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19826.977945] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19826.977947] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19826.977949] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19826.977988] pcieport 0000:00:03.0: AER: Device recovery failed [19826.995481] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19826.995486] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19826.995487] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19826.995489] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19826.995529] pcieport 0000:00:03.0: AER: Device recovery failed [19827.013021] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.013026] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.013027] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.013029] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.013091] pcieport 0000:00:03.0: AER: Device recovery failed [19827.030562] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.030567] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.030568] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.030570] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.030610] pcieport 0000:00:03.0: AER: Device recovery failed [19827.048102] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.048106] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.048108] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.048110] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.048148] pcieport 0000:00:03.0: AER: Device recovery failed [19827.065644] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.065648] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.065650] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.065652] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.065692] pcieport 0000:00:03.0: AER: Device recovery failed [19827.083183] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.083188] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.083190] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.083192] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.083231] pcieport 0000:00:03.0: AER: Device recovery failed [19827.100724] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.100729] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.100731] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.100732] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.100772] pcieport 0000:00:03.0: AER: Device recovery failed [19827.118264] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.118269] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.118270] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.118272] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.118310] pcieport 0000:00:03.0: AER: Device recovery failed [19827.135804] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.135809] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.135811] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.135812] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.135852] pcieport 0000:00:03.0: AER: Device recovery failed [19827.153345] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.153350] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.153352] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.153353] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.153393] pcieport 0000:00:03.0: AER: Device recovery failed [19827.170887] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.170892] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.170893] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.170895] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.170934] pcieport 0000:00:03.0: AER: Device recovery failed [19827.188426] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.188431] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.188433] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.188435] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.188473] pcieport 0000:00:03.0: AER: Device recovery failed [19827.205966] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.205971] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.205973] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.205974] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.206013] pcieport 0000:00:03.0: AER: Device recovery failed [19827.223507] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.223512] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.223514] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.223515] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.223554] pcieport 0000:00:03.0: AER: Device recovery failed [19827.241053] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.241058] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.241059] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.241061] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.241120] pcieport 0000:00:03.0: AER: Device recovery failed [19827.258589] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.258594] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.258595] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.258597] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.258637] pcieport 0000:00:03.0: AER: Device recovery failed [19827.276129] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.276134] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.276135] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.276137] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.276176] pcieport 0000:00:03.0: AER: Device recovery failed [19827.293670] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.293675] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.293676] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.293678] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.293718] pcieport 0000:00:03.0: AER: Device recovery failed [19827.311211] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.311215] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.311217] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.311219] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.311259] pcieport 0000:00:03.0: AER: Device recovery failed [19827.328751] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.328756] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.328758] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.328759] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.328800] pcieport 0000:00:03.0: AER: Device recovery failed [19827.346291] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.346295] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.346297] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.346299] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.346344] pcieport 0000:00:03.0: AER: Device recovery failed [19827.363831] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.363836] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.363838] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.363839] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.363886] pcieport 0000:00:03.0: AER: Device recovery failed [19827.381372] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.381376] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.381378] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.381380] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.381425] pcieport 0000:00:03.0: AER: Device recovery failed [19827.398913] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.398917] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.398919] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.398921] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.398959] pcieport 0000:00:03.0: AER: Device recovery failed [19827.416453] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.416458] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.416460] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.416467] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.416507] pcieport 0000:00:03.0: AER: Device recovery failed [19827.433994] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.433999] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.434001] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.434002] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.434042] pcieport 0000:00:03.0: AER: Device recovery failed [19827.451536] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.451542] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.451544] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.451545] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.451588] pcieport 0000:00:03.0: AER: Device recovery failed [19827.469085] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.469091] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.469092] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.469094] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.469136] pcieport 0000:00:03.0: AER: Device recovery failed [19827.486616] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.486626] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.486628] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.486630] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.486670] pcieport 0000:00:03.0: AER: Device recovery failed [19827.504161] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.504167] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.504170] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.504171] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.504218] pcieport 0000:00:03.0: AER: Device recovery failed [19827.521697] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.521702] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.521704] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.521706] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.521934] pcieport 0000:00:03.0: AER: Device recovery failed [19827.539242] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.539247] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.539249] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.539250] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.539290] pcieport 0000:00:03.0: AER: Device recovery failed [19827.556778] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.556782] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.556784] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.556786] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.556836] pcieport 0000:00:03.0: AER: Device recovery failed [19827.574325] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.574330] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.574332] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.574334] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.574373] pcieport 0000:00:03.0: AER: Device recovery failed [19827.591858] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.591863] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.591865] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.591867] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.591908] pcieport 0000:00:03.0: AER: Device recovery failed [19827.609401] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.609405] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.609407] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.609409] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.609448] pcieport 0000:00:03.0: AER: Device recovery failed [19827.626939] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.626944] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.626946] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.626947] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.626986] pcieport 0000:00:03.0: AER: Device recovery failed [19827.644481] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.644486] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.644488] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.644489] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.644528] pcieport 0000:00:03.0: AER: Device recovery failed [19827.662021] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.662026] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.662028] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.662029] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.662087] pcieport 0000:00:03.0: AER: Device recovery failed [19827.679561] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.679566] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.679568] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.679570] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.679608] pcieport 0000:00:03.0: AER: Device recovery failed [19827.697101] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.697106] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.697108] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.697110] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.697149] pcieport 0000:00:03.0: AER: Device recovery failed [19827.714648] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.714653] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.714655] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.714656] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.714703] pcieport 0000:00:03.0: AER: Device recovery failed [19827.732183] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.732188] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.732190] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.732191] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.732230] pcieport 0000:00:03.0: AER: Device recovery failed [19827.749724] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.749729] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.749730] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.749732] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.767327] pcieport 0000:00:03.0: AER: Device recovery failed [19827.767330] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.767335] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.767336] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.767338] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.767364] pcieport 0000:00:03.0: AER: Device recovery failed [19827.784805] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.784810] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.784812] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.784813] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.784853] pcieport 0000:00:03.0: AER: Device recovery failed [19827.802345] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.802350] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.802352] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.802354] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.802394] pcieport 0000:00:03.0: AER: Device recovery failed [19827.819886] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.0 [19827.819891] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor= rected (Non-Fatal), type=3DTransaction Layer, (Requester ID) [19827.819893] pcieport 0000:00:03.0: AER: device [8086:6f08] error status/mask=3D00004000/00000000 [19827.819894] pcieport 0000:00:03.0: AER: [14] CmpltTO=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 (First) [19827.819934] pcieport 0000:00:03.0: AER: Device recovery failed --=20 You are receiving this mail because: You are the assignee for the bug.= --15740006793.f0F24F.25556 Date: Sun, 17 Nov 2019 14:24:39 +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 # 135 on bug 10995= 5 from Rodney A Morris 
(In reply to haro41 from comment #127)
> (In reply to Rodney A Morris from comment #126)
> > If you want someone to apply your changes in bug report no. 11077=
7 to the
> > kernel for testing, I can so but will not be to it until this wee=
kend.=20
>=20=20
> ... thanks for you reply. Yes, that was the idea and would be very nic=
e...
>=20
> Since i thing the proposed fix is more relevant to this very thread, l=
et me
> repeat the proposed patch here:
>=20
> in 'drivers/gpu/drm/amd/powerplay/hwmgr/vega10_hwmgr.c':
>=20
> static void vega10_notify_smc_display_change(struct pp_hwmgr *hwmgr,
>                 bool has_disp)
> {
> 	smum_send_msg_to_smc_with_parameter(hwmgr,
> 	                                    PPSMC_MSG_SetUclkFastSwitch,
> 	                                    has_disp ? 1 : 0);
> /* proposed fix for crashes because of frequently mclk level 0/1 switc=
hing */
> 	smum_send_msg_to_smc_with_parameter(hwmgr, PPSMC_MSG_SetUclkDownHyst,=
 1);
> }
>=20
> Only module 'amdgpu.ko' needs to be rebuild and copied, like this:
>=20
> $ cd /home/user/linux-5.x.x && make -j8 -C . M=3Ddrivers/gpu/d=
rm/amd/amdgpu
>=20
> # cp /home/user/linux-5.x.x/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
> /lib/modules/5.x.x/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko &&a=
mp;
> update-initramfs -u
>=20
> ... 'user' and 'x.x' have to be adapted, most likely ...

I applied the patch and recompiled the kernel with the modified amdgpu driv=
er.=20
Unfortunately, the patch did not resolve my issues.  I experienced a crash =
with
the same symptoms as before within 20 minutes of playing Battletech and wit=
hin
40 minutes of playing Stellaris.  Again, limiting the HMB memory clock to
levels 1,2, and 3 prevents the system from crashing, indicating that someth=
ing
with the switching of the memory clock between level 0 and 1, 2, and 3 are
causing the crash.

Interestingly, the debug output indicates a possible problem in
amdgpu/../display/dc/dc_helper.c at, I am guessing, line 332.  If I have ti=
me
later this week, I may take a look at the code in that file.  Here are the
pertinent details from the Stellaris crash.

Distro:  Fedora
Kernel:  5.3.11

dmesg crash output:

[19792.781681] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=3D3875204, emitted seq=3D3875205
[19792.781727] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process informati=
on:
process stellaris pid 13309 thread stellaris:cs0 pid 13310
[19792.781731] amdgpu 0000:06:00.0: GPU reset begin!
[19792.798997] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19792.799004] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19792.799006] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19792.799007] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19792.800004] pcieport 0000:00:03.0: AER: Device recovery failed
[19794.419525] amdgpu: [powerplay] No response from smu
[19794.419542] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x=
0,
error code: 0x0
[19796.043441] amdgpu: [powerplay] No response from smu
[19797.665903] amdgpu: [powerplay] No response from smu
[19797.665907] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0=
x1,
error code: 0x0
[19799.287749] amdgpu: [powerplay] No response from smu
[19800.910845] amdgpu: [powerplay] No response from smu
[19800.910850] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0=
x0,
error code: 0x0
[19800.977846] [drm] REG_WAIT timeout 10us * 3500 tries - dce_mi_free_dmif
line:634
[19800.977855] ------------[ cut here ]------------
[19800.977967] WARNING: CPU: 10 PID: 15123 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:332
generic_reg_wait.cold+0x31/0x53 [amdgpu]
[19800.977968] Modules linked in: rfcomm xt_CHECKSUM xt_MASQUERADE nf_nat_t=
ftp
nf_conntrack_tftp tun bridge stp llc nf_conntrack_netbios_ns
nf_conntrack_broadcast xt_CT ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter
ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_=
nat
ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat
iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6
nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables
ip6table_filter ip6_tables iptable_filter cmac bnep nct6775 hwmon_vid vfat =
fat
intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp core=
temp
kvm_intel kvm iTCO_wdt iTCO_vendor_support irqbypass iwlmvm crct10dif_pclmul
snd_hda_codec_realtek crc32_pclmul snd_hda_codec_generic ledtrig_audio
snd_hda_codec_hdmi ghash_clmulni_intel mac80211 snd_hda_intel intel_cstate
snd_hda_codec libarc4 intel_uncore snd_hda_core btusb snd_hwdep btrtl
intel_rapl_perf btbcm iwlwifi snd_seq btintel snd_seq_device
[19800.977994]  bluetooth joydev mxm_wmi snd_pcm cfg80211 snd_timer
ecdh_generic ecc rfkill snd mei_me soundcore i2c_i801 lpc_ich mei binfmt_mi=
sc
auth_rpcgss sunrpc ip_tables amdgpu amd_iommu_v2 gpu_sched ttm drm_kms_help=
er
drm crc32c_intel mpt3sas igb nvme e1000e dca raid_class i2c_algo_bit
scsi_transport_sas nvme_core wmi usb_storage fuse
[19800.978009] CPU: 10 PID: 15123 Comm: kworker/10:1 Not tainted
5.3.11-300.RAM.local.fc31.x86_64+debug #1
[19800.978011] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M.=
/X99
Taichi, BIOS P1.80 04/06/2018
[19800.978014] Workqueue: events drm_sched_job_timedout [gpu_sched]
[19800.978082] RIP: 0010:generic_reg_wait.cold+0x31/0x53 [amdgpu]
[19800.978084] Code: 4c 24 18 44 89 fa 89 ee 48 c7 c7 a8 ee 7e c0 e8 82 00 =
a5
fa 83 7b 20 01 0f 84 94 ee fd ff 48 c7 c7 a0 ed 7e c0 e8 6c 00 a5 fa <0f=
> 0b e9
81 ee fd ff 48 c7 c7 a0 ed 7e c0 89 54 24 04 e8 55 00 a5
[19800.978086] RSP: 0018:ffff957a0520f690 EFLAGS: 00010246
[19800.978087] RAX: 0000000000000024 RBX: ffff88d6a8030780 RCX:
0000000000000006
[19800.978089] RDX: 0000000000000000 RSI: ffff88d645a10e50 RDI:
ffff88d6bf9d9e00
[19800.978090] RBP: 000000000000000a R08: 0000120246405906 R09:
0000000000000000
[19800.978091] R10: 0000000000000000 R11: 0000000000000000 R12:
00000000000035af
[19800.978092] R13: 0000000000000dad R14: 0000000000000001 R15:
0000000000000dac
[19800.978093] FS:  0000000000000000(0000) GS:ffff88d6bf800000(0000)
knlGS:0000000000000000
[19800.978095] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[19800.978096] CR2: 0000289e30054000 CR3: 0000000278612003 CR4:
00000000003606e0
[19800.978097] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[19800.978098] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
0000000000000400
[19800.978100] Call Trace:
[19800.978152]  dce_mi_free_dmif+0xef/0x150 [amdgpu]
[19800.978200]  dce110_reset_hw_ctx_wrap+0x15f/0x200 [amdgpu]
[19800.978261]  dce110_apply_ctx_to_hw+0x4b/0x530 [amdgpu]
[19800.978316]  ? amdgpu_pm_compute_clocks+0xc9/0x5f0 [amdgpu]
[19800.978383]  ? dm_pp_apply_display_requirements+0x1a8/0x1c0 [amdgpu]
[19800.978429]  dc_commit_state+0x26b/0x590 [amdgpu]
[19800.978479]  amdgpu_dm_atomic_commit_tail+0xd18/0x1cf0 [amdgpu]
[19800.978486]  ? check_irq_usage+0xa7/0x460
[19800.978488]  ? find_held_lock+0x32/0x90
[19800.978494]  ? check_path+0x22/0x40
[19800.978496]  ? check_noncircular+0xaf/0x1b0
[19800.978501]  ? __lock_acquire+0x247/0x1910
[19800.978507]  ? find_held_lock+0x32/0x90
[19800.978511]  ? mark_held_locks+0x50/0x80
[19800.978513]  ? _raw_spin_unlock_irq+0x29/0x40
[19800.978516]  ? lockdep_hardirqs_on+0xf0/0x180
[19800.978518]  ? _raw_spin_unlock_irq+0x29/0x40
[19800.978521]  ? wait_for_completion_timeout+0x75/0x190
[19800.978534]  ? commit_tail+0x3c/0x70 [drm_kms_helper]
[19800.978578]  ? amdgpu_dm_audio_eld_notify+0x60/0x60 [amdgpu]
[19800.978583]  commit_tail+0x3c/0x70 [drm_kms_helper]
[19800.978588]  drm_atomic_helper_commit+0xe3/0x150 [drm_kms_helper]
[19800.978595]  drm_atomic_helper_disable_all+0x14c/0x160 [drm_kms_helper]
[19800.978601]  drm_atomic_helper_suspend+0x66/0x100 [drm_kms_helper]
[19800.978652]  dm_suspend+0x20/0x60 [amdgpu]
[19800.978679]  amdgpu_device_ip_suspend_phase1+0x91/0xc0 [amdgpu]
[19800.978707]  amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu]
[19800.978753]  amdgpu_device_pre_asic_reset+0x191/0x1a4 [amdgpu]
[19800.978799]  amdgpu_device_gpu_recover+0x260/0x934 [amdgpu]
[19800.978843]  amdgpu_job_timedout+0x115/0x140 [amdgpu]
[19800.978848]  drm_sched_job_timedout+0x44/0xa0 [gpu_sched]
[19800.978852]  process_one_work+0x272/0x5a0
[19800.978858]  worker_thread+0x50/0x3b0
[19800.978863]  kthread+0x108/0x140
[19800.978865]  ? process_one_work+0x5a0/0x5a0
[19800.978867]  ? kthread_park+0x80/0x80
[19800.978870]  ret_from_fork+0x3a/0x50
[19800.978878] irq event stamp: 211500
[19800.978881] hardirqs last  enabled at (211499): [<ffffffffbb1715db>=
;]
console_unlock+0x46b/0x5d0
[19800.978885] hardirqs last disabled at (211500): [<ffffffffbb0038da>=
;]
trace_hardirqs_off_thunk+0x1a/0x20
[19800.978887] softirqs last  enabled at (211486): [<ffffffffbbe0035d>=
;]
__do_softirq+0x35d/0x45d
[19800.978889] softirqs last disabled at (211479): [<ffffffffbb0f20c7>=
;]
irq_exit+0xf7/0x100
[19800.978891] ---[ end trace 722d34fe8b4d4012 ]---
[19802.595549] amdgpu: [powerplay] No response from smu
[19804.214995] amdgpu: [powerplay] No response from smu
[19804.215000] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0=
x1,
error code: 0x0
[19805.837985] amdgpu: [powerplay] No response from smu
[19807.458610] amdgpu: [powerplay] No response from smu
[19807.458614] amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0=
x3,
error code: 0x0
[19809.078189] amdgpu: [powerplay] No response from smu
[19810.698831] amdgpu: [powerplay] No response from smu
[19810.698835] amdgpu: [powerplay] Failed message: 0x9, input parameter: 0x=
f4,
error code: 0x0
[19812.321202] amdgpu: [powerplay] No response from smu
[19813.938039] amdgpu: [powerplay] No response from smu
[19813.938043] amdgpu: [powerplay] Failed message: 0xa, input parameter:
0xa0b000, error code: 0x0
[19815.558461] amdgpu: [powerplay] No response from smu
[19817.179965] amdgpu: [powerplay] No response from smu
[19817.179969] amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x=
0,
error code: 0x0
[19818.790507] amdgpu: [powerplay] No response from smu
[19820.409551] amdgpu: [powerplay] No response from smu
[19820.409555] amdgpu: [powerplay] Failed message: 0x42, input parameter: 0=
x1,
error code: 0x0
[19822.030397] amdgpu: [powerplay] No response from smu
[19823.648860] amdgpu: [powerplay] No response from smu
[19823.648864] amdgpu: [powerplay] Failed message: 0x43, input parameter: 0=
x1,
error code: 0x0
[19825.269615] amdgpu: [powerplay] No response from smu
[19826.890755] amdgpu: [powerplay] No response from smu
[19826.890760] amdgpu: [powerplay] Failed message: 0x24, input parameter: 0=
x0,
error code: 0x0
[19826.907783] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19826.907789] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19826.907791] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19826.907793] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19826.907853] pcieport 0000:00:03.0: AER: Device recovery failed
[19826.925319] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19826.925325] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19826.925326] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19826.925328] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19826.925371] pcieport 0000:00:03.0: AER: Device recovery failed
[19826.942858] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19826.942863] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19826.942865] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19826.942867] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19826.942922] pcieport 0000:00:03.0: AER: Device recovery failed
[19826.960471] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19826.960477] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19826.960480] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19826.960483] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19826.960532] pcieport 0000:00:03.0: AER: Device recovery failed
[19826.977940] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19826.977945] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19826.977947] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19826.977949] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19826.977988] pcieport 0000:00:03.0: AER: Device recovery failed
[19826.995481] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19826.995486] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19826.995487] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19826.995489] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19826.995529] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.013021] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.013026] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.013027] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.013029] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.013091] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.030562] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.030567] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.030568] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.030570] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.030610] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.048102] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.048106] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.048108] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.048110] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.048148] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.065644] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.065648] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.065650] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.065652] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.065692] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.083183] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.083188] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.083190] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.083192] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.083231] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.100724] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.100729] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.100731] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.100732] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.100772] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.118264] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.118269] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.118270] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.118272] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.118310] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.135804] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.135809] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.135811] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.135812] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.135852] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.153345] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.153350] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.153352] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.153353] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.153393] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.170887] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.170892] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.170893] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.170895] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.170934] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.188426] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.188431] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.188433] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.188435] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.188473] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.205966] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.205971] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.205973] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.205974] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.206013] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.223507] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.223512] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.223514] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.223515] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.223554] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.241053] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.241058] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.241059] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.241061] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.241120] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.258589] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.258594] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.258595] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.258597] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.258637] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.276129] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.276134] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.276135] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.276137] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.276176] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.293670] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.293675] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.293676] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.293678] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.293718] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.311211] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.311215] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.311217] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.311219] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.311259] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.328751] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.328756] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.328758] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.328759] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.328800] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.346291] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.346295] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.346297] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.346299] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.346344] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.363831] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.363836] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.363838] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.363839] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.363886] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.381372] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.381376] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.381378] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.381380] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.381425] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.398913] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.398917] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.398919] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.398921] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.398959] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.416453] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.416458] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.416460] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.416467] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.416507] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.433994] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.433999] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.434001] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.434002] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.434042] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.451536] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.451542] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.451544] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.451545] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.451588] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.469085] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.469091] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.469092] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.469094] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.469136] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.486616] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.486626] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.486628] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.486630] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.486670] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.504161] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.504167] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.504170] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.504171] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.504218] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.521697] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.521702] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.521704] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.521706] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.521934] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.539242] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.539247] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.539249] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.539250] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.539290] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.556778] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.556782] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.556784] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.556786] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.556836] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.574325] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.574330] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.574332] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.574334] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.574373] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.591858] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.591863] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.591865] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.591867] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.591908] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.609401] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.609405] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.609407] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.609409] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.609448] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.626939] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.626944] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.626946] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.626947] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.626986] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.644481] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.644486] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.644488] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.644489] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.644528] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.662021] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.662026] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.662028] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.662029] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.662087] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.679561] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.679566] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.679568] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.679570] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.679608] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.697101] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.697106] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.697108] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.697110] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.697149] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.714648] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.714653] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.714655] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.714656] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.714703] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.732183] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.732188] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.732190] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.732191] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.732230] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.749724] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.749729] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.749730] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.749732] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.767327] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.767330] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.767335] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.767336] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.767338] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.767364] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.784805] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.784810] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.784812] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.784813] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.784853] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.802345] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.802350] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.802352] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.802354] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.802394] pcieport 0000:00:03.0: AER: Device recovery failed
[19827.819886] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error
received: 0000:00:03.0
[19827.819891] pcieport 0000:00:03.0: AER: PCIe Bus Error: severity=3DUncor=
rected
(Non-Fatal), type=3DTransaction Layer, (Requester ID)
[19827.819893] pcieport 0000:00:03.0: AER:   device [8086:6f08] error
status/mask=3D00004000/00000000
[19827.819894] pcieport 0000:00:03.0: AER:    [14] CmpltTO=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
(First)
[19827.819934] pcieport 0000:00:03.0: AER: Device recovery failed

You are receiving this mail because:
  • You are the assignee for the bug.
= --15740006793.f0F24F.25556-- --===============0792946836== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0792946836==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming Date: Sun, 17 Nov 2019 17:13:10 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1074173369==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 4CAE76E2DC for ; Sun, 17 Nov 2019 17:13:11 +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 --===============1074173369== Content-Type: multipart/alternative; boundary="15740107913.1D47AD9.24932" Content-Transfer-Encoding: 7bit --15740107913.1D47AD9.24932 Date: Sun, 17 Nov 2019 17:13:11 +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=3D109955 --- Comment #136 from haro41@gmx.de --- Thank you for testing and reporting back. I think the crashes are caused by voltage drops, followed by a hardware failure. That would explain the many different kernel logs too, because from the dri= vers pow, it is randomly. If vsync is enabled, mclk level is switched at least twice per frame (down/= up). And in some cases i have seen more switches inside a frame.=20 I am not sure, if this fast memory clock level switching, multiple times du= ring a frame really useful? It saves not much power, but makes the system instab= le, apparently. I don't think this is wanted behavior, it looks more like a firmware bug, i= mo. Maybe an opensource driver developer can help us to understand? --=20 You are receiving this mail because: You are the assignee for the bug.= --15740107913.1D47AD9.24932 Date: Sun, 17 Nov 2019 17:13:11 +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 # 136 on bug 10995= 5 from haro41@gmx.de 
Thank you for testing and reporting back.

I think the crashes are caused by voltage drops, followed by a hardware
failure.
That would explain the many different kernel logs too, because from the dri=
vers
pow, it is randomly.

If vsync is enabled, mclk level is switched at least twice per frame (down/=
up).
And in some cases i have seen more switches inside a frame.=20

I am not sure, if this fast memory clock level switching, multiple times du=
ring
a frame really useful? It saves not much power, but makes the system instab=
le,
apparently.

I don't think this is wanted behavior, it looks more like a firmware bug, i=
mo.

Maybe an opensource driver developer can help us to understand?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15740107913.1D47AD9.24932-- --===============1074173369== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1074173369==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming (VSYNC enabled) Date: Sun, 17 Nov 2019 17:18:11 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1378130599==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 8B21B6E12B for ; Sun, 17 Nov 2019 17:18:11 +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 --===============1378130599== Content-Type: multipart/alternative; boundary="15740110918.acdCdeFc8.26264" Content-Transfer-Encoding: 7bit --15740110918.acdCdeFc8.26264 Date: Sun, 17 Nov 2019 17:18:11 +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=3D109955 haro41@gmx.de changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|amdgpu [RX Vega 64] system |amdgpu [RX Vega 64] system |freeze while gaming |freeze while gaming (VSYNC | |enabled) --=20 You are receiving this mail because: You are the assignee for the bug.= --15740110918.acdCdeFc8.26264 Date: Sun, 17 Nov 2019 17:18:11 +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 haro41@gmx.de changed bug 10995= 5
What Removed Added
Summary amdgpu [RX Vega 64] system freeze while gaming amdgpu [RX Vega 64] system freeze while gaming (VSYNC enable= d)

You are receiving this mail because:
  • You are the assignee for the bug.
= --15740110918.acdCdeFc8.26264-- --===============1378130599== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1378130599==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming (VSYNC enabled) Date: Wed, 20 Nov 2019 07:52:11 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2091215348==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 913C96E235 for ; Wed, 20 Nov 2019 07:52:12 +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 --===============2091215348== Content-Type: multipart/alternative; boundary="15742363327.625dFDa2.2006" Content-Transfer-Encoding: 7bit --15742363327.625dFDa2.2006 Date: Wed, 20 Nov 2019 07:52:12 +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=3D109955 Martin Peres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED --- Comment #137 from Martin Peres --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/716. --=20 You are receiving this mail because: You are the assignee for the bug.= --15742363327.625dFDa2.2006 Date: Wed, 20 Nov 2019 07:52:12 +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 <= span class=3D"fn">Martin Peres changed bug 10995= 5
What Removed Added
Status NEW RESOLVED
Resolution --- MOVED

Comm= ent # 137 on bug 10995= 5 from Martin Peres 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this =
link
to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/716.

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