From: Mascha Kurpicz <mascha.kurpicz@unine.ch>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Linux PM list <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
Maxime Colmant <maxime.colmant@inria.fr>
Subject: Re: time_in_state on Ubuntu 13.10
Date: Tue, 29 Apr 2014 09:17:11 +0200 [thread overview]
Message-ID: <535F51F7.5090804@unine.ch> (raw)
In-Reply-To: <CAOh2x==Q_oDn9v4S5ggh_e-3_=vSU_5Ko_89LfWM9ARBS9i=Rg@mail.gmail.com>
Hi,
Sorry for the imprecision.
Works correctly with
Ubuntu 12.04.3 LTS - kernel 3.2.0-29-generic
Ubuntu 12.04.3 LTS - kernel 3.8.0-29
Ubuntu 13.10 - kernel 3.8.0-29-generic
0 or very small (e.g. 6) values with
Ubuntu 13.10 - kernel 3.11.0-20-generic
Thanks,
Mascha
On 04/29/2014 06:28 AM, Viresh Kumar wrote:
> On Mon, Apr 28, 2014 at 8:13 PM, Mascha Kurpicz <mascha.kurpicz@unine.ch> wrote:
>> 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.
> Do you mean that kernel version is same for 12.04 and 13.10? We need
> kernel versions for these two bases.
next prev parent reply other threads:[~2014-04-29 7:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 14:43 time_in_state on Ubuntu 13.10 Mascha Kurpicz
2014-04-29 4:28 ` Viresh Kumar
2014-04-29 7:17 ` Mascha Kurpicz [this message]
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=535F51F7.5090804@unine.ch \
--to=mascha.kurpicz@unine.ch \
--cc=cpufreq@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maxime.colmant@inria.fr \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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