From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dominik Brodowski Subject: Re: Weird behaviour (cpufreq-2.4.21-2) Date: Tue, 22 Jul 2003 14:13:55 +0200 Sender: cpufreq-admin@www.linux.org.uk Message-ID: <20030722121355.GC1964@brodo.de> References: <20030719003302.1664a98f.frx@firenze.linux.it> <20030719064528.GA1658@brodo.de> <20030722011220.2905e9e0.frx@firenze.linux.it> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20030722011220.2905e9e0.frx@firenze.linux.it> Errors-To: cpufreq-admin@www.linux.org.uk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Francesco Poli Cc: CpuFreq 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