All of lore.kernel.org
 help / color / mirror / Atom feed
* [Bug 101877] R9 390 with multiple monitors always using highest memory clock
@ 2017-07-22 14:48 bugzilla-daemon
  2017-07-23 14:07 ` bugzilla-daemon
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: bugzilla-daemon @ 2017-07-22 14:48 UTC (permalink / raw)
  To: dri-devel


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

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

            Bug ID: 101877
           Summary: R9 390 with multiple monitors always using highest
                    memory clock
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: hisele@siduge.v0yd.nl

My MSI r9 390 forces the memory clock to 150000 if I plug in more than one
monitor. The card draws 40 watts more power while idle and keeps the fans
running all the time.

This is happening with both amdgpu and radeon and I can fix the problem by
disabling dpm, but this causes some other issues.

I read earlier that this behaviour is intended and is a common problem with
graphics cards but IIRC a recent driver update fixed this on windows so I'd
like to know if there is any chance to also get a fix on linux?

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

[-- Attachment #1.2: Type: text/html, Size: 2398 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] 6+ messages in thread

* [Bug 101877] R9 390 with multiple monitors always using highest memory clock
  2017-07-22 14:48 [Bug 101877] R9 390 with multiple monitors always using highest memory clock bugzilla-daemon
@ 2017-07-23 14:07 ` bugzilla-daemon
  2017-07-23 14:14 ` bugzilla-daemon
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2017-07-23 14:07 UTC (permalink / raw)
  To: dri-devel


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

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

Alex Deucher <alexdeucher@gmail.com> changed:

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

--- Comment #1 from Alex Deucher <alexdeucher@gmail.com> ---
mclk changes have to be synced to the vertical blanking period of the displays.
 If the displays have different timings, it's not possible to change the mclk
without causing display flickering.

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

[-- Attachment #1.2: Type: text/html, Size: 2246 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] 6+ messages in thread

* [Bug 101877] R9 390 with multiple monitors always using highest memory clock
  2017-07-22 14:48 [Bug 101877] R9 390 with multiple monitors always using highest memory clock bugzilla-daemon
  2017-07-23 14:07 ` bugzilla-daemon
@ 2017-07-23 14:14 ` bugzilla-daemon
  2017-07-23 14:23 ` bugzilla-daemon
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2017-07-23 14:14 UTC (permalink / raw)
  To: dri-devel


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

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

--- Comment #2 from hisele@siduge.v0yd.nl ---
So does the windows driver detect the timing of the displays and keep the mclk
low if it's in sync?

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

[-- Attachment #1.2: Type: text/html, Size: 1133 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] 6+ messages in thread

* [Bug 101877] R9 390 with multiple monitors always using highest memory clock
  2017-07-22 14:48 [Bug 101877] R9 390 with multiple monitors always using highest memory clock bugzilla-daemon
  2017-07-23 14:07 ` bugzilla-daemon
  2017-07-23 14:14 ` bugzilla-daemon
@ 2017-07-23 14:23 ` bugzilla-daemon
  2017-07-23 14:43 ` bugzilla-daemon
  2018-09-18 12:47 ` bugzilla-daemon
  4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2017-07-23 14:23 UTC (permalink / raw)
  To: dri-devel


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

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

--- Comment #3 from Alex Deucher <alexdeucher@gmail.com> ---
AFAIK, the windows driver forces the mclk high as well when multiple displays
are attached.  The only possible exception would be if multiple displays had
the exact same timing and the vblank periods could be aligned.

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

[-- Attachment #1.2: Type: text/html, Size: 1285 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] 6+ messages in thread

* [Bug 101877] R9 390 with multiple monitors always using highest memory clock
  2017-07-22 14:48 [Bug 101877] R9 390 with multiple monitors always using highest memory clock bugzilla-daemon
                   ` (2 preceding siblings ...)
  2017-07-23 14:23 ` bugzilla-daemon
@ 2017-07-23 14:43 ` bugzilla-daemon
  2018-09-18 12:47 ` bugzilla-daemon
  4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2017-07-23 14:43 UTC (permalink / raw)
  To: dri-devel


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

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

--- Comment #4 from hisele@siduge.v0yd.nl ---
Yeah, both my monitors are the same model so this is probably the case. If
there's no way to enable changing the mclk, can I set it to a lower default
value without disabling dpm completely?

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

[-- Attachment #1.2: Type: text/html, Size: 1225 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] 6+ messages in thread

* [Bug 101877] R9 390 with multiple monitors always using highest memory clock
  2017-07-22 14:48 [Bug 101877] R9 390 with multiple monitors always using highest memory clock bugzilla-daemon
                   ` (3 preceding siblings ...)
  2017-07-23 14:43 ` bugzilla-daemon
@ 2018-09-18 12:47 ` bugzilla-daemon
  4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2018-09-18 12:47 UTC (permalink / raw)
  To: dri-devel


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

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

--- Comment #5 from Alexandre Pereira <pereira.alex@gmail.com> ---
I have a similar problem.

I have a Rx 580 with 2 exactly equal monitors. On windows, there is no issue
and memory clock is always at 300mhz, except when gaming.

When on linux, If using graphical display, memory clock is always MAX.
If i am only on the tty's ( text mode only ) I can set it to 300mhz, after
changing memory clock pp setting ( echo 1 > pp_mclk_od ).

Like the op, drawing 40 watts more power than windows, is very undesirable,
besides also running much cooler on windows. Also on windows I never saw any
problem whatsoever with it running at minimum 300mhz.

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

[-- Attachment #1.2: Type: text/html, Size: 1666 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] 6+ messages in thread

end of thread, other threads:[~2018-09-18 12:47 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-07-22 14:48 [Bug 101877] R9 390 with multiple monitors always using highest memory clock bugzilla-daemon
2017-07-23 14:07 ` bugzilla-daemon
2017-07-23 14:14 ` bugzilla-daemon
2017-07-23 14:23 ` bugzilla-daemon
2017-07-23 14:43 ` bugzilla-daemon
2018-09-18 12:47 ` 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.