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: Mon, 12 Aug 2019 15:56:32 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0148548089==" 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 EF2516E563 for ; Mon, 12 Aug 2019 15:56: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 --===============0148548089== Content-Type: multipart/alternative; boundary="15656253911.Ebb022b.14995" Content-Transfer-Encoding: 7bit --15656253911.Ebb022b.14995 Date: Mon, 12 Aug 2019 15:56: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=3D110674 --- Comment #85 from Tom B --- > Yeah. I've had boots where I have my 2 4K DP monitors in and I don't get = powerplay error on boot. In fact, it can go a bit and seem stable. In addition to that, vega20_set_fclk_to_highest_dpm_level is called several times before the card is initialized and even on 5.2.7 works. Something hap= pens during or just before the initialization stage that stops smum_send_msg_to_smc_with_parameter accepting 1001 as a valid value, as it = does until that point. I think you're right about BACO, it was worth looking at but I applied a qu= ick hack to ensure it's disabled: int vega20_baco_set_state(struct pp_hwmgr *hwmgr, enum BACO_STATE state) { return 0; } int vega20_baco_get_capability(struct pp_hwmgr *hwmgr, bool *cap) { *cap =3D false; return 0; } No difference, I still get the errors and wrong wattage so unless BACO is somehow on by default and only turned off in the proper version of this cod= e, we can rule it out. --=20 You are receiving this mail because: You are the assignee for the bug.= --15656253911.Ebb022b.14995 Date: Mon, 12 Aug 2019 15:56: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 # 85 on bug 11067= 4 from Tom = B 
> Yeah. I've had boots where I have my 2 4K DP mon=
itors in and I don't get powerplay error on boot. In fact, it can go a bit =
and seem stable.

In addition to that, vega20_set_fclk_to_highest_dpm_level is called several
times before the card is initialized and even on 5.2.7 works. Something hap=
pens
during or just before the initialization stage that stops
smum_send_msg_to_smc_with_parameter accepting 1001 as a valid value, as it =
does
until that point.

I think you're right about BACO, it was worth looking at but I applied a qu=
ick
hack to ensure it's disabled:

int vega20_baco_set_state(struct pp_hwmgr *hwmgr, enum BACO_STATE state)
{
        return 0;
}

int vega20_baco_get_capability(struct pp_hwmgr *hwmgr, bool *cap)
{
    *cap =3D false;
    return 0;
}

No difference, I still get the errors and wrong wattage so unless BACO is
somehow on by default and only turned off in the proper version of this cod=
e,
we can rule it out.

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