From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@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
Message-ID:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1420850124=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 4E0E16E07B
for ; Sat, 1 Oct 2016 14:31:01 +0000 (UTC)
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1420850124==
Content-Type: multipart/alternative; boundary="14753322610.d194CE29C.10002";
charset="UTF-8"
--14753322610.d194CE29C.10002
Date: Sat, 1 Oct 2016 14:31:01 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D98004
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 unplug=
ged
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 (Her=
e:
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.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--14753322610.d194CE29C.10002
Date: Sat, 1 Oct 2016 14:31:01 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
| Bug ID |
98004
|
| Summary |
RX470 doesn't reclock memory if a second display has been plu=
gged 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 unplug=
ged
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 (Her=
e:
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.=
pre>
You are receiving this mail because:
- You are the assignee for the bug.
=
--14753322610.d194CE29C.10002--
--===============1420850124==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1420850124==--