From: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Dave Jones <davej@redhat.com>,
cpufreq@lists.linux.org.uk, pjones@redhat.com
Subject: Re: ondemand vs suspend.
Date: Wed, 21 Jun 2006 11:54:13 -0700 [thread overview]
Message-ID: <20060621115413.A16324@unix-os.sc.intel.com> (raw)
In-Reply-To: <44972ACB.2040609@goop.org>; from jeremy@goop.org on Mon, Jun 19, 2006 at 03:52:59PM -0700
On Mon, Jun 19, 2006 at 03:52:59PM -0700, Jeremy Fitzhardinge wrote:
> Pallipadi, Venkatesh wrote:
> > Yes. I am able to reproduce this 2.6.17-rc6 and trying to narrow it
> > down.
> >
> > Also, there is a known issue with ondemand and resuming anyway as the
> > second CPU will not be able to resume with ondemand, but instead will go
> > back to 'default' governor on initialization.
> > So, even with this bug fixed, we cannot suspend-resume with ondemand
> > governor. Workaround for now can be just to switch to default governor
> > before suspend and go back to ondemand after resume, using initscripts.
> >
> I've noticed another problem, which may be related. Sometimes after
> resume, cpufreq seems to lose the ability to control the CPU speeds:
> they stay at the lowest performance level, and don't change regardless
> of what governor I set. I'm seeing this on a T2400 Core Duo. I'm not
> sure if this is a speedfreq-centrino problem or cpufreq itself.
>
> J
Does it only happen on CPU 1 or both the CPUs? What does /sys/.../cpufreq
look like once you get to this stuck at lowest freq state? Does
scaling_available_frequencies still show all the freqs.
Thanks,
Venki
next prev parent reply other threads:[~2006-06-21 18:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 2:50 ondemand vs suspend Pallipadi, Venkatesh
2006-06-14 3:08 ` Peter Jones
2006-06-19 22:52 ` Jeremy Fitzhardinge
2006-06-21 18:54 ` Venkatesh Pallipadi [this message]
2006-06-21 21:01 ` Jeremy Fitzhardinge
2006-06-23 22:45 ` Jeremy Fitzhardinge
2006-06-21 18:35 ` Venkatesh Pallipadi
-- strict thread matches above, loose matches on Subject: below --
2006-06-26 22:12 Pallipadi, Venkatesh
2006-06-28 22:20 ` Jeremy Fitzhardinge
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-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=20060621115413.A16324@unix-os.sc.intel.com \
--to=venkatesh.pallipadi@intel.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=jeremy@goop.org \
--cc=pjones@redhat.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