Bug 102244

Summary: [powerplay] Can't overclock GPU memory
Product: DRI Reporter: Claudio Kozický <claudio>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: vittorio88
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Complete `dmesg` output.
none
`lspci` output
none
`lspci -vvv` output. none

Description Claudio Kozický 2017-08-16 10:13:51 UTC 
Created attachment 133538 [details]
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.
Comment 1 Claudio Kozický 2017-08-16 10:15:09 UTC 
Created attachment 133539 [details]
`lspci` output
Comment 2 Claudio Kozický 2017-08-16 10:16:07 UTC 
Created attachment 133540 [details]
`lspci -vvv` output.
Comment 3 Vittorio 2017-09-06 11:01:54 UTC 
I can confirm the issue.

I have tested on Ubuntu 16.04.2 and 17.04. Both give the same results.
17.04 as of today uses kernel 4.10.0-33-generic #37-Ubuntu.

I am using Radeon Rx470 for testing.

I can successfully overclock memory on Windows.

Many other people have this issue on amd.com and phoronix.com forums.

I do not believe I have run across a single instance of this working across many forums where I have investigated.

I am willing to provide further info and testing if required, and have placed myself on CC.

Thanks,
Vittorio
Comment 4 Martin Peres 2019-11-19 08:21:17 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/221.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.