From: Mascha Kurpicz <mascha.kurpicz@unine.ch>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
Maxime Colmant <maxime.colmant@inria.fr>
Subject: Re: time_in_state on Ubuntu 13.10
Date: Mon, 5 May 2014 14:08:09 +0200 [thread overview]
Message-ID: <53677F29.2090905@unine.ch> (raw)
In-Reply-To: <CAKohponNhk2wxM2vTX6ZWf590bxTSjT-53oV9D6AKPch+VbsSw@mail.gmail.com>
On 05/02/2014 07:25 AM, Viresh Kumar wrote:
> On 29 April 2014 14:08, Mascha Kurpicz <mascha.kurpicz@unine.ch> wrote:
>> On 04/29/2014 10:26 AM, Viresh Kumar wrote:
>>> On 29 April 2014 12:47, Mascha Kurpicz <mascha.kurpicz@unine.ch> wrote:
>>>> 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
>>> Can you provide cpufreq-info 's output for the last two cases please?
> Sorry, got distracted and just forgot about this thread :), must have marked
> it in my pending list :(
>
> Anyways, I have tried to look at the diff between these kernel releases and
> looks like I couldn't figure out what's going wrong.
>
> I tried to test things with the latest kernel and they seem to be working fine.
> Atleast on my ARM board.
>
> Would it be possible for you to do a git bisect between 3.8 and 3.11 ?
We just tested with the latest release (14.04) and realized that the
issue was already fixed for the latest kernel version, sorry about that!
https://lkml.org/lkml/2013/9/7/119
Thanks anyways for your support :-)
> --
> viresh
prev parent reply other threads:[~2014-05-05 12:08 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
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 [this message]
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=53677F29.2090905@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.