From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105324] R9 285 weston hangs since drm/amd/pp: Fix bug that dpm level was not really locked Date: Fri, 02 Mar 2018 09:57:20 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0311501169==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 9878F6EE7E for ; Fri, 2 Mar 2018 09:57:20 +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 --===============0311501169== Content-Type: multipart/alternative; boundary="15199846400.8af7.26220" Content-Transfer-Encoding: 7bit --15199846400.8af7.26220 Date: Fri, 2 Mar 2018 09:57:20 +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=3D105324 Bug ID: 105324 Summary: R9 285 weston hangs since drm/amd/pp: Fix bug that dpm level was not really locked Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: adf.lists@gmail.com R9 285 Tonga, testing with amdgpu.dc=3D0 on agd5f 4.17-wip Since commit a02497b73218f10f237d98fb10d34d0baed607a0 Author: Rex Zhu Date: Fri Feb 9 16:47:53 2018 +0800 drm/amd/pp: Fix bug that dpm level was not really locked Lock the dpm levels when we use SW method to modify the dpm tables directly to avoid a possible race with the smu. weston may hang display on start/quit/vt switch SysRq works and logged will be errors like - Mar 2 00:19:03 ph4 kernel: amdgpu: [powerplay]=20 Mar 2 00:19:03 ph4 kernel: failed to send message 18b ret is 0=20 Mar 2 00:19:03 ph4 kernel: amdgpu: [powerplay]=20 Mar 2 00:19:03 ph4 kernel: failed to send pre message 18a ret is 0=20 Mar 2 00:19:04 ph4 kernel: amdgpu: [powerplay]=20 Mar 2 00:19:04 ph4 kernel: failed to send message 18a ret is 0=20 Mar 2 00:19:04 ph4 kernel: amdgpu: [powerplay]=20 Mar 2 00:19:04 ph4 kernel: failed to send pre message 18c ret is 0=20 Mar 2 00:19:04 ph4 kernel: amdgpu: [powerplay]=20 Mar 2 00:19:04 ph4 kernel: failed to send message 18c ret is 0=20 Mar 2 00:19:05 ph4 kernel: amdgpu: [powerplay]=20 Mar 2 00:19:05 ph4 kernel: failed to send pre message 145 ret is 0=20 Mar 2 00:19:05 ph4 kernel: amdgpu: [powerplay]=20 Mar 2 00:19:05 ph4 kernel: failed to send message 145 ret is 0=20 Mar 2 00:19:06 ph4 kernel: amdgpu: [powerplay]=20 Mar 2 00:19:06 ph4 kernel: failed to send pre message 146 ret is 0=20 Mar 2 00:19:06 ph4 kernel: amdgpu: [powerplay]=20 Mar 2 00:19:06 ph4 kernel: failed to send message 146 ret is 0=20 Mar 2 00:19:07 ph4 kernel: amdgpu: [powerplay]=20 Mar 2 00:19:07 ph4 kernel: failed to send pre message 148 ret is 0 --=20 You are receiving this mail because: You are the assignee for the bug.= --15199846400.8af7.26220 Date: Fri, 2 Mar 2018 09:57:20 +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 105324
Summary R9 285 weston hangs since drm/amd/pp: Fix bug that dpm level = was not really locked
Product DRI
Version DRI git
Hardware Other
OS All
Status NEW
Severity normal
Priority medium
Component DRM/AMDgpu
Assignee dri-devel@lists.freedesktop.org
Reporter adf.lists@gmail.com 

R9 285 Tonga,  testing with amdgpu.dc=3D0 on agd5f 4.17-wip

Since

commit a02497b73218f10f237d98fb10d34d0baed607a0
Author: Rex Zhu <Rex.Zhu@amd.=
com>
Date:   Fri Feb 9 16:47:53 2018 +0800

    drm/amd/pp: Fix bug that dpm level was not really locked

    Lock the dpm levels when we use SW method to modify
    the dpm tables directly to avoid a possible race
    with the smu.

weston may hang display on start/quit/vt switch

SysRq works and logged will be errors like -

Mar  2 00:19:03 ph4 kernel: amdgpu: [powerplay]=20
Mar  2 00:19:03 ph4 kernel:  failed to send message 18b ret is 0=20
Mar  2 00:19:03 ph4 kernel: amdgpu: [powerplay]=20
Mar  2 00:19:03 ph4 kernel:  failed to send pre message 18a ret is 0=20
Mar  2 00:19:04 ph4 kernel: amdgpu: [powerplay]=20
Mar  2 00:19:04 ph4 kernel:  failed to send message 18a ret is 0=20
Mar  2 00:19:04 ph4 kernel: amdgpu: [powerplay]=20
Mar  2 00:19:04 ph4 kernel:  failed to send pre message 18c ret is 0=20
Mar  2 00:19:04 ph4 kernel: amdgpu: [powerplay]=20
Mar  2 00:19:04 ph4 kernel:  failed to send message 18c ret is 0=20
Mar  2 00:19:05 ph4 kernel: amdgpu: [powerplay]=20
Mar  2 00:19:05 ph4 kernel:  failed to send pre message 145 ret is 0=20
Mar  2 00:19:05 ph4 kernel: amdgpu: [powerplay]=20
Mar  2 00:19:05 ph4 kernel:  failed to send message 145 ret is 0=20
Mar  2 00:19:06 ph4 kernel: amdgpu: [powerplay]=20
Mar  2 00:19:06 ph4 kernel:  failed to send pre message 146 ret is 0=20
Mar  2 00:19:06 ph4 kernel: amdgpu: [powerplay]=20
Mar  2 00:19:06 ph4 kernel:  failed to send message 146 ret is 0=20
Mar  2 00:19:07 ph4 kernel: amdgpu: [powerplay]=20
Mar  2 00:19:07 ph4 kernel:  failed to send pre message 148 ret is 0

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