All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111482] Sapphire Pulse RX 5700 XT power consumption
Date: Sat, 05 Oct 2019 11:55:29 +0000	[thread overview]
Message-ID: <bug-111482-502-44PNHhVgHS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111482-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1639 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=111482

--- Comment #23 from Andrew Sheldon <asheldon55@gmail.com> ---
@Leon

I suspect there is more than one bug occurring. The main Navi-specific issue
has been fixed with newer kernels (that affected everyone), but there is
another issue relating to high resolution and high refresh rate monitors, that
looks to affect at least Navi, Vega (and probably Polaris going by other
reports).

The secondary issue is probably by design to an extent. High res/refresh rate
requires a lot more bandwidth which needs a higher memory clock. However, I
suspect there are two problems within this:

- Once a high bandwidth mode is used and the maximum memory clock is chosen, it
never switches down again (even if you switch to a lower bandwidth mode).
Particularly, if you boot at 2560x1440@144hz, you won't be able to switch down
again.
- The choice of memory clock is higher than it needs to be, even for high
bandwidth modes

You can workaround this to some extent on Vega by writing to the powerplay
tables (while in a high bandwidth mode) and, in the case of Vega, the card will
stay in the more reasonable memory clock of 700mhz (versus the max of 950mhz).
However, if you then switch to any other high bandwidth mode (e.g.
2560x1440@120), the problem will return (card stuck at 950mhz).

I don't recommend trying that on Navi as powerplay table writing is currently
buggy without reverting a commit, I haven't confirmed the behaviour there, but
I suspect the same workaround will work.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2426 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

  parent reply	other threads:[~2019-10-05 11:55 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-25  8:43 [Bug 111482] Sapphire Pulse RX 5700 XT power consumption bugzilla-daemon
2019-08-26 23:07 ` bugzilla-daemon
2019-08-27  4:47 ` bugzilla-daemon
2019-08-27  7:25 ` bugzilla-daemon
2019-08-27 22:20 ` bugzilla-daemon
2019-08-28 14:25 ` bugzilla-daemon
2019-08-29 16:27 ` bugzilla-daemon
2019-09-03  9:35 ` bugzilla-daemon
2019-09-03 16:54 ` bugzilla-daemon
2019-09-04  1:16 ` bugzilla-daemon
2019-09-04 22:16 ` bugzilla-daemon
2019-09-05  1:01 ` bugzilla-daemon
2019-09-05  2:20 ` bugzilla-daemon
2019-09-05 14:21 ` bugzilla-daemon
2019-09-05 14:24 ` bugzilla-daemon
2019-09-05 14:53 ` bugzilla-daemon
2019-09-05 18:16 ` bugzilla-daemon
2019-09-08  2:02 ` bugzilla-daemon
2019-09-10 19:27 ` bugzilla-daemon
2019-09-27 10:49 ` bugzilla-daemon
2019-09-27 10:51 ` bugzilla-daemon
2019-09-28  7:38 ` bugzilla-daemon
2019-09-28  9:05 ` bugzilla-daemon
2019-09-28 10:14 ` bugzilla-daemon
2019-10-05 11:55 ` bugzilla-daemon [this message]
2019-10-05 12:20 ` bugzilla-daemon
2019-10-06  4:45 ` bugzilla-daemon
2019-10-07  8:31 ` bugzilla-daemon
2019-10-07 10:05 ` bugzilla-daemon
2019-10-26  8:33 ` bugzilla-daemon
2019-11-01  3:01 ` bugzilla-daemon
2019-11-02  4:22 ` bugzilla-daemon
2019-11-03 16:55 ` bugzilla-daemon
2019-11-04 16:31 ` bugzilla-daemon
2019-11-04 16:42 ` bugzilla-daemon
2019-11-04 23:48 ` bugzilla-daemon
2019-11-05  0:37 ` bugzilla-daemon
2019-11-05  0:43 ` bugzilla-daemon
2019-11-05  0:50 ` bugzilla-daemon
2019-11-05  5:57 ` bugzilla-daemon
2019-11-08  1:35 ` bugzilla-daemon
2019-11-08  1:36 ` bugzilla-daemon
2019-11-08  6:36 ` bugzilla-daemon
2019-11-19  9:50 ` 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-111482-502-44PNHhVgHS@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.