All of
 help / color / mirror / Atom feed
From: Francesco Poli <>
To: CpuFreq <>
Subject: Weird behaviour (cpufreq-2.4.21-2)
Date: Sat, 19 Jul 2003 00:33:02 +0200	[thread overview]
Message-ID: <> (raw)

Hello everybody!  :)
I installed a 2.4.21 kernel + cpufreq-2.4.21-2 (downloaded
from + acpi-20030619-2.4.21
(downloaded from on an Acer Aspire 1302XV
(AMD Mobile Athlon XP 1600+). I manually fixed the vid-fid bug in
powernow-k7.c (as reminded by Carl Thompson in a recent post), activated
the ACPI-related configuration options, compiled and installed.

Here comes the weird!

When I boot all seems right. The CPU is almost 100% idle and
$ cat /proc/cpufreq
          minimum CPU frequency  -  maximum CPU frequency  -  policy
CPU  0       500000 kHz ( 35 %)  -    1400000 kHz (100 %)  - 
performance$ cat /proc/acpi/thermal_zone/THRM/temperature
temperature:              60 C
And this seems to be able to go on (with temperature slowly

Then I disconnect the laptop from the electrical network: so I run on
When I go back on AC power, the battery starts charging (as reported by
the LED and by ACPI). And the temperature goes up towards 80 degrees
Celsius; the back fan wakes up thus pushing the temperature down again
to 69 degrees Celsius; then the fan rests and the temperature goes up
again. This thermal cycle goes on and on, even if the CPU is almost
totally idle.

A simple reboot stops this behaviour and, after a while, I get
$ cat /proc/acpi/thermal_zone/THRM/temperature
temperature:              57 C

The question is: what's wrong? What did I messed up with?

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

             reply	other threads:[~2003-07-18 22:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18 22:33 Francesco Poli [this message]
2003-07-19  6:45 ` Weird behaviour (cpufreq-2.4.21-2) Dominik Brodowski
2003-07-21 23:12   ` Francesco Poli
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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.