From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@kernel.org
Subject: [Bug 197009] /proc/cpuinfo does not update frequency
Date: Mon, 20 Nov 2017 14:36:25 +0000 [thread overview]
Message-ID: <bug-197009-137361-2Ayz4ghyCT@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 #10 from Hal (haleakalas@yahoo.com) ---
Hi Rob. Thanks for your message.
I opened the ticket https://bugzilla.kernel.org/show_bug.cgi?id=197017 which
was marked as a DUPLICATE of this ticket and closed. That's why I came here to
comment and ask my question.
I don't want to waste anyone's time and post in the wrong place, but in my
experience the /proc/cpuinfo has ramifications beyond just the frequency meter
showing the top speed CPU as opposed to the actual real time CPU speed, at
least in XFCE according to my experience. Here is why?
1) Starting with 4.13.0 and with every subsequent version of the kernel
(including 4.14.0), when used on Linux Mint 18.2 64bit with XFCE, it causes the
"CPU Frequency Monitor" to show the top speed of the CPU, not the actual,
instantaneous frequency (in average mode). Note that with any prior version,
that is not the case and it works as it should.
2) Now, after I posted my bug report, I was let to understand that this was
because the XFCE panel plugin read the information from the wrong location, aka
"/proc/cpuinfo" rather than
"/sys/devices/system/cpu/cpufreq/policy*/scaling_cur_freq". Then my bug report
was marked as duplicate of this one and closed.
3) Fetching the CPU info in the wrong place might be only a "cosmetic" issue if
it is not being used for anything other than just showing info on the screen.
But it seems to be used for more than that. It somehow has a direct impact on
"intel_pstate" driver which gets disturbed and results in far greater power
consumption. When I observed that, I switched to "acpi_cpufreq" driver and the
power consumption got lower but not to the minimum as it was the case with
"intel_pstate" when running with an older kernel.
I don't know where "acpi_cpufreq" is getting its CPU speed cue but somehow it
behaves better than "intel_pstate" on this affected series of kernels.
4) The only exception to this occurrence is with kernel version
4.13.12-041312-generic #201711080535, which I currently use, and which makes my
machine behave EXACTLY as it did with older kernel versions. So, for me it WAS
a solution.
5) But the fix in 4.13.12 was reversed because apparently it caused to much CPU
IPI, etc. I can understand that a different fix is necessary. But I question
the wisdom of closing this ticket, unless there is another one that I haven't
been able to find yet.
As to the "cosmetic" vs "functional" aspect of the issue, it worries me even
more because it sounds like I am the only one out there observing power
consumption issues.
Again to reiterate, on my 6 month old Intel Pentium G4560 desktop I see this
issue, on my HP high end laptop with Intel i7-4710HQ, same behavior, and on a
low end unbranded laptop with Intel Celeron N3450 same tune! (All three systems
running Linux Mint 18.2 XFCE 64 bit in various state of update)
I understand this is not a discussion forum and only bug reports should be made
with useful information for the developers, and that's what I was trying to do.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-11-20 14:36 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
2017-11-20 5:28 ` bugzilla-daemon
2017-11-20 14:36 ` bugzilla-daemon [this message]
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-2Ayz4ghyCT@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).