All of lore.kernel.org
 help / color / mirror / Atom feed
* [Bug 98004] RX470 doesn't reclock memory if a second display has been plugged in at some point
@ 2016-10-01 14:31 bugzilla-daemon
  2016-10-01 14:47 ` bugzilla-daemon
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: bugzilla-daemon @ 2016-10-01 14:31 UTC (permalink / raw)
  To: dri-devel


[-- 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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug 98004] RX470 doesn't reclock memory if a second display has been plugged in at some point
  2016-10-01 14:31 [Bug 98004] RX470 doesn't reclock memory if a second display has been plugged in at some point bugzilla-daemon
@ 2016-10-01 14:47 ` bugzilla-daemon
  2016-10-03  2:55 ` bugzilla-daemon
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: bugzilla-daemon @ 2016-10-01 14:47 UTC (permalink / raw)
  To: dri-devel


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

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

--- Comment #1 from Jonathan Moerman <jonathanmoerman@gmail.com> ---
Created attachment 126947
  --> https://bugs.freedesktop.org/attachment.cgi?id=126947&action=edit
Log from Linux 4.4 + amdgpu-pro kernel module

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

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug 98004] RX470 doesn't reclock memory if a second display has been plugged in at some point
  2016-10-01 14:31 [Bug 98004] RX470 doesn't reclock memory if a second display has been plugged in at some point bugzilla-daemon
  2016-10-01 14:47 ` bugzilla-daemon
@ 2016-10-03  2:55 ` bugzilla-daemon
  2016-10-03  6:53 ` bugzilla-daemon
  2016-10-03 16:09 ` bugzilla-daemon
  3 siblings, 0 replies; 5+ messages in thread
From: bugzilla-daemon @ 2016-10-03  2:55 UTC (permalink / raw)
  To: dri-devel


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

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

--- Comment #2 from Michel Dänzer <michel@daenzer.net> ---
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-4.9&id=9716ebc38dfabe6c8e5e3c809e9f3c61dd3740f9
should fix this.

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

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug 98004] RX470 doesn't reclock memory if a second display has been plugged in at some point
  2016-10-01 14:31 [Bug 98004] RX470 doesn't reclock memory if a second display has been plugged in at some point bugzilla-daemon
  2016-10-01 14:47 ` bugzilla-daemon
  2016-10-03  2:55 ` bugzilla-daemon
@ 2016-10-03  6:53 ` bugzilla-daemon
  2016-10-03 16:09 ` bugzilla-daemon
  3 siblings, 0 replies; 5+ messages in thread
From: bugzilla-daemon @ 2016-10-03  6:53 UTC (permalink / raw)
  To: dri-devel


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

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

--- Comment #3 from Jonathan Moerman <jonathanmoerman@gmail.com> ---
Ah, so it is fixed in drm next. I should have some time to test it today.

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

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug 98004] RX470 doesn't reclock memory if a second display has been plugged in at some point
  2016-10-01 14:31 [Bug 98004] RX470 doesn't reclock memory if a second display has been plugged in at some point bugzilla-daemon
                   ` (2 preceding siblings ...)
  2016-10-03  6:53 ` bugzilla-daemon
@ 2016-10-03 16:09 ` bugzilla-daemon
  3 siblings, 0 replies; 5+ messages in thread
From: bugzilla-daemon @ 2016-10-03 16:09 UTC (permalink / raw)
  To: dri-devel


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

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

Jonathan Moerman <jonathanmoerman@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Jonathan Moerman <jonathanmoerman@gmail.com> ---
I can confirm that it is fixed in drm-next-4.9.
(On first boot eventually the clocks got stuck at the minimum frequencies (both
memory and gpu), and the system hung when trying to shut down, but that's
something for another bug report. (No errors in the dmesg log.) Right now it
works fine.)

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

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2016-10-03 16:09 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-10-01 14:31 [Bug 98004] RX470 doesn't reclock memory if a second display has been plugged in at some point bugzilla-daemon
2016-10-01 14:47 ` bugzilla-daemon
2016-10-03  2:55 ` bugzilla-daemon
2016-10-03  6:53 ` bugzilla-daemon
2016-10-03 16:09 ` bugzilla-daemon

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.