All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Poli <frx@firenze.linux.it>
To: CpuFreq <cpufreq@www.linux.org.uk>
Subject: Re: Weird behaviour (cpufreq-2.4.21-2)
Date: Tue, 22 Jul 2003 01:12:20 +0200	[thread overview]
Message-ID: <20030722011220.2905e9e0.frx@firenze.linux.it> (raw)
In-Reply-To: <20030719064528.GA1658@brodo.de>

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)


# alias ETEMP='cat /proc/acpi/thermal_zone/THRM/temperature'
# ETEMP
temperature:             62 C
# ETEMP
temperature:             62 C
# cat /proc/cpufreq
          minimum CPU frequency  -  maximum CPU frequency  -  policy
CPU  0       500000 kHz ( 35 %)  -    1400000 kHz (100 %)  - 
performance# ETEMP
temperature:             62 C
# on_ac_power
# echo $?
0
# on_ac_power
# echo $?
1
# ETEMP
temperature:             62 C
# bogomips
Calibrating delay loop.. ok - 1394.00 BogoMips
# on_ac_power
# echo $?
0
# ETEMP
temperature:             78 C
# ETEMP
temperature:             79 C
# bogomips
Calibrating delay loop.. ok - 1394.00 BogoMips
# ETEMP
temperature:             76 C
# bogomips
Calibrating delay loop.. ok - 1394.00 BogoMips
# ETEMP
temperature:             75 C
# ETEMP
temperature:             74 C
# ETEMP
temperature:             74 C
# bogomips
Calibrating delay loop.. ok - 1394.00 BogoMips
# ETEMP
temperature:             73 C
# ETEMP
temperature:             73 C
# ETEMP
temperature:             73 C
# ETEMP
temperature:             72 C
# bogomips 
Calibrating delay loop.. ok - 1384.00 BogoMips
# ETEMP
temperature:             73 C
# ETEMP
temperature:             72 C
# ETEMP
temperature:             72 C
# ETEMP
temperature:             72 C


It seems that the CPU clock frequency stays pretty fixed, doesn't it?

Any ideas?

-- 
    Francesco Poli       <frx AT firenze.linux.it>
======================================================
You're compiling a program and, all of a sudden, boom!
  -- from APT HOWTO, version 1.8.0

  reply	other threads:[~2003-07-21 23:12 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 [this message]
2003-07-22 12:13     ` Dominik Brodowski
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=20030722011220.2905e9e0.frx@firenze.linux.it \
    --to=frx@firenze.linux.it \
    --cc=cpufreq@www.linux.org.uk \
    /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.