From: Arjan van de Ven <arjan@infradead.org>
To: Dimitrios Apostolou <jimis@gmx.net>
Cc: Len Brown <lenb@kernel.org>,
Wojciech Ploskonka <wploskonka@gmail.com>,
thomas@archlinux.org, Andrew Morton <akpm@linux-foundation.org>,
Alex Chiang <achiang@hp.com>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Yinghai Lu <yinghai@kernel.org>,
linux-kernel@vger.kernel.org, mie.iscrizioni@gmail.com
Subject: Re: High cpu temperature with 2.6.32, bisection shows commit 69d258 (fwd)
Date: Mon, 22 Feb 2010 17:55:29 -0800 [thread overview]
Message-ID: <20100222175529.13ae0565@infradead.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1002221836060.15882@localhost.localdomain>
On Mon, 22 Feb 2010 18:43:50 +0200 (EET)
Dimitrios Apostolou <jimis@gmx.net> wrote:
> Hi Arjan, Len,
>
> It seems that another user of archlinux (mie.iscrizioni CC'd) is
> having the same problem, and this time I can't see any PME+ flag in
> lspci output. The bug report is at [1] but since it's getting too big
> perhaps you want to take a look at attachment [2], which includes
> "powertop -d", "dmidecode" and "lspci -vvv" output.
>
> BTW, the common denominator for all these cases is the message
> "Marking TSC unstable due to TSC halts in idle". So I was thinking
> perhaps the code that detects the bug is already there! What do you
> think?
every single Intel and AMD cpu prior to the latest generation will spew
that message....
next prev parent reply other threads:[~2010-02-23 1:53 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
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 [this message]
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=20100222175529.13ae0565@infradead.org \
--to=arjan@infradead.org \
--cc=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=jimis@gmx.net \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mie.iscrizioni@gmail.com \
--cc=thomas@archlinux.org \
--cc=wploskonka@gmail.com \
--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®