All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Henning Gerdes <mail@dirk-gerdes.de>
To: sander@humilis.net
Cc: Willy Tarreau <willy@w.ods.org>,
	Caroline GAUDREAU <caroline.gaudreau.1@ens.etsmtl.ca>,
	linux-kernel@vger.kernel.org, coywolf@gmail.com
Subject: Re: bugs?
Date: Wed, 14 Dec 2005 12:32:27 +0100	[thread overview]
Message-ID: <1134559947.8885.8.camel@noti> (raw)
In-Reply-To: <20051214105723.GA25166@favonius>

Hallo!

You could try:
  
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor 

It's possible that you have chosen "power_save".
You can see possible settings in 

sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors

Try "performance"!
Then you should get your 1,4 GHz.
But be aware, that this is not powersaving!
Maybe you can play around with it.
A good possibility is to install an userspace application for governing
the cpu-speed lik cpufreqd



Dirk


Am Mittwoch, den 14.12.2005, 11:57 +0100 schrieb Sander:
> Willy Tarreau wrote (ao):
> > On Tue, Dec 13, 2005 at 08:47:58PM -0500, Caroline GAUDREAU wrote:
> > > my cpu is 1400MHz, but why there's cpu MHz         : 598.593
> > > 
> > > caro@olymphe:~$ cat /proc/cpuinfo
> > > processor       : 0
> > > vendor_id       : GenuineIntel
> > > cpu family      : 6
> > > model           : 9
> > > model name      : Intel(R) Pentium(R) M processor 1400MHz
> > > stepping        : 5
> > > cpu MHz         : 598.593
> > > cache size      : 1024 KB
> > 
> > It's probably a notebook that you started unplugged from the mains
> > power. Mine is stupid enough to believe that I *want* to save power if
> > I plug the mains *after* powering it up ! And there's no way to force
> > it to switch from 600 to nominal freq afterwards ! So I have to
> > connect it to the mains first.
> 
> If you say this based on 'cat /proc/cpuinfo' output: isn't it true that
> /proc/cpuinfo is static, and doesn't necessarily reflect the actual
> speed of the processor?
> 
-- 
Dirk Henning Gerdes
Bönnersdyk 47
47803 Krefeld

Tel:  02151-755745
      0174-7776640
Mail: mail@dirk-gerdes.de


  parent reply	other threads:[~2005-12-14 11:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14  1:47 bugs? Caroline GAUDREAU
2005-12-14  2:10 ` bugs? Andrew Haninger
2005-12-14  2:14 ` bugs? Dmitry Torokhov
2005-12-14  3:02   ` bugs? Coywolf Qi Hunt
2005-12-14  2:24 ` bugs? Dave Jones
2005-12-14  3:03   ` bugs? Coywolf Qi Hunt
2005-12-14  3:25     ` bugs? Dave Jones
2005-12-14  2:43 ` bugs? Willy Tarreau
2005-12-14  3:05   ` bugs? Coywolf Qi Hunt
2005-12-14 10:57   ` bugs? Sander
2005-12-14 11:04     ` bugs? Arjan van de Ven
2005-12-14 11:32     ` Dirk Henning Gerdes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-14  4:30 bugs! Lucas Correia Villa Real
2004-05-14 23:14 ` bugs! Lucas Correia Villa Real
2004-05-15  2:12   ` bugs! Lucas Correia Villa Real
2003-08-17 20:46 Bugs? William Jared Roberts
2003-08-17 20:23 Bugs? William Jared Roberts
2003-08-17 19:22 Bugs? William Jared Roberts
2003-08-17 19:33 ` Bugs? Hans Reiser
2003-08-18  7:47   ` Bugs? Nikita Danilov
2003-08-17 19:16 Bugs? William Jared Roberts
2003-08-17  4:04 Bugs? Thomas Graham
2003-08-17 18:52 ` Bugs? Alex Zarochentsev
2003-08-17  6:54   ` Bugs? Thomas Graham

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=1134559947.8885.8.camel@noti \
    --to=mail@dirk-gerdes.de \
    --cc=caroline.gaudreau.1@ens.etsmtl.ca \
    --cc=coywolf@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sander@humilis.net \
    --cc=willy@w.ods.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.