From: Dimitrios Apostolou <jimis@gmx.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alex Chiang <achiang@hp.com>, Len Brown <lenb@kernel.org>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Yinghai Lu <yinghai@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: High cpu temperature with 2.6.32, bisection shows commit 69d258 (fwd)
Date: Wed, 10 Feb 2010 22:51:38 +0200 (EET) [thread overview]
Message-ID: <alpine.LNX.2.00.1002102245200.1675@localhost.localdomain> (raw)
In-Reply-To: <20100112213205.7d74808a@infradead.org>
Hi Arjan,
it seems that the changes inside processor module have bitten another
user, see relevant thread at archlinux bugtracker:
http://bugs.archlinux.org/task/17771
It can be summarised with the following quote:
I've tested jimis's suggestion about booting with init=/bin/sh and later
modprobing next modules.
I confirm that module called "processor" in any kernel26 2.6.32.* is a
root problem of high power consumption.
Here's output of modprobing it:
ACPI: SSDT 000000003f6d94fb 00238 (v01 PmRef Cpu0Ist 000003000 INTL
20050624)
ACPI: SSDT 000000003f6d8e8c 005EA (v01 PmRef Cpu0Cst 000003001 INTL
20050624)
Marking TSC unstable due to TSC halts in idle
processor LNXCPU:00: registered as cooling_device0
ACPI: SSDT 000000003f6d9733 000C8(v01 PmRef Cpu1Ist 000003000 INTL
20050624)
ACPI: SSDT 00000000376d9476 00085 (v01 PmRef Cpu1Cst 000003000 INTL
20050624)
Swtiching to clocksource hpet
processor LNXCPU:01: registered as cooling_device1
As I understand, in his case the C3 state is unstable and exits
immediately. I have asked him to post the dmidecode output so you can put
him on the exception list too. However I now believe that more and more
users will be facing the same problem, it's not something you find easily,
especially on desktop machines! What do you think?
Thanks,
Dimitris
next prev parent reply other threads:[~2010-02-10 20:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LNX.2.00.1001071941470.1363@localhost.localdomain>
2010-01-08 17:15 ` Alex Chiang
2010-01-09 21:43 ` Arjan van de Ven
2010-01-09 23:55 ` Dimitrios Apostolou
2010-01-10 0:08 ` Arjan van de Ven
2010-01-10 0:32 ` Dimitrios Apostolou
2010-01-10 0:42 ` Arjan van de Ven
2010-01-10 1:05 ` Dimitrios Apostolou
2010-01-10 1:38 ` Arjan van de Ven
2010-01-13 0:07 ` Andrew Morton
2010-01-13 5:32 ` Arjan van de Ven
2010-02-10 20:51 ` Dimitrios Apostolou [this message]
2010-02-10 21:42 ` Dimitrios Apostolou
2010-02-11 4:56 ` Arjan van de Ven
2010-02-11 18:00 ` Dimitrios Apostolou
2010-02-11 21:58 ` Wojciech Ploskonka
2010-02-12 5:24 ` Arjan van de Ven
2010-02-12 21:05 ` Matthew Garrett
2010-02-18 20:27 ` Dimitrios Apostolou
2010-02-18 20:34 ` Rafael J. Wysocki
2010-02-22 16:43 ` Dimitrios Apostolou
2010-02-23 1:55 ` Arjan van de Ven
2010-02-12 5:23 ` Arjan van de Ven
2010-01-10 2:07 ` Ray Lee
2010-01-10 3:09 ` Robert Hancock
2010-01-10 4:15 ` Arjan van de Ven
2010-01-15 20:00 ` -O0 kernel " Pavel Machek
2010-01-15 20:40 ` Dimitrios Apostolou
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=alpine.LNX.2.00.1002102245200.1675@localhost.localdomain \
--to=jimis@gmx.net \
--cc=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=bjorn.helgaas@hp.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yinghai@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
all inboxes | Powered by JetHome®