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, 20 Mar 2019 07:45:41 +0000 [thread overview]
Message-ID: <bug-202043-2300-HJ4uu4qy8L@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 #5 from Ivan Avdeev (lists@w23.ru) ---
Created attachment 281917
--> https://bugzilla.kernel.org/attachment.cgi?id=281917&action=edit
Example of undervolting effect
Example of what happens when undervolting is attempted. Notice how:
- frame time goes from stable ~15ms to stuttering 25-30ms
- core freq drops from ~1.4GHz to 1.1GHz
- memory freq goes from stable ~900MHz to rapidly oscillating between
200-900MHz.
Captured by running Unigine Superposition in game mode on medium setttings on
2560x1440 screen with
`GALLIUM_HUD=.d.w1920frametime,.d.w1920shader-clock+memory-clock
GALLIUM_HUD_PERIOD=0`
--
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
next prev parent reply other threads:[~2019-03-20 7: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 [this message]
2019-03-27 0:41 ` bugzilla-daemon
2019-03-27 0:45 ` bugzilla-daemon
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-HJ4uu4qy8L@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.