From: Robert Hancock <hancockr@shaw.ca>
To: akwatts@ymail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Thermal problems with newer kernels
Date: Wed, 28 Jan 2009 18:44:42 -0600 [thread overview]
Message-ID: <4980FBFA.1010402@shaw.ca> (raw)
In-Reply-To: <863288.78002.qm@web111002.mail.gq1.yahoo.com>
Andrew Watts wrote:
> Dear Kernel Gurus:
>
> Below is a problem that I am unable to explain along with relevant(?) info. Please let me know if I should provide additional debugging information. Thanks in advance for your assistance!
>
> -Andy
>
> [1] Problem: HP Pavilion zv5000 laptop idle temp is 17 degrees higher when running most recent kernels (57C versus 40C).
>
> [2] Brief Description
>
> Newer kernels (noticed starting with 2.6.27.3 but could have started anytime past 2.6.26.7) result in a much higher idle CPU temp. Physical temperature reading of exhaust from primary cooling fan and the regular triggering of secondary cooling fan confirms this (it is not a readout scaling issue). The kernels and temps below:
>
> 2.6.26.7 Idle temp 40C
> 2.6.27.3 Idle temp 57C
> 2.6.28 Idle temp 57C
>
> The only third party kernel module installed that is not part of the official kernel source is: madwifi-ng. However, the problem occurs even when this module is not loaded.
>
> The .config file used for the newer kernels was imported from the working 2.6.26.7 .config file.
CPU frequency scaling not working perhaps? What's your dmesg output from
bootup look like? Is the acpi-cpufreq driver being loaded?
next prev parent reply other threads:[~2009-01-29 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 21:14 Thermal problems with newer kernels Andrew Watts
2009-01-29 0:44 ` Robert Hancock [this message]
2009-02-05 15:21 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2009-01-31 8:06 Andrew Watts
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=4980FBFA.1010402@shaw.ca \
--to=hancockr@shaw.ca \
--cc=akwatts@ymail.com \
--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 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.