From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@kernel.org
Subject: [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo
Date: Sun, 08 Oct 2017 03:37:21 +0000 [thread overview]
Message-ID: <bug-197153-137361-FXeAl0Phlo@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197153-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=197153
--- Comment #7 from Doug Smythies (dsmythies@telus.net) ---
@Artem: Please be considerate that, since this bug is unassigned, emails are
going to the entire linux-pm e-mail list.
> The /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq interface is also
> broken in 4.13.
It is not broken, and the numbers you are getting are most probably correct.
If you are running a desktop computer with a GUI, then this statement:
"my laptop is more or less completely idle"
simply is not true. You would have to disable the GUI and a bunch of other
services to get a more idle system (which would still not be completely idle).
If I use my test Ubuntu 16.04.3 server (no GUI) and disable several services,
i.e.:
$ cat set_cpu_turn_off_services
#! /bin/bash
# Turn off some services to try to get "idle" to be more "idle"
sudo systemctl stop mysql.service
sudo systemctl stop apache2.service
sudo systemctl stop nmbd.service
sudo systemctl stop smbd.service
sudo systemctl stop cron.service
sudo systemctl stop winbind.service
sudo systemctl stop apt-daily.timer
then for your command I usually get 1.61 GHz, which is the minimum for my
processor.
In order to not influence the system I was testing, I ran your command at a
very slow rate of once every 2 seconds for 6112 samples. 5970 (97.68%) of them
reported the minimum frequency for my 8 CPU processor.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-10-08 3:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-197153-137361@https.bugzilla.kernel.org/>
2017-10-07 14:10 ` [Bug 197153] Wrong cores frequencies values in /proc/cpuinfo bugzilla-daemon
2017-10-07 15:13 ` bugzilla-daemon
2017-10-07 15:21 ` bugzilla-daemon
2017-10-07 15:41 ` bugzilla-daemon
2017-10-07 15:53 ` bugzilla-daemon
2017-10-07 15:57 ` bugzilla-daemon
2017-10-07 16:02 ` bugzilla-daemon
2017-10-07 22:33 ` bugzilla-daemon
2017-10-08 3:37 ` bugzilla-daemon [this message]
2017-10-11 5:49 ` bugzilla-daemon
2017-10-16 22:51 ` 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-197153-137361-FXeAl0Phlo@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).