From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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 [thread overview]
Message-ID: <bug-105324-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2280 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105324
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=0 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]
Mar 2 00:19:03 ph4 kernel: failed to send message 18b ret is 0
Mar 2 00:19:03 ph4 kernel: amdgpu: [powerplay]
Mar 2 00:19:03 ph4 kernel: failed to send pre message 18a ret is 0
Mar 2 00:19:04 ph4 kernel: amdgpu: [powerplay]
Mar 2 00:19:04 ph4 kernel: failed to send message 18a ret is 0
Mar 2 00:19:04 ph4 kernel: amdgpu: [powerplay]
Mar 2 00:19:04 ph4 kernel: failed to send pre message 18c ret is 0
Mar 2 00:19:04 ph4 kernel: amdgpu: [powerplay]
Mar 2 00:19:04 ph4 kernel: failed to send message 18c ret is 0
Mar 2 00:19:05 ph4 kernel: amdgpu: [powerplay]
Mar 2 00:19:05 ph4 kernel: failed to send pre message 145 ret is 0
Mar 2 00:19:05 ph4 kernel: amdgpu: [powerplay]
Mar 2 00:19:05 ph4 kernel: failed to send message 145 ret is 0
Mar 2 00:19:06 ph4 kernel: amdgpu: [powerplay]
Mar 2 00:19:06 ph4 kernel: failed to send pre message 146 ret is 0
Mar 2 00:19:06 ph4 kernel: amdgpu: [powerplay]
Mar 2 00:19:06 ph4 kernel: failed to send message 146 ret is 0
Mar 2 00:19:07 ph4 kernel: amdgpu: [powerplay]
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.
[-- Attachment #1.2: Type: text/html, Size: 3640 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-03-02 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 9:57 bugzilla-daemon [this message]
2018-03-07 10:46 ` [Bug 105324] R9 285 weston hangs since drm/amd/pp: Fix bug that dpm level was not really locked bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-105324-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox