dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98004] RX470 doesn't reclock memory if a second display has been plugged in at some point
Date: Sat, 01 Oct 2016 14:31:01 +0000	[thread overview]
Message-ID: <bug-98004-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 98004
           Summary: RX470 doesn't reclock memory if a second display has
                    been plugged in at some point
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: minor
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: jonathanmoerman@gmail.com

If a second display has been plugged in the memory clock gets stuck at the
highest frequency, even if the display is disabled (using xrandr) or unplugged
again.

How to reproduce: plug in a second display and either disable it or unplug it
again, the memory will continue to be clocked at its maximal frequency (Here:
1750Mhz).

Kernels used for testing: Linux 4.4 (amdgpu-pro kernel driver), 4.7, 4.8rc5

The hardware is perfectly capable of clocking back to its lowest frequency if
only one display is actually enabled. (It works as expected in Windows)

This issue doesn't cause any problems other than using more watts than
necessary.

I'm not currently using the system with the RX470 GPU, I'll upload a dmesg log
in a few minutes.

I'm sorry if this isn't the correct place to post this bug, I'm new here.

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

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

             reply	other threads:[~2016-10-01 14:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-01 14:31 bugzilla-daemon [this message]
2016-10-01 14:47 ` [Bug 98004] RX470 doesn't reclock memory if a second display has been plugged in at some point bugzilla-daemon
2016-10-03  2:55 ` bugzilla-daemon
2016-10-03  6:53 ` bugzilla-daemon
2016-10-03 16:09 ` 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-98004-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;
as well as URLs for NNTP newsgroup(s).