From: Jean Delvare <khali@linux-fr.org>
To: Matthew <jackdachef@gmail.com>
Cc: Rudolf Marek <r.marek@assembler.cz>,
Maxim Levitsky <maximlevitsky@gmail.com>,
trenn@suse.de, Kasper Sandberg <lkml@metanurb.dk>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, "Zhang, Rui" <rui.zhang@intel.com>
Subject: Re: Linux 2.6.25 (coretemp reads high temperatures)
Date: Wed, 30 Apr 2008 08:10:35 +0200 [thread overview]
Message-ID: <20080430081035.2e789a50@hyperion.delvare> (raw)
In-Reply-To: <e85b9d30804291558r4051f1bbm9256aa2af2d86b6c@mail.gmail.com>
On Wed, 30 Apr 2008 00:58:50 +0200, Matthew wrote:
> so we were just too concerned all the time & even though the
> temperatures seem too high there's nothing to worry ?
Yes.
> I'd be more tranquilized if I had the old temperatures ;)
Note that you can easily get them back by tweaking your sensors.conf
file:
chip "coretemp-*"
compute temp1 @-15, @+15
But I wouldn't do it, as it doesn't make much sense.
> but like lm_sensors's output states - it's not bad until I / we're
> getting temperatures from 85°C (?) [in this particular case], ...
If I remember correctly, at 84°C your CPU will start to throttle, at
100°C it will shut down. You still have 24°C before the former happens,
so it should be OK.
--
Jean Delvare
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali@linux-fr.org>
To: Matthew <jackdachef@gmail.com>
Cc: "Rudolf Marek" <r.marek@assembler.cz>,
"Maxim Levitsky" <maximlevitsky@gmail.com>,
trenn@suse.de, "Kasper Sandberg" <lkml@metanurb.dk>,
"Len Brown" <lenb@kernel.org>,
linux-acpi@vger.kernel.org, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, "Zhang, Rui" <rui.zhang@intel.com>
Subject: Re: Linux 2.6.25 (coretemp reads high temperatures)
Date: Wed, 30 Apr 2008 08:10:35 +0200 [thread overview]
Message-ID: <20080430081035.2e789a50@hyperion.delvare> (raw)
In-Reply-To: <e85b9d30804291558r4051f1bbm9256aa2af2d86b6c@mail.gmail.com>
On Wed, 30 Apr 2008 00:58:50 +0200, Matthew wrote:
> so we were just too concerned all the time & even though the
> temperatures seem too high there's nothing to worry ?
Yes.
> I'd be more tranquilized if I had the old temperatures ;)
Note that you can easily get them back by tweaking your sensors.conf
file:
chip "coretemp-*"
compute temp1 @-15, @+15
But I wouldn't do it, as it doesn't make much sense.
> but like lm_sensors's output states - it's not bad until I / we're
> getting temperatures from 85°C (?) [in this particular case], ...
If I remember correctly, at 84°C your CPU will start to throttle, at
100°C it will shut down. You still have 24°C before the former happens,
so it should be OK.
--
Jean Delvare
next prev parent reply other threads:[~2008-04-30 6:10 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 15:37 Linux 2.6.25 Matthew
2008-04-18 15:43 ` Linus Torvalds
2008-04-18 16:02 ` Matthew
2008-04-18 19:38 ` Cyrill Gorcunov
2008-04-18 20:03 ` Cyrill Gorcunov
2008-04-19 3:05 ` Rene Herman
2008-04-19 3:20 ` Rene Herman
2008-04-19 6:17 ` Cyrill Gorcunov
2008-04-19 10:18 ` Matthew
2008-04-19 10:22 ` Matthew
2008-04-20 12:02 ` Matthew
2008-04-24 3:36 ` Len Brown
2008-04-18 16:24 ` Gene Heskett
2008-04-18 16:27 ` Gene Heskett
2008-04-18 19:18 ` Bart Van Assche
2008-04-18 20:24 ` Jiri Slaby
2008-04-18 20:50 ` [lm-sensors] " Rudolf Marek
2008-04-18 20:50 ` Rudolf Marek
2008-04-19 1:51 ` Linux 2.6.25 (coretemp reads high temperatures) Len Brown
2008-04-21 16:10 ` Thomas Bächler
2008-04-21 16:28 ` Matthew
2008-04-21 17:07 ` Fwd: " Matthew
2008-04-22 9:26 ` Matthew
2008-04-23 8:43 ` Maxim Levitsky
2008-04-23 8:43 ` Maxim Levitsky
2008-04-28 18:19 ` Kasper Sandberg
2008-04-28 18:19 ` Kasper Sandberg
2008-04-29 13:07 ` Thomas Renninger
2008-04-29 15:08 ` Jean Delvare
2008-04-29 22:14 ` Rudolf Marek
2008-04-29 22:58 ` Matthew
2008-04-29 22:58 ` Matthew
2008-04-30 6:10 ` Jean Delvare [this message]
2008-04-30 6:10 ` Jean Delvare
2008-04-30 14:46 ` Henrique de Moraes Holschuh
2008-04-30 14:46 ` Henrique de Moraes Holschuh
2008-04-30 14:50 ` Rudolf Marek
2008-04-30 14:50 ` Rudolf Marek
2008-04-30 15:18 ` Jean Delvare
2008-04-30 15:18 ` Jean Delvare
2008-05-02 20:35 ` Pavel Machek
2008-05-02 20:35 ` Pavel Machek
2008-04-30 0:11 ` Kasper Sandberg
2008-04-30 0:11 ` Kasper Sandberg
2008-04-30 6:20 ` Jean Delvare
2008-04-30 6:20 ` Jean Delvare
2008-04-30 14:51 ` Henrique de Moraes Holschuh
2008-04-30 14:51 ` Henrique de Moraes Holschuh
2008-04-30 15:28 ` Jean Delvare
2008-04-30 15:28 ` Jean Delvare
2008-05-02 20:36 ` Pavel Machek
2008-05-02 20:36 ` Pavel Machek
2008-05-04 17:42 ` Henrique de Moraes Holschuh
2008-05-05 13:45 ` Pavel Machek
2008-05-02 20:35 ` Pavel Machek
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=20080430081035.2e789a50@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=jackdachef@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
--cc=maximlevitsky@gmail.com \
--cc=r.marek@assembler.cz \
--cc=rui.zhang@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=trenn@suse.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 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.