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: Tue, 13 Aug 2019 03:15:19 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1474207070==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 45AF66E61F for ; Tue, 13 Aug 2019 03:15:19 +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 --===============1474207070== Content-Type: multipart/alternative; boundary="15656661193.EAAfeC.32767" Content-Transfer-Encoding: 7bit --15656661193.EAAfeC.32767 Date: Tue, 13 Aug 2019 03:15:19 +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 #92 from ReddestDream --- >If you follow the callstack: I've been thinking all this over. The only thing unfortunately that really sticks out at me still is how Chris Hodapp says that reverting this commit: https://github.com/torvalds/linux/commit/d1a3e239a6016f2bb42a91696056e22398= 2e8538#diff-0bc07842bc28283d64ffa6dd2ed716de Seems to improve things. Considering that we now know from Tom B.'s work th= at dpm_state.hard_min_level is apparently calculated correctly and stable the entire time, it doesn't make sense that reverting this commit could fix anything.=20 The code seems very similar to what we see in vega20_notify_smc_display_config_after_ps_adjustment near where we get the " [SetHardMinFreq] Set hard min uclk failed!" Maybe this smum_send_msg_to_smc_with_parameter get through where others fail because of the formatting or something? Thanks again Tom B. for all your testing. I'd like to do some tests of my o= wn, but time's just not permitting for me ATM. Hoping to be more free next week= end. :/ --=20 You are receiving this mail because: You are the assignee for the bug.= --15656661193.EAAfeC.32767 Date: Tue, 13 Aug 2019 03:15:19 +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 # 92 on bug 11067= 4 from ReddestDream 
>If you follow the callstack:

I've been thinking all this over. The only thing unfortunately that really
sticks out at me still is how Chris Hodapp says that reverting this commit:

https://github.com=
/torvalds/linux/commit/d1a3e239a6016f2bb42a91696056e223982e8538#diff-0bc078=
42bc28283d64ffa6dd2ed716de

Seems to improve things. Considering that we now know from Tom B.'s work th=
at
dpm_state.hard_min_level is apparently calculated correctly and stable the
entire time, it doesn't make sense that reverting this commit could fix
anything.=20

The code seems very similar to what we see in
vega20_notify_smc_display_config_after_ps_adjustment near where we get the =
"
[SetHardMinFreq] Set hard min uclk failed!" Maybe this
smum_send_msg_to_smc_with_parameter get through where others fail because of
the formatting or something?

Thanks again Tom B. for all your testing. I'd like to do some tests of my o=
wn,
but time's just not permitting for me ATM. Hoping to be more free next week=
end.
:/

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