From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102130] pp_dpm_mclk always on level 1 (cant set to level 0) rx 480
Date: Wed, 09 Aug 2017 10:03:23 +0000 [thread overview]
Message-ID: <bug-102130-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1198 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102130
Bug ID: 102130
Summary: pp_dpm_mclk always on level 1 (cant set to level 0) rx
480
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: gsedej@gmail.com
I can't set memory state to 0 (300 MHz), it always stays at state 1 (2000 MHz).
If I set
echo "manual" > power_dpm_force_performance_level
echo 0 > pp_dpm_mclk
the memory clock stays at level 1, and I get kernel message:
[ 239.231304] amdgpu: [powerplay]
failed to send message 146 ret is 255
[ 239.995386] amdgpu: [powerplay]
failed to send pre message 201 ret is 255
The hardware is "SAPPHIRE NITRO+ Radeon RX 480 OC" and it might be BIOS
related, since some rx 480 users does not have such problem.
Using Ubuntu 16.04.2 kernel 4.13-rc4.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2509 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:[~2017-08-09 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 10:03 bugzilla-daemon [this message]
2017-08-09 13:26 ` [Bug 102130] pp_dpm_mclk always on level 1 (cant set to level 0) rx 480 bugzilla-daemon
2017-08-10 8:15 ` bugzilla-daemon
2017-08-10 8:16 ` bugzilla-daemon
2017-08-10 8:17 ` bugzilla-daemon
2017-12-20 18:15 ` bugzilla-daemon
2017-12-20 18:41 ` 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-102130-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.