From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110865] Rx480 consumes 20w more power in idle than under Windows
Date: Tue, 27 Aug 2019 18:11:14 +0000 [thread overview]
Message-ID: <bug-110865-502-Lm01ujMLaE@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110865-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1220 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110865
--- Comment #27 from Dieter Nützel <Dieter@nuetzel-hh.de> ---
This is going nuts...
Martins has
2 different displays (both 59.95Hz@1920x1200),
RX 480 and _very nice_ numbers (only 12.222 W), now
GFX Clocks and Power:
300 MHz (MCLK) <= !!!
308 MHz (SCLK)
300 MHz (PSTATE_SCLK)
300 MHz (PSTATE_MCLK)
800 mV (VDDGFX) <= !!!
12.222 W (average GPU)
=> working (?!) but flicker
I have
2 identical displays BenQ GL2440H (both 60.00 Hz @ 1920x1080),
RX580 and 'normal' numbers (~32 W - but to high?!), now
GFX Clocks and Power:
300 MHz (MCLK) <= !!!
300 MHz (SCLK)
600 MHz (PSTATE_SCLK)
1000 MHz (PSTATE_MCLK)
750 mV (VDDGFX) <= !!! mine is better, but...
32.76 W (average GPU)
=> working (?!) but flicker, too.
This
600 MHz (PSTATE_SCLK)
1000 MHz (PSTATE_MCLK)
must be a different problem (compare with Martin's RX 480).
I open another ticket for it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2047 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-08-27 18:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 13:22 [Bug 110865] Rx480 consumes 20w more power in idle than under Windows bugzilla-daemon
2019-06-10 0:58 ` bugzilla-daemon
2019-08-07 9:53 ` bugzilla-daemon
2019-08-07 14:35 ` bugzilla-daemon
2019-08-07 15:16 ` bugzilla-daemon
2019-08-08 5:46 ` bugzilla-daemon
2019-08-08 5:49 ` bugzilla-daemon
2019-08-08 10:29 ` bugzilla-daemon
2019-08-08 13:31 ` bugzilla-daemon
2019-08-08 13:37 ` bugzilla-daemon
2019-08-08 14:08 ` bugzilla-daemon
2019-08-08 14:45 ` bugzilla-daemon
2019-08-08 15:42 ` bugzilla-daemon
2019-08-08 23:39 ` bugzilla-daemon
2019-08-08 23:56 ` bugzilla-daemon
2019-08-09 14:59 ` bugzilla-daemon
2019-08-20 13:41 ` bugzilla-daemon
2019-08-22 16:17 ` bugzilla-daemon
2019-08-22 16:17 ` bugzilla-daemon
2019-08-25 20:53 ` bugzilla-daemon
2019-08-25 21:00 ` bugzilla-daemon
2019-08-26 3:00 ` bugzilla-daemon
2019-08-26 9:37 ` bugzilla-daemon
2019-08-26 21:45 ` bugzilla-daemon
2019-08-26 22:07 ` bugzilla-daemon
2019-08-26 22:45 ` bugzilla-daemon
2019-08-27 14:37 ` bugzilla-daemon
2019-08-27 18:09 ` bugzilla-daemon
2019-08-27 18:11 ` bugzilla-daemon [this message]
2019-08-27 18:22 ` bugzilla-daemon
2019-08-29 10:50 ` bugzilla-daemon
2019-08-29 13:10 ` bugzilla-daemon
2019-08-29 13:44 ` bugzilla-daemon
2019-08-29 13:54 ` bugzilla-daemon
2019-08-29 14:28 ` bugzilla-daemon
2019-08-29 14:33 ` bugzilla-daemon
2019-08-30 15:44 ` bugzilla-daemon
2019-10-03 20:43 ` bugzilla-daemon
2019-10-08 0:57 ` bugzilla-daemon
2019-11-19 9:30 ` 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-110865-502-Lm01ujMLaE@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