From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state Date: Tue, 22 Nov 2016 21:33:00 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0751516611==" 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 599116E069 for ; Tue, 22 Nov 2016 21:33: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 --===============0751516611== Content-Type: multipart/alternative; boundary="14798503800.4aca2a.13543"; charset="UTF-8" --14798503800.4aca2a.13543 Date: Tue, 22 Nov 2016 21:33: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=3D98821 --- Comment #5 from Alex Deucher --- Can you clarify the behavior you are seeing as per my questions in comment = 1?=20 Is it possible this failure is just random? I don't see why drm/amdgpu:impl vgt_flush for VI(V5) would have any affect on mclk at all. It's just adding some additional synchronization packets that mesa may already submit today. The following are likely the reason the mclk is getting stuck. [ 1.570820]=20 failed to send message 5e ret is 0=20 [ 1.953147]=20 failed to send pre message 145 ret is 0=20 Please use /sys/kernel/debug/dri/64/amdgpu_pm_info to verify the clocks at runtime rather than the files in sysfs. --=20 You are receiving this mail because: You are the assignee for the bug.= --14798503800.4aca2a.13543 Date: Tue, 22 Nov 2016 21:33: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

Comment= # 5 on bug 98821<= /a> from Alex Deucher 
Can you clarify the behavior you are seeing as per my question=
s in comment 1?=20
Is it possible this failure is just random?  I don't see why
drm/amdgpu:impl vgt_flush for VI(V5)
would have any affect on mclk at all.  It's just adding some additional
synchronization packets that mesa may already submit today.

The following are likely the reason the mclk is getting stuck.
[    1.570820]=20
                failed to send message 5e ret is 0=20
[    1.953147]=20
                failed to send pre message 145 ret is 0=20

Please use /sys/kernel/debug/dri/64/amdgpu_pm_info to verify the clocks at
runtime rather than the files in sysfs.

You are receiving this mail because:
  • You are the assignee for the bug.
= --14798503800.4aca2a.13543-- --===============0751516611== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0751516611==--