From: Peter Jones <pjones@redhat.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Dave Jones <davej@redhat.com>, cpufreq@lists.linux.org.uk
Subject: RE: ondemand vs suspend.
Date: Tue, 13 Jun 2006 23:08:42 -0400 [thread overview]
Message-ID: <1150254522.16845.20.camel@localhost.localdomain> (raw)
In-Reply-To: <EB12A50964762B4D8111D55B764A8454110B16@scsmsx413.amr.corp.intel.com>
On Tue, 2006-06-13 at 19:50 -0700, 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.
Yeah, that's what I implemented for our pm utils earlier today.
--
Peter
next prev parent reply other threads:[~2006-06-14 3:08 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 [this message]
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
-- 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=1150254522.16845.20.camel@localhost.localdomain \
--to=pjones@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@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