From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.4-rc1-mm1, as scheduler causes higher idle temp?
Date: Tue, 02 Mar 2004 21:45:18 +0100 [thread overview]
Message-ID: <4044F25E.3010802@gmx.de> (raw)
In-Reply-To: <40448E60.5020403@gmx.de>
Prakash K. Cheemplavam wrote:
> 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. :-)
Ok, its me again. So now I was running 2.6.4-rc1-mm1 today and the
rratic behaviour came again, ie, idle temps went high. Strange enough
this only happens after some time.
Comparing dmesg from both, I see this as major differnece: With latest
mm-source the as scheduler gets used, though I set elevator=cfq in the
kernel line. So either you removed cfq or it doesn't get selcted and
maybe anticipatory causes the temp rise?
Well, I will test as scheduler with 2.6.3-mm4 tomorrow and report back
Prakash
PS: here the diff between the dmesgs:
--- dmesg2.6.3-mm4.txt 2004-03-02 21:40:07.359583984 +0100
+++ dmesg2.6.4-rc1-mm1.txt 2004-03-02 09:59:49.000000000 +0100
@@ -1,4 +1,4 @@
-Linux version 2.6.3-mm4 (root@tachyon) (gcc-Version 3.3.3 20040217
(Gentoo Linux 3.3.3, propolice-3.3-7)) #12 Tue Mar 2 09:39:12 CET 2004
+Linux version 2.6.4-rc1 (root@tachyon) (gcc-Version 3.3.3 20040217
(Gentoo Linux 3.3.3, propolice-3.3-7)) #3 Tue Mar 2 09:58:07 CET 2004
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
@@ -11,7 +11,6 @@
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
127MB HIGHMEM available.
896MB LOWMEM available.
-zapping low mappings.
On node 0 totalpages: 262128
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 225280 pages, LIFO batch:16
@@ -24,14 +23,15 @@
ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: PM-Timer IO Port: 0x4008
Built 1 zonelists
-Initializing CPU#0
Kernel command line: root=/dev/hde7 quiet apic_tack=2 elevator=cfq
doataraid noraid hdg=none
ide_setup: hdg=none
+Initializing CPU#0
PID hash table entries: 4096 (order 12: 32768 bytes)
-Detected 2205.190 MHz processor.
+Detected 2204.949 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
-Memory: 1033100k/1048512k available (2555k kernel code, 14492k
reserved, 862k data, 136k init, 131008k highmem)
+Memory: 1033144k/1048512k available (2527k kernel code, 14448k
reserved, 861k data, 136k init, 131008k highmem)
+Checking if this processor honours the WP bit even in supervisor
mode... Ok.
Calibrating delay loop... 4358.14 BogoMIPS
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
@@ -117,13 +117,13 @@
ACPI: Power Button (FF) [PWRF]
ACPI: Fan [FAN] (on)
ACPI: Processor [CPU0] (supports C1)
-ACPI: Thermal Zone [THRM] (48 C)
+ACPI: Thermal Zone [THRM] (46 C)
Real Time Clock Driver v1.12
Non-volatile memory driver v1.2
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
-Using cfq io scheduler
+Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
loop: loaded (max 8 devices)
@@ -179,8 +179,8 @@
i2c_adapter i2c-2: nForce2 SMBus adapter at 0x5100
Advanced Linux Sound Architecture Driver Version 1.0.2c (Thu Feb 05
15:41:49 2004 UTC).
PCI: Setting latency timer of device 0000:00:06.0 to 64
-intel8x0_measure_ac97_clock: measured 49398 usecs
-intel8x0: clocking to 47423
+intel8x0_measure_ac97_clock: measured 49397 usecs
+intel8x0: clocking to 47422
ALSA device list:
#0: NVidia nForce2 at 0xdc081000, irq 10
NET: Registered protocol family 2
@@ -226,6 +226,7 @@
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[11]
MMIO=[dc084000-dc0847ff] Max Packet=[2048]
ohci1394: fw-host0: SelfID received outside of bus reset sequence
ieee1394: Host added: ID:BUS[0-00:1023] GUID[000000508df0fbe3]
+svc: unknown version (3)
nvidia: no version magic, tainting kernel.
nvidia: module license 'NVIDIA' taints kernel.
0: nvidia: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-5336
Wed Jan 14 18:29:26 PST 2004
next prev parent reply other threads:[~2004-03-02 20:45 UTC|newest]
Thread overview: 21+ 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 ` 2.6.4-rc1-mm1 Prakash K. Cheemplavam
2004-03-02 20:45 ` Prakash K. Cheemplavam [this message]
2004-03-02 21:11 ` 2.6.4-rc1-mm1, as scheduler causes higher idle temp? Andrew Morton
2004-03-02 21:39 ` Prakash K. Cheemplavam
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=4044F25E.3010802@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