public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Dave Jones <davej@redhat.com>,
	"Justin P. Mattock" <justinmattock@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: cat /proc/cpuinfo shows full throttle
Date: Fri, 23 Jan 2009 14:30:22 -0800	[thread overview]
Message-ID: <497A44FE.2040905@gmail.com> (raw)
In-Reply-To: <20090123193601.GB1295@redhat.com>

Dave Jones wrote:
> On Fri, Jan 23, 2009 at 01:27:39AM -0800, Justin P. Mattock wrote:
>
>  > I'm confused here  when doing a cat /proc/cpuinfo
>  > with an idle system, I see cpu MHz at 2167.000;
>  > should be at 1000.00 (when settled down);
>  >  ..
>  > 
>  > In any case the system is idle and quiet.
>  > it just says full throttle when it should say
>  > nice and quiet.
>  
> is acpi-cpufreq loaded ? and cpufreq-ondemand ?
> (Also make sure the relevant sysfs knobs are set to use ondemand)
>
> If no: Make them so!
> If yes: boot with cpufreq.debug=7 and send the dmesg
>  to cpufreq@vger.kernel.org
>
> Thanks,
>
> 	Dave
>
>   
I've managed to have cat /proc/cpuinfo
read correctly. somewhere somehow
when compiling xserver I Installed
some package that messed up libpowersaved11
and liblazy1. reinstalling those packages as well
as the other powersaved packages seems to have resolved this
issue for me.(as well as haveing  cpufreq running correctly);

I just can't remember what might the package be that
caused this to go crazy.(oh-well);
as long as the fans aren't screaming/or stuck I'm happy...

regards;

Justin P. Mattock

      reply	other threads:[~2009-01-23 22:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23  9:27 cat /proc/cpuinfo shows full throttle Justin P. Mattock
2009-01-23 19:36 ` Dave Jones
2009-01-23 22:30   ` Justin P. Mattock [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=497A44FE.2040905@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox