From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101528] RX460 Memory clock stays high until card is "used"
Date: Thu, 29 Jun 2017 17:36:48 +0000 [thread overview]
Message-ID: <bug-101528-502-GAs9I10WKh@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101528-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 684 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101528
--- Comment #1 from Alexander Tsoy <alexander@tsoy.me> ---
Same problem with TONGA. When GPU is idle, mclk goes to its maximum. This is
easily reproducible: just turn off the monitor. I noticed this issue after
upgrade from 4.9.x kernels to 4.11.7. Maybe I'll check the mainline kernel
later and/or bisect.
# cat /sys/class/drm/card0/device/pp_dpm_mclk
0: 150Mhz
1: 300Mhz
2: 700Mhz
3: 1450Mhz *
# sensors amdgpu-\*
amdgpu-pci-0100
Adapter: PCI adapter
fan1: 2025 RPM
temp1: +47.0°C (crit = +0.0°C, hyst = +0.0°C)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1489 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 prev parent reply other threads:[~2017-06-29 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 18:58 [Bug 101528] RX460 Memory clock stays high until card is "used" bugzilla-daemon
2017-06-29 17:36 ` bugzilla-daemon [this message]
2017-06-29 19:48 ` bugzilla-daemon
2017-06-29 20:14 ` bugzilla-daemon
2017-06-29 22:14 ` bugzilla-daemon
2017-07-14 11:52 ` bugzilla-daemon
2017-07-14 11:53 ` [Bug 101528] RX460 Memory clock stays high until card / display " bugzilla-daemon
2017-08-30 15:13 ` 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-101528-502-GAs9I10WKh@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