linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 215729] amd-pstate driver has a much higher idle power consumption for a desktop Zen 3 CPU
Date: Wed, 23 Mar 2022 02:09:55 +0000	[thread overview]
Message-ID: <bug-215729-137361-qzrr3AfEal@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215729-137361@https.bugzilla.kernel.org/>

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

Huang Rui (huangrui@mail.ustc.edu.cn) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |huangrui@mail.ustc.edu.cn

--- Comment #3 from Huang Rui (huangrui@mail.ustc.edu.cn) ---
(In reply to Artem S. Tashkinov from comment #0)
> I have a Ryzen 7 5800X CPU.
> 
> With the acpi-cpufreq driver the CPU idles around 20W, frequencies are in
> the range of 2.2-2.8GHz.
> 
> The very same system with the amd-pstate driver idles around 25W frequencies
> are in the range of 3.9-4.75GHz.
> 
> This doesn't look right.
> 
> Changing governor from ondemand to powersave reduces idle power consumption
> to around 21.5W (still higher than with acpi-cpufreq) but this obvious
> completely destroys performance.

Thanks to report the issue. Could you please dump the print of "lscpu" and use
the latest bleeding-edge source code include the CPUPower support
(https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/log/?h=bleeding-edge)
to print "cpupower frequency-info"?

Thanks,
Ray

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2022-03-23  2:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 23:58 [Bug 215729] New: amd-pstate driver has a much higher idle power consumption for a desktop Zen 3 CPU bugzilla-daemon
2022-03-22 23:59 ` [Bug 215729] " bugzilla-daemon
2022-03-23  0:01 ` bugzilla-daemon
2022-03-23  2:09 ` bugzilla-daemon [this message]
2022-03-23 15:35 ` bugzilla-daemon
2022-03-23 15:41 ` bugzilla-daemon
2022-03-23 15:58 ` bugzilla-daemon
2022-03-23 16:04 ` bugzilla-daemon
2022-04-28  8:49 ` bugzilla-daemon
2022-05-09  8:38 ` bugzilla-daemon
2023-07-07 13:24 ` bugzilla-daemon
2023-09-15 10:24 ` 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-215729-137361-qzrr3AfEal@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-pm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).