public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Georg Schild <dangertools@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: cpu throttling powernow-k8 and acpi in kernel
Date: Mon, 03 Jan 2005 08:02:40 +0100	[thread overview]
Message-ID: <41D8EE10.3040003@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.60.0501022349340.4725@poirot.grange>


> skipped...
> 
> Try writing to sensors@stimpy.netroedge.com. I had a CPU-throttling 
> problem, when the CPU got throttled down without really getting hot - I 
> just had wrongly configured /etc/sensors.conf. Might be your problem too?

Would be happy if it were the sensors but i am not using them, a least 
not the ones lm-sensors can use. My temperature is shown via ACPI 
Thermal zone of the processor driver. Afaik ACPI does also regulate the 
fan-speed so it doesn't work proper without acpi-processor driver as 
mentionend in the first post. so i don't think that the different 
sensors in i2c have to do something with it. But thanks for response, 
good to know that others have similar problems, even if they are not the 
same ;) Anyone else an idea how to tell acpi that it has perhaps wrong 
values?. I remember that when i first used this laptop with linux the 
fan went off after some time but now the fan doesn't go off, at least i 
don't recognize it. this is just because acpi has too high temps and 
lets the fan cool down the cpu because of that (at least acpi thinks so 
;)). Thanks for every help


Georg Schild


  reply	other threads:[~2005-01-03  7:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-02 15:00 cpu throttling powernow-k8 and acpi in kernel Georg Schild
2005-01-02 22:53 ` Guennadi Liakhovetski
2005-01-03  7:02   ` Georg Schild [this message]
2005-01-03  9:42 ` Pavel Machek
2005-01-04 14:29   ` Georg Schild
2005-01-04 12:11 ` Georg Schild

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=41D8EE10.3040003@gmx.net \
    --to=dangertools@gmx.net \
    --cc=linux-kernel@vger.kernel.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