From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 100443] DMESG: [powerplay] Can't find requested voltage id in vdd_dep_on_sclk table! Date: Mon, 03 Apr 2017 14:34:33 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1063343238==" 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 BB0596E1A0 for ; Mon, 3 Apr 2017 14:34: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 --===============1063343238== Content-Type: multipart/alternative; boundary="14912300720.29E1f70.15880"; charset="UTF-8" --14912300720.29E1f70.15880 Date: Mon, 3 Apr 2017 14:34: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=3D100443 --- Comment #3 from Christian Lanig --- I have looked a bit around for the cause of these messages. In the first ca= se I guess I found a reason: /*Driver went offline but SMU was still alive and contains the VFT table */ in line 340 in polaris10_smumgr.c In case of the second message in line 575 in hwmgr.c the driver searches for the maximum leakage voltage I guess, where the virtual voltage ID can have values between 0xFF01 - 0xFF08, probably kind of representing the power sta= tes ATOM_VIRTUAL_VOLTAGE_ID0 - ATOM_VIRTUAL_VOLTAGE_ID7. But it doesn't find the specific voltage value in the table so instead of setting the value of the *sclk destination it prints the assertion. That's = kind of my interpretation. Unfortunately the rest is too intricate for me. The messages disappeared with an R9 290X. The RX 480-BIOS can be downloaded here: https://www.techpowerup.com/vgabios/184548/xfx-rx480-8192-160614 --=20 You are receiving this mail because: You are the assignee for the bug.= --14912300720.29E1f70.15880 Date: Mon, 3 Apr 2017 14:34: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

Commen= t # 3 on bug 10044= 3 from Christian Lanig 
I have looked a bit around for the cause of these messages. In=
 the first case I
guess I found a reason:
/*Driver went offline but SMU was still alive and contains the VFT table */
in line 340 in polaris10_smumgr.c

In case of the second message in line 575 in hwmgr.c the driver searches for
the maximum leakage voltage I guess, where the virtual voltage ID can have
values between 0xFF01 - 0xFF08, probably kind of representing the power sta=
tes
ATOM_VIRTUAL_VOLTAGE_ID0 - ATOM_VIRTUAL_VOLTAGE_ID7.

But it doesn't find the specific voltage value in the table so instead of
setting the value of the *sclk destination it prints the assertion. That's =
kind
of my interpretation.
Unfortunately the rest is too intricate for me.

The messages disappeared with an R9 290X.

The RX 480-BIOS can be downloaded here:
https://www.techpowerup.com/vgabios/184548/xfx-rx480-8192-160614

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