From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109887] vega56 undervolting/overclocking voltage issues
Date: Wed, 31 Jul 2019 10:43:38 +0000 [thread overview]
Message-ID: <bug-109887-502-hYalCKk04U@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109887-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1000 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109887
--- Comment #10 from Andrew Sheldon <asheldon55@gmail.com> ---
(In reply to Andrew Sheldon from comment #9)
> I will note that you might still see raised voltages if you do a too
> aggressive overclock/undervolt with modded PP tables, but it seems to only
> overvolt as much as is needed (say 975mv -> 1.05V) if you set a too high
> clock, rather than jumping to the maximum possible voltage that you see by
> editing pp_od_clk_voltage.
Replying to myself here. I've found that the raised voltage occurs when forcing
GPU state to "high". If I then re-write the PP table again, it settles on the
correct voltage, and successfully switches to "high" after. I'm not sure if
this is related to some of the other voltage issues, but there you go. This
occurs on both 5.2.3 and 5.3-rc2, for the record.
I have to do this every time I force to "high", BTW.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1899 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-07-31 10:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 8:06 [Bug 109887] vega56 undervolting/overclocking voltage issues bugzilla-daemon
2019-03-06 8:08 ` bugzilla-daemon
2019-03-06 8:10 ` bugzilla-daemon
2019-03-06 14:52 ` bugzilla-daemon
2019-03-06 15:45 ` bugzilla-daemon
2019-04-07 14:48 ` bugzilla-daemon
2019-06-07 22:10 ` bugzilla-daemon
2019-06-20 13:38 ` bugzilla-daemon
2019-07-31 4:05 ` bugzilla-daemon
2019-07-31 9:16 ` bugzilla-daemon
2019-07-31 10:43 ` bugzilla-daemon [this message]
2019-10-13 18:26 ` bugzilla-daemon
2019-10-13 20:05 ` bugzilla-daemon
2019-10-23 14:40 ` bugzilla-daemon
2019-10-23 14:41 ` bugzilla-daemon
2019-10-23 14:59 ` [Bug 109887] [Vega10][powerplay] P7 gets reset to max_vddc (1.2V/1.25V) after applying any custom settings via pp_od_clk_voltage and/or pp_table bugzilla-daemon
2019-10-24 9:53 ` bugzilla-daemon
2019-10-28 22:00 ` bugzilla-daemon
2019-10-31 13:05 ` 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-109887-502-hYalCKk04U@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;
as well as URLs for NNTP newsgroup(s).