From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Wojciech Ploskonka <wploskonka@gmail.com>,
Dimitrios Apostolou <jimis@gmx.net>,
thomas@archlinux.org, 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: Fri, 12 Feb 2010 21:05:40 +0000 [thread overview]
Message-ID: <20100212210540.GA25752@srcf.ucam.org> (raw)
In-Reply-To: <20100211212415.2eace0c2@infradead.org>
On Thu, Feb 11, 2010 at 09:24:15PM -0800, Arjan van de Ven wrote:
> On Thu, 11 Feb 2010 22:58:21 +0100
> Wojciech Ploskonka <wploskonka@gmail.com> wrote:
>
> > 08:06.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394
> > Controller (rev 05) (prog-if 10 [OHCI])
>
> 08:06.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
> (rev 05) (prog-if 10 [OHCI])
>
> is the one having PME+ set.
>
> Len: how do we handle PME's again?
Right now, nothing enables the GPE they're connected to and so they're
entirely irrelevant.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-02-12 21:06 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 ` High cpu temperature with 2.6.32, bisection shows commit 69d258 (fwd) 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 [this message]
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=20100212210540.GA25752@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=bjorn.helgaas@hp.com \
--cc=jimis@gmx.net \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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