From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@kernel.org
Subject: [Bug 197009] /proc/cpuinfo does not update frequency
Date: Sat, 18 Nov 2017 15:34:27 +0000 [thread overview]
Message-ID: <bug-197009-137361-37t5DMdHLK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197009-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=197009
--- Comment #8 from Hal (haleakalas@yahoo.com) ---
The "fix" in 4.13.12 was undone/reversed in 4.13.13 and subsequent releases,
including 4.13.14 and 4.14.0.
Therefore we are back to square one with this issue, whether you call it a bug,
a regression or the improvement of the code.
This has a significant impact on power consumption on some machines, especially
laptops and passive cooling type setups.
The issue that was reported as "CPU Frequency Monitor showing the maximum
frequency of the CPU in XFCE at all times" is just the tip of the iceberg. It
is far from being a cosmetic issue. It functionally is very disruptive.
On laptops it drains the battery at a rate far greater than normal. It makes
the difference of being or not being able to use your laptop during a 4 hr
flight.
Going back to acpi_cpufreq instead of intel_pstate is a temporary solution on
some hardware, but not always, as acpi_cpufreq doesn't seem to have the same
level of power savings optimizations as in intel_pstate.
What would it take to "reopen" this issue as it looks like from a "bug" point
of view this is now set aside.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-11-18 15:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 18:55 [Bug 197009] New: /proc/cpuinfo does not update frequency bugzilla-daemon
2017-09-20 19:03 ` [Bug 197009] " bugzilla-daemon
2017-09-20 19:14 ` bugzilla-daemon
2017-09-22 5:01 ` bugzilla-daemon
2017-10-11 5:51 ` bugzilla-daemon
2017-10-17 1:41 ` bugzilla-daemon
2017-10-24 5:12 ` bugzilla-daemon
2017-11-02 1:44 ` bugzilla-daemon
2017-11-05 22:28 ` bugzilla-daemon
2017-11-18 15:34 ` bugzilla-daemon [this message]
2017-11-20 5:28 ` bugzilla-daemon
2017-11-20 14:36 ` bugzilla-daemon
2017-11-20 19:12 ` bugzilla-daemon
2017-11-20 22:16 ` bugzilla-daemon
2017-11-20 22:22 ` bugzilla-daemon
2017-11-21 1: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-197009-137361-37t5DMdHLK@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-pm@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).