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: Wed, 31 Jul 2019 17:13:24 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0655948752==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 4027D6E17F for ; Wed, 31 Jul 2019 17:13:24 +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 --===============0655948752== Content-Type: multipart/alternative; boundary="15645932043.CCc2013c7.3333" Content-Transfer-Encoding: 7bit --15645932043.CCc2013c7.3333 Date: Wed, 31 Jul 2019 17:13: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=3D110674 --- Comment #57 from Tom B --- 5.0.13 works fine, I've been using it since I first encountered the problem. 5.1+ introduces this issue. The way to tell whether it's working correctly is to run sensors and check = the power1 number. The bug causes the GPU to be stuck in a high power state (fo= r me 135w) where in previous kernels it idles at 23w. Alternatively run cat /sys/kernel/debug/dri/0/amdgpu_pm_info which will show the same thing, it will be stuck at 1.1v/135w and the clocks will be maxed rather that clocked down when idle. --=20 You are receiving this mail because: You are the assignee for the bug.= --15645932043.CCc2013c7.3333 Date: Wed, 31 Jul 2019 17:13:24 +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 11067= 4 from Tom = B 
5.0.13 works fine, I've been using it since I first encountere=
d the problem.
5.1+ introduces this issue.

The way to tell whether it's working correctly is to run sensors and check =
the
power1 number. The bug causes the GPU to be stuck in a high power state (fo=
r me
135w) where in previous kernels it idles at 23w.

Alternatively run cat /sys/kernel/debug/dri/0/amdgpu_pm_info which will show
the same thing, it will be stuck at 1.1v/135w and the clocks will be maxed
rather that clocked down when idle.

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