From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110777] Kernel 5.1-5.2 MCLK stuck at 167MHz Vega 10 (56)
Date: Wed, 05 Jun 2019 17:44:58 +0000 [thread overview]
Message-ID: <bug-110777-502-2PRzK5Rzcy@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110777-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 581 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110777
--- Comment #5 from Anton Herzfeld <antonh@gmx.de> ---
The following patch fixes the issue with boosting again:
https://cgit.freedesktop.org/~agd5f/linux/commit/drivers/gpu/drm/amd/powerplay/hwmgr?h=amd-staging-drm-next&id=7d59c41b5150d0641203f91cfcaa0f9af5999cce
however it also seems to expose the issue in mclk not going down again once it
has boosted.
just to clarify the issue occurs when using manual OD on mclk since kernel 5.1.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1532 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-06-05 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 17:56 [Bug 110777] Kernel 5.1-5.2 MCLK stuck at 167MHz Vega 10 (56) bugzilla-daemon
2019-06-02 17:40 ` bugzilla-daemon
2019-06-03 18:41 ` bugzilla-daemon
2019-06-03 18:55 ` bugzilla-daemon
2019-06-03 19:21 ` bugzilla-daemon
2019-06-05 17:44 ` bugzilla-daemon [this message]
2019-06-11 17:04 ` 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-110777-502-2PRzK5Rzcy@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