From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: unlisted-recipients:; (no To-header on input)
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.4-rc1-mm1
Date: Tue, 02 Mar 2004 14:38:40 +0100 [thread overview]
Message-ID: <40448E60.5020403@gmx.de> (raw)
In-Reply-To: <404367C2.3050109@gmx.de>
Prakash K. Cheemplavam wrote:
> has anything changed with C1 halt? I mean it seems that CPU Disconnect
> doesn't get called (Though I enabled it), as with 2.6.3-mm4 (yesterday
> and today going back) my idle temps are about 46-47°C. Now with
> 2.6.4-mm1 they went up to 50-52°C.
Hmm, today I went back to 2.6.4-rc1-mm1 and everything seems to be
normal again. Strange... So forget about it. :-)
Prakash
next prev parent reply other threads:[~2004-03-02 13:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 22:06 2.6.4-rc1-mm1 Andrew Morton
2004-02-29 22:24 ` 2.6.4-rc1-mm1 Christoph Hellwig
2004-02-29 22:31 ` 2.6.4-rc1-mm1 Andrew Morton
2004-03-02 13:52 ` 2.6.4-rc1-mm1 bill davidsen
2004-03-01 1:02 ` 2.6.4-rc1-mm1 Nick Piggin
2004-03-01 1:14 ` 2.6.4-rc1-mm1 Andrew Morton
2004-03-01 1:30 ` 2.6.4-rc1-mm1 Nick Piggin
2004-03-01 1:45 ` 2.6.4-rc1-mm1 Nick Piggin
2004-03-01 2:05 ` 2.6.4-rc1-mm1 Andrew Morton
2004-03-01 1:10 ` 2.6.4-rc1-mm1: multiple definitions of `debug' Adrian Bunk
2004-03-01 1:41 ` Andrew Morton
2004-03-01 17:49 ` Torrey Hoffman
2004-03-01 1:39 ` 2.6.4-rc1-mm1 Marc-Christian Petersen
2004-03-01 1:46 ` 2.6.4-rc1-mm1 Marc-Christian Petersen
2004-03-01 11:26 ` posix message queues, was 2.6.4-rc1-mm1 bert hubert
2004-03-01 14:27 ` Krzysztof Benedyczak
2004-03-01 16:41 ` 2.6.4-rc1-mm1 Prakash K. Cheemplavam
2004-03-02 13:38 ` Prakash K. Cheemplavam [this message]
2004-03-02 20:45 ` 2.6.4-rc1-mm1, as scheduler causes higher idle temp? Prakash K. Cheemplavam
2004-03-02 21:11 ` Andrew Morton
2004-03-02 21:39 ` Prakash K. Cheemplavam
-- strict thread matches above, loose matches on Subject: below --
2004-03-02 0:20 2.6.4-rc1-mm1 Pedro Larroy
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=40448E60.5020403@gmx.de \
--to=prakashkc@gmx.de \
--cc=akpm@osdl.org \
--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