From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Mike Galbraith <efault@gmx.de>,
Arjan van de Ven <arjan@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
pranith-kumar_d@mentorg.com
Subject: Re: [patch] CFS scheduler, -v14
Date: Fri, 8 Jun 2007 01:29:25 +0300 [thread overview]
Message-ID: <200706080129.28487.caglar@pardus.org.tr> (raw)
In-Reply-To: <alpine.LFD.0.98.0706010829041.3957@woody.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 2215 bytes --]
Hi;
01 Haz 2007 Cum tarihinde, Linus Torvalds şunları yazmıştı:
> Has it been hot where you are lately? Is your fan working?
First of all sorry for late reply.
For a while İstanbul is not really hot [~26 C] :) and yes fans are/seems
working without a problem.
> Hardware that acts up under load is quite often thermal-related,
> especially if it starts happening during summer and didn't happen before
> that... ESPECIALLY the kinds of behaviours you see: the "sudden power-off"
> is the normal behaviour for a CPU that trips a critial overheating point,
> and the slowdown is also one normal response to overheating (CPU
> throttling).
According to ACPI output;
[caglar@zangetsu][~]> cat /proc/acpi/thermal_zone/THRM/*
<setting not supported>
cooling mode: passive
<polling disabled>
state: ok
temperature: 56 C
critical (S5): 105 C
passive: 95 C: tc1=1 tc2=5 tsp=10 devices=0xc20deec8
105 C is critical for that CPU, for a while (this is why i reply late) i'm
constantly monitoring the temprature under low and high load.
Its in 50-70 C interval in normal usage/idle and 80-100 C interval under high
load (compiling some applications, using cpuburn to test etc.), so seems it
can handle overheating issues
But digging the kern.log shows some strange values also;
May 24 10:39:23 localhost kernel: [ 0.000000] Detected 897.748 MHz
processor. <--- 2.6.21.2-CFS-v14
...
May 30 00:59:11 localhost kernel: [ 0.000000] Detected 898.726 MHz
processor. <--- 2.6.21.2-CFS-v15
...
Jun 1 02:09:44 localhost kernel: [ 0.000000] Detected 897.591 MHz
processor. <--- 2.6.21.3-CFS-v15
...
And according to same log these slowdowns occured after i compiled/installed
these kernel versions into system(cause these are the first appearence of
this versions in kern.log). So as you said it seems definetly a overheating
issue. I'll continue to test/monitor and report back if i can find anything.
Thanks!
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-07 22:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 12:06 [patch] CFS scheduler, -v14 Ingo Molnar
2007-05-23 19:39 ` Nicolas Mailhot
2007-05-23 19:57 ` Ingo Molnar
2007-05-23 20:02 ` Nicolas Mailhot
2007-05-24 6:42 ` Balbir Singh
2007-05-24 8:09 ` Ingo Molnar
2007-05-24 9:19 ` Balbir Singh
2007-05-24 17:25 ` Jeremy Fitzhardinge
2007-05-24 20:59 ` Ingo Molnar
2007-05-24 22:43 ` Jeremy Fitzhardinge
2007-05-25 12:46 ` Ingo Molnar
2007-05-25 16:45 ` Balbir Singh
2007-05-28 11:07 ` Ingo Molnar
2007-05-29 10:23 ` Balbir Singh
2007-06-05 7:57 ` Ingo Molnar
2007-05-29 10:19 ` Balbir Singh
2007-05-26 14:58 ` S.Çağlar Onur
2007-05-26 15:08 ` S.Çağlar Onur
2007-06-01 13:35 ` S.Çağlar Onur
2007-06-01 15:31 ` Linus Torvalds
2007-06-07 22:29 ` S.Çağlar Onur [this message]
2007-06-01 15:37 ` [OT] " Andreas Mohr
2007-05-27 2:49 ` Li Yu
2007-05-29 6:15 ` Ingo Molnar
2007-05-29 8:07 ` Ingo Molnar
2007-05-31 9:45 ` Li Yu
2007-05-31 9:53 ` Ingo Molnar
2007-06-01 7:16 ` Li Yu
2007-06-01 19:21 ` Ingo Molnar
2007-06-05 2:33 ` Li Yu
2007-06-05 8:01 ` Ingo Molnar
2007-06-05 8:54 ` Li Yu
2007-06-06 7:41 ` Li Yu
2007-06-05 3:35 ` Li Yu
2007-05-28 1:17 ` Li Yu
2007-05-29 0:49 ` Li Yu
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=200706080129.28487.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pranith-kumar_d@mentorg.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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