From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Dave Jones <davej@redhat.com>,
pjones@redhat.com, cpufreq@lists.linux.org.uk
Subject: Re: ondemand vs suspend.
Date: Wed, 28 Jun 2006 15:20:36 -0700 [thread overview]
Message-ID: <44A300B4.8050202@goop.org> (raw)
In-Reply-To: <EB12A50964762B4D8111D55B764A84541D4F8C@scsmsx413.amr.corp.intel.com>
Pallipadi, Venkatesh wrote:
> Strange. I guess only scaling_max_freq is changing and not
> cpuinfo_max_freq. Right?
> Can you try stopping the applet and see whether anything changes?
> Is the system idle while these changes happen or the load is varying
> causing some frequency changes by conservative on CPU 0?
>
> I am not able to reproduce this with periodic reading of
> scaling_cur_freq. May be soemthing else is happening from userlevel that
> is causing this..
>
Sorry, I haven't got around to looking at this closely again. However,
the behaviour with 2.6.17-mm3 has changed a bit. Now on resume, the
cpufreq applets exit for some reason, and both CPUs end up with a max
speed of 1GHz.
> Can you enable cpufreq.debug and capture the log.
>
Will do.
J
next prev parent reply other threads:[~2006-06-28 22:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 22:12 ondemand vs suspend Pallipadi, Venkatesh
2006-06-28 22:20 ` Jeremy Fitzhardinge [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-26 20:24 Pallipadi, Venkatesh
2006-06-26 20:58 ` Jeremy Fitzhardinge
2006-06-26 18:43 Pallipadi, Venkatesh
2006-06-26 19:23 ` Jeremy Fitzhardinge
2006-06-14 2:50 Pallipadi, Venkatesh
2006-06-14 3:08 ` Peter Jones
2006-06-19 22:52 ` Jeremy Fitzhardinge
2006-06-21 18:54 ` Venkatesh Pallipadi
2006-06-21 21:01 ` Jeremy Fitzhardinge
2006-06-23 22:45 ` Jeremy Fitzhardinge
2006-06-21 18:35 ` Venkatesh Pallipadi
2006-06-13 23:03 Pallipadi, Venkatesh
2006-06-13 23:06 ` Dave Jones
2006-06-13 20:53 Dave Jones
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=44A300B4.8050202@goop.org \
--to=jeremy@goop.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=pjones@redhat.com \
--cc=venkatesh.pallipadi@intel.com \
/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