public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Mark Lord <lkml@rtr.ca>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: cpufreq stops working after a while
Date: Fri, 11 Aug 2006 17:01:04 -0400	[thread overview]
Message-ID: <20060811210104.GL26930@redhat.com> (raw)
In-Reply-To: <44DCEAF7.5020005@rtr.ca>

On Fri, Aug 11, 2006 at 04:39:19PM -0400, Mark Lord wrote:
 > Ahhh...
 > 
 > >From the trace, I see a bunch of "userspace" lines appearing.
 > And sure enough, something called "powernowd" is running,
 > and probably conflicting with the "ondemand" governor.

It'll override it, you can't run both at the same time.
Well, unless you have a dual-core/multi-cpu system, where you
could have a different governor per-core. But that would be loony,
and we should probably disallow that possibility before someone
gets any bright ideas.

Looking at your log however, you only have a single CPU, so it'll
be using userspace exclusively.

 > I'm nuking powernowd, and that'll probably cure it for this box.
 > I guess the distro (kubuntu) must have started "powernowd"
 > even though I told it (the distro) to use "ondemand".
 > 
 > Does it make sense that this could change the upper limit, though?

A userspace governor can pretty much invent its own rules. I'm not
familiar with what constraints powernowd has.  It may even have
limits defined in a config file someplace.

Is it behaving again with ondemand ?

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-08-11 21:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 19:55 cpufreq stops working after a while Pallipadi, Venkatesh
2006-08-11 20:29 ` Mark Lord
2006-08-11 20:39   ` Mark Lord
2006-08-11 21:01     ` Dave Jones [this message]
2006-08-11 21:09       ` Mark Lord
2006-08-11 21:15       ` Mark Lord
2006-08-11 21:17         ` Mark Lord
2006-08-11 21:25         ` Mark Lord
2006-08-18 15:11           ` Pavel Machek
2006-08-24 14:44             ` Mark Lord
2006-08-24 16:15               ` Matthew Garrett
  -- strict thread matches above, loose matches on Subject: below --
2006-08-11 22:18 Pallipadi, Venkatesh
2006-08-11 21:38 Pallipadi, Venkatesh
2006-08-11 21:53 ` Mark Lord
2006-08-11 21:08 Pallipadi, Venkatesh
2006-08-11 18:25 Mark Lord
2006-08-11 18:39 ` Dave Jones
2006-08-11 19:41   ` Mark Lord
2006-08-11 20:01     ` Mark Lord
2006-08-11 20:12       ` Dave Jones
2006-08-11 18:46 ` Andrew Morton
2006-08-11 19:01   ` Mark Lord
2006-08-11 19:10   ` Mark Lord
2006-08-11 19:18     ` Andrew Morton

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=20060811210104.GL26930@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --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