From: =?unknown-8bit?q?=C3=93scar?= Fuentes <ofv@wanadoo.es>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Does this makes any sense?
Date: Sun, 28 Sep 2008 20:22:50 +0000 [thread overview]
Message-ID: <4p40uijp.fsf@telefonica.net> (raw)
This is not a problem with lm-sensors, but an attempt to understand
what can cause the values it outputs.
When I start four mprime processes in "torture test" mode on a Q6600
system it shows a flat 100% CPU usage line and `sensors` report
temperatures around or below 70 degrees Celsius for each core, which
is consistent with Intel's specs for a fully loaded CPU:
oscar@qcore:~/Archivo/prime$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +73.0°C (crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +71.0°C (crit = +100.0°C)
coretemp-isa-0002
Adapter: ISA adapter
Core 2: +62.0°C (crit = +100.0°C)
coretemp-isa-0003
Adapter: ISA adapter
Core 3: +58.0°C (crit = +100.0°C)
However, when compiling an application with "make -j 4" the CPU usage
is around 95% (which is expected as there is quite a bit of I/O
involved) but the temperature goes up to 88 degrees on some cores!
This is a typical output of `sensors` on this scenario:
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +85.0°C (crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +82.0°C (crit = +100.0°C)
coretemp-isa-0002
Adapter: ISA adapter
Core 2: +71.0°C (crit = +100.0°C)
coretemp-isa-0003
Adapter: ISA adapter
Core 3: +65.0°C (crit = +100.0°C)
What can cause this difference on temperatures, when mprime stresses
the CPU much more than the compiler?
--
Oscar
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next reply other threads:[~2008-09-28 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 20:22 =?unknown-8bit?q?=C3=93scar?= Fuentes [this message]
2008-09-28 20:37 ` [lm-sensors] Does this makes any sense? Rudolf Marek
2008-09-28 20:55 ` Óscar Fuentes
2008-09-28 21:40 ` Jean Delvare
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=4p40uijp.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.