From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99718] RX480 - MCLK stuck at 300
Date: Thu, 09 Feb 2017 06:14:02 +0000 [thread overview]
Message-ID: <bug-99718-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1171 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99718
Bug ID: 99718
Summary: RX480 - MCLK stuck at 300
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: b747xx@gmail.com
Created attachment 129417
--> https://bugs.freedesktop.org/attachment.cgi?id=129417&action=edit
DMESG
I,
I just found out that the MCLK was stuck at 300Mhz on my Polaris10 card. I got
the card last week, I don't really know if it's new. I have git version of
linux, mesa, libdrm.
I can force the power to high and get the proper 2000Mhz and when I set it back
to auto, it go back down to 300Mhz, halving my EVE-Online fps by about 200%.
The SCLK is normal, It move according to load on auto and move according to
crappy cooling on high.
I got some error in the dmesg too, can be related, or no.., I attach them.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2546 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-02-09 6:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 6:14 bugzilla-daemon [this message]
2017-02-09 13:44 ` [Bug 99718] RX480 - MCLK stuck at 300 bugzilla-daemon
2017-02-09 13:46 ` bugzilla-daemon
2017-02-09 16:20 ` bugzilla-daemon
2017-03-09 4:02 ` 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-99718-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).