From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106177] overclocking doesn't work with 4.17-rc1
Date: Fri, 04 May 2018 16:49:22 +0000 [thread overview]
Message-ID: <bug-106177-502-5REeeY62Kn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106177-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 929 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106177
--- Comment #4 from tempel.julian@gmail.com ---
I'm on a RX 560.
I can confirm that with 4.17, behavior has quite changed a lot. I don't think
it's buggy for Polaris, but not documented correctly.
To make values "stick" in pp_sclk_od, you have to boot with the parameter
amdgpu.ppfeaturemask=0xffffffff.
Applying values higher than 1 in pp_sclk_od don't get reported back correctly,
cat pp_sclk_od always returns 1.
However, entering values higher than 1 have an effect despite of this, as they
allow using of higher clocks in pp_od_clk_voltage.
And unlike with 4.16, higher values than 0 in pp_sclk_od don't automatically
lead to higher clocks. Additionally it is also required to change the pstates
in pp_od_clk_voltage (again unlocked with amdgpu.ppfeaturemask=0xffffffff).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1690 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 prev parent reply other threads:[~2018-05-04 16:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-22 16:46 [Bug 106177] overclocking doesn't work with 4.17-rc1 bugzilla-daemon
2018-05-03 17:55 ` bugzilla-daemon
2018-05-03 23:42 ` bugzilla-daemon
2018-05-03 23:46 ` bugzilla-daemon
2018-05-04 16:49 ` bugzilla-daemon [this message]
2018-05-08 21:21 ` bugzilla-daemon
2018-05-09 7:11 ` bugzilla-daemon
2018-10-16 4:03 ` bugzilla-daemon
2018-10-16 4:07 ` bugzilla-daemon
2018-10-18 22:33 ` bugzilla-daemon
2018-10-18 22:37 ` bugzilla-daemon
2018-10-19 1:47 ` 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-106177-502-5REeeY62Kn@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