From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102244] [powerplay] Can't overclock GPU memory
Date: Wed, 16 Aug 2017 10:13:51 +0000 [thread overview]
Message-ID: <bug-102244-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1244 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102244
Bug ID: 102244
Summary: [powerplay] Can't overclock GPU memory
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: claudio@thinkeasy.cz
Created attachment 133538
--> https://bugs.freedesktop.org/attachment.cgi?id=133538&action=edit
Complete `dmesg` output.
OS: Ubuntu Server 17.04, Linux 4.10.0
GPU: ASUS ROG Strix Radeon RX 570 4G Gaming
Performing a memory overclock using the following command:
echo 1 > /sys/class/drm/card1/device/pp_mclk_od
fails with the following output in dmesg:
VDDCI is larger than max VDDCI in VDDCI Voltage Table!
failed to send message 18a ret is 255
failed to send pre message 145 ret is 255
This issue seems to be related (but I'm not entirely sure) to this issue:
https://bugs.freedesktop.org/show_bug.cgi?id=100443
Complete `dmesg` output is attached.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2856 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-08-16 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 10:13 bugzilla-daemon [this message]
2017-08-16 10:15 ` [Bug 102244] [powerplay] Can't overclock GPU memory bugzilla-daemon
2017-08-16 10:16 ` bugzilla-daemon
2017-09-06 11:01 ` bugzilla-daemon
2019-11-19 8:21 ` 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-102244-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.