From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
Cc: ross@datscreative.com.au, Len Brown <len.brown@intel.com>,
Thomas Schlichter <thomas.schlichter@web.de>,
linux-kernel@vger.kernel.org
Subject: Re: idle Athlon with IOAPIC is 10C warmer since 2.6.3-bk1
Date: Mon, 29 Mar 2004 21:59:55 +0200 [thread overview]
Message-ID: <4068803B.5010208@gmx.de> (raw)
In-Reply-To: <405C1C0D.9050108@gmx.de>
Prakash K. Cheemplavam wrote:
> Ross Dickson wrote:
>
>> On Saturday 20 March 2004 19:29, Prakash K. Cheemplavam wrote:
>>
>>> Len Brown wrote:
>>>
>>>> On Fri, 2004-03-19 at 14:22, Prakash K. Cheemplavam wrote:
>>>>
>>>>
>>>>
>>>>> Hmm, I just did a cat /proc/acpi/processor/CPU0/power:
>>>>> active state: C1
>>>>> default state: C1
>>>>> bus master activity: 00000000
>>>>> states:
>>>>> *C1: promotion[--] demotion[--] latency[000]
>>>>> usage[00000000]
>>>>> C2: <not supported>
>>>>> C3: <not supported>
>>>>>
>>>>> I am currently NOT using APIC mode (nforce2, as well) and using
>>>>> vanilla 2.6.4. It seems C1 halt state isn't used, which exlains why
>>>>> I am having
>>>
>>>
>>> [snip]
>>>
>>>>
>>>> Actually I think it is that we don't _count_ C1 usage.
>>>
>>>
>>> Hmm, OK, then I am really puzzled what specifically about mm sources
>>> make my idle temps hotter, as I still couldn't properly resolve it
>>> what is causing it. I thought ACPI, but no, using APM only does the
>>> same (apm only with vanilla is low temp though.)
>>
>>
>>
>> Have you seen this thread, it may be relevant?
>> Re: [2.6.4-rc2] bogus semicolon behind if()
>> http://linux.derkeiler.com/Mailing-Lists/Kernel/2004-03/4170.html
>
>
So, I seem to have found the bugger causing higher temps: It is NVidia
binary driver, or rather its AGP part of the 53.36 driver. Using AGPGART
and Nvidia driver leaves my system cool. Using NVAGP it seems as though
C1 state isn't actually used anymore thus making the CPU hotter.
Tested with (and without) ACPI and APIC (and Ross' tack patch).
Currently running in PIC mode (with ACPI) and idle temp of 44°C (instead
of about 50°C...). But it was as cool in APIC mode.
Of course I have to test few more days, but at least currently I am
happy again. :-)
Prakash
next prev parent reply other threads:[~2004-03-29 20:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 0:19 idle Athlon with IOAPIC is 10C warmer since 2.6.3-bk1 Ross Dickson
2004-03-18 1:02 ` Craig Bradney
2004-03-18 11:41 ` Bernd Schubert
2004-03-18 11:55 ` Ross Dickson
2004-03-19 18:55 ` Thomas Schlichter
2004-03-19 19:22 ` Prakash K. Cheemplavam
2004-03-19 23:20 ` Len Brown
2004-03-20 9:29 ` Prakash K. Cheemplavam
2004-03-20 10:19 ` Ross Dickson
2004-03-20 10:25 ` Prakash K. Cheemplavam
2004-03-20 10:50 ` Ross Dickson
2004-03-29 19:59 ` Prakash K. Cheemplavam [this message]
2004-03-30 0:57 ` Ross Dickson
2004-03-30 9:30 ` Prakash K. Cheemplavam
2004-03-20 13:07 ` Daniel Egger
-- strict thread matches above, loose matches on Subject: below --
2004-03-17 21:26 Thomas Schlichter
[not found] <A6974D8E5F98D511BB910002A50A6647615F571D@hdsmsx402.hd.intel.com>
2004-03-17 15:53 ` Len Brown
[not found] <200403032119.58817.thomas.schlichter@web.de>
2004-03-17 15:29 ` Maciej W. Rozycki
2004-03-04 12:47 Thomas Schlichter
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=4068803B.5010208@gmx.de \
--to=prakashkc@gmx.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ross@datscreative.com.au \
--cc=thomas.schlichter@web.de \
/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