From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 110674] Crashes / Resets From AMDGPU / Radeon VII Date: Sat, 03 Aug 2019 12:10:10 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0365902920==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 52F126E4B3 for ; Sat, 3 Aug 2019 12: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 --===============0365902920== Content-Type: multipart/alternative; boundary="15648342113.CEd271.15390" Content-Transfer-Encoding: 7bit --15648342113.CEd271.15390 Date: Sat, 3 Aug 2019 12:10: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=3D110674 --- Comment #58 from Peter Hercek --- It is probably not related to changes from 5.0 to 5.1. I have got the hang up with 5.0.13 as well as with 4.20.11. It may be only less common with older kernels. In my case, it is triggered mostly by playing a video stream in parallel wi= th some other activity. My logs with 5.1 and 5.2 kernels look just like Chris' log. First amdgpu_job_timedout, then an attempt to reset gpu followed by endless stream of parser initialization failures. I did not check the logs with older kernels but it all looked the same at t= he user level. The video subsystem is hung up. The rest of the machine (e.g. an ssh session) work ok. My /sys/class/hwmon/hwmon1/power1_average reported normal values around 25W after hang up. I'm not seeing unusually high power values like Tom B. --=20 You are receiving this mail because: You are the assignee for the bug.= --15648342113.CEd271.15390 Date: Sat, 3 Aug 2019 12: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 # 58 on bug 11067= 4 from Peter Hercek
It is probably not related to changes from 5.0 to 5.1.
I have got the hang up with 5.0.13 as well as with 4.20.11.
It may be only less common with older kernels.

In my case, it is triggered mostly by playing a video stream in parallel wi=
th
some other activity. My logs with 5.1 and 5.2 kernels look just like Chris'
log. First amdgpu_job_timedout, then an attempt to reset gpu followed by
endless stream of parser initialization failures.

I did not check the logs with older kernels but it all looked the same at t=
he
user level. The video subsystem is hung up. The rest of the machine (e.g. an
ssh session) work ok.

My /sys/class/hwmon/hwmon1/power1_average reported normal values around 25W
after hang up. I'm not seeing unusually high power values like Tom B.


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