From: Dominik Brodowski <linux@brodo.de>
To: Francesco Poli <frx@firenze.linux.it>
Cc: CpuFreq <cpufreq@www.linux.org.uk>
Subject: Re: Weird behaviour (cpufreq-2.4.21-2)
Date: Tue, 22 Jul 2003 14:13:55 +0200 [thread overview]
Message-ID: <20030722121355.GC1964@brodo.de> (raw)
In-Reply-To: <20030722011220.2905e9e0.frx@firenze.linux.it>
On Tue, Jul 22, 2003 at 01:12:20AM +0200, Francesco Poli wrote:
> On Sat, 19 Jul 2003 08:45:28 +0200 Dominik Brodowski wrote:
>
> > > The question is: what's wrong? What did I messed up with?
> >
> > Hmmm... might it be that the BIOS meddles with the CPU frequency, too?
> > You could compare the output of the "bogomips" tool to detect
> > frequency changes, for example.
>
> Here's a session log (I used bogomips v1.2 from the Debian Woody
> sysutils package)
Thanks
> It seems that the CPU clock frequency stays pretty fixed, doesn't it?
Indeed. But, as others pointed out, it might be a non-cpufreq related
problem but more a "battery loading" one. At least, I cannot see why there
should be any additional heat generation by cpufreq as the frequency doesn't
change at all...
Dominik
next prev parent reply other threads:[~2003-07-22 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 22:33 Weird behaviour (cpufreq-2.4.21-2) Francesco Poli
2003-07-19 6:45 ` Dominik Brodowski
2003-07-21 23:12 ` Francesco Poli
2003-07-22 12:13 ` Dominik Brodowski [this message]
2003-07-19 16:18 ` David
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=20030722121355.GC1964@brodo.de \
--to=linux@brodo.de \
--cc=cpufreq@www.linux.org.uk \
--cc=frx@firenze.linux.it \
/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