From: Mascha Kurpicz <mascha.kurpicz@unine.ch>
To: cpufreq@vger.kernel.org
Cc: Maxime Colmant <maxime.colmant@inria.fr>
Subject: time_in_state on Ubuntu 13.10
Date: Mon, 28 Apr 2014 16:43:18 +0200 [thread overview]
Message-ID: <535E6906.2090201@unine.ch> (raw)
Hi,
First of all I would like to thank for the cpufreq utility that I use
regularly.
Unfortunately, when upgrading our systems from Ubuntu 12.04 to 13.10, we
are encountering some issues with the data in
/sys/devices/system/cpu/cpu*/cpufreq/stats/time_in_state.
On some of the machines, the values are all set to 0 [1], whereas on
other machines, values are 0 or very small [2]. In both cases, the
output of cpufreq-info for the cpufreq stats is not correct. When
running Ubuntu 12.04, we get reasonable values.
We noticed this behavior on Intel i3 machines, and on Intel Xeon. Kernel
version in all cases is 3.11.0-20-generic.
Thanks in advance and best regards,
Mascha
---
[1]
user@ubuntu1310:~$ cat
/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
3100000 0
2800000 0
2600000 0
2400000 0
2200000 0
2000000 0
1800000 0
1600000 0
user@ubuntu1310:~$ cpufreq-info
...
cpufreq stats: 3.10 GHz:-nan%, 2.80 GHz:-nan%, 2.60 GHz:-nan%, 2.40
GHz:-nan%, 2.20 GHz:-nan%, 2.00 GHz:-nan%, 1.80 GHz:-nan%, 1.60
GHz:-nan% (21768)
...
[2]
user@ubuntu1310:~$ cat
/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
3100000 0
2800000 0
2600000 0
2400000 0
2200000 0
2000000 0
1800000 0
1600000 6
user@ubuntu1310:~$ cpufreq-info
...
cpufreq stats: 3.10 GHz:0.00%, 2.80 GHz:0.00%, 2.60 GHz:0.00%, 2.40
GHz:0.00%, 2.20 GHz:0.00%, 2.00 GHz:0.00%, 1.80 GHz:0.00%, 1.60
GHz:100.00% (86356)
...
next reply other threads:[~2014-04-28 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 14:43 Mascha Kurpicz [this message]
2014-04-29 4:28 ` time_in_state on Ubuntu 13.10 Viresh Kumar
2014-04-29 7:17 ` Mascha Kurpicz
2014-04-29 8:26 ` Viresh Kumar
2014-04-29 8:38 ` Mascha Kurpicz
2014-05-02 5:25 ` Viresh Kumar
2014-05-05 12:08 ` Mascha Kurpicz
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=535E6906.2090201@unine.ch \
--to=mascha.kurpicz@unine.ch \
--cc=cpufreq@vger.kernel.org \
--cc=maxime.colmant@inria.fr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).