All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202043] amdgpu: Vega 56 SCLK drops to 700 Mhz when undervolting
Date: Wed, 27 Mar 2019 00:45:46 +0000	[thread overview]
Message-ID: <bug-202043-2300-LzEoc1r8mr@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202043-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=202043

--- Comment #7 from mistarzy@gmail.com ---
Best results performance wise had with following setup:

echo 275000000 >> /sys/class/drm/card0/device/hwmon/hwmon0/power1_cap
echo "m 3 1100 1000" > /sys/class/drm/card0/device/pp_od_clk_voltage

GPU clock hovered above 1400Mhz and memory kept state 3 with 1100Mhz even
though I did not change to manual or sent commit. But after extensive use by
benchmarking or gaming for 20+ min drivers seems to bug at goes to lower states
even though temperatures stay the same. Let me know if you would like some
tests and logs.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-03-27  0:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-22 12:24 [Bug 202043] New: amdgpu: Vega 56 SCLK drops to 700 Mhz when undervolting bugzilla-daemon
2018-12-22 15:31 ` [Bug 202043] " bugzilla-daemon
2018-12-24 13:05 ` bugzilla-daemon
2018-12-26 19:39 ` bugzilla-daemon
2019-03-20  7:40 ` bugzilla-daemon
2019-03-20  7:45 ` bugzilla-daemon
2019-03-27  0:41 ` bugzilla-daemon
2019-03-27  0:45 ` bugzilla-daemon [this message]
2019-09-29  5:04 ` bugzilla-daemon
2019-10-31 13:07 ` bugzilla-daemon
2021-02-08 18:22 ` 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-202043-2300-LzEoc1r8mr@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.