From: Sander <sander@humilis.net>
To: Willy Tarreau <willy@w.ods.org>
Cc: Caroline GAUDREAU <caroline.gaudreau.1@ens.etsmtl.ca>,
linux-kernel@vger.kernel.org, coywolf@gmail.com
Subject: Re: bugs?
Date: Wed, 14 Dec 2005 11:57:23 +0100 [thread overview]
Message-ID: <20051214105723.GA25166@favonius> (raw)
In-Reply-To: <20051214024316.GG15993@alpha.home.local>
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?
--
Humilis IT Services and Solutions
http://www.humilis.net
next prev parent reply other threads:[~2005-12-14 10:57 UTC|newest]
Thread overview: 12+ 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 ` Sander [this message]
2005-12-14 11:04 ` bugs? Arjan van de Ven
2005-12-14 11:32 ` bugs? Dirk Henning Gerdes
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=20051214105723.GA25166@favonius \
--to=sander@humilis.net \
--cc=caroline.gaudreau.1@ens.etsmtl.ca \
--cc=coywolf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox