From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101877] R9 390 with multiple monitors always using highest memory clock
Date: Sat, 22 Jul 2017 14:48:06 +0000 [thread overview]
Message-ID: <bug-101877-502@http.bugs.freedesktop.org/> (raw)
[-- 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
next reply other threads:[~2017-07-22 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-22 14:48 bugzilla-daemon [this message]
2017-07-23 14:07 ` [Bug 101877] R9 390 with multiple monitors always using highest memory clock 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
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-101877-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 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.