From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 112234] [REGRESSION] navi10: writing to pp_table fails (5.4-rc6 = working) Date: Fri, 08 Nov 2019 16:47:01 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0292409010==" 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 CED306FA0C for ; Fri, 8 Nov 2019 16:47:01 +0000 (UTC) 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 --===============0292409010== Content-Type: multipart/alternative; boundary="15732316211.5131e25.26350" Content-Transfer-Encoding: 7bit --15732316211.5131e25.26350 Date: Fri, 8 Nov 2019 16:47:01 +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=3D112234 Bug ID: 112234 Summary: [REGRESSION] navi10: writing to pp_table fails (5.4-rc6 =3D working) Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: not set Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: mcoffin13@gmail.com Created attachment 145913 --> https://bugs.freedesktop.org/attachment.cgi?id=3D145913&action=3Dedit dmesg log (journalctl -k) for the failure. On 5.4-rc6, with navi10, writing to the sysfs pp_table works, with the SMU resetting successfully. On amd-staging-drm-next (270209307880ec946cfe9b98a6a58d285dbc5a2e), this fa= ils. I can bisect, but unfortunately I'm not too sure on where to start, since t= he amd-staging-drm-next branch is currently rebased off of an older version (5.3-rcX I think?). Tips on where to start would be helpful and appreciated, but my guess that this would be introduced in the big refactor to remove the swSMU code layer. --=20 You are receiving this mail because: You are the assignee for the bug.= --15732316211.5131e25.26350 Date: Fri, 8 Nov 2019 16:47:01 +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
Bug ID 112234
Summary [REGRESSION] navi10: writing to pp_table fails (5.4-rc6 =3D w= orking)
Product DRI
Version unspecified
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority not set
Component DRM/AMDgpu
Assignee dri-devel@lists.freedesktop.org
Reporter mcoffin13@gmail.com 

Created attachment 145913 [details]=

dmesg log (journalctl -k) for the failure.

On 5.4-rc6, with navi10, writing to the sysfs pp_table works, with the SMU
resetting successfully.

On amd-staging-drm-next (270209307880ec946cfe9b98a6a58d285dbc5a2e), this fa=
ils.
I can bisect, but unfortunately I'm not too sure on where to start, since t=
he
amd-staging-drm-next branch is currently rebased off of an older version
(5.3-rcX I think?). Tips on where to start would be helpful and appreciated,
but my guess that this would be introduced in the big refactor to remove the
swSMU code layer.

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