All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Richling <jan@richling.de>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] coretemp driver and Celeron 430 - works
Date: Sun, 07 Oct 2007 17:10:05 +0000	[thread overview]
Message-ID: <470912ED.3040301@richling.de> (raw)
In-Reply-To: <4708C611.5040808@assembler.cz>

Hi Rudolf,

> Cool thanks. Please note that the temperature might be more non-physical. So in
> your case you have still 55C to overheat. The processor reports temp relative to
> trip point, which is "100C" in your case. If it is 85C or 100C works fine on
> mobile variants, should not on desktop CPUs.
> 
> To sum it up. Even if your temperature is not a real one, you have still 55C to
> critical level.

I know... I did a kind of "test" of this. Running burnP6 with overclock
to 3 GHz and the stock cooler triggered auto shutdown of the CPU in less
than 30 seconds. Now I have a Pentium D820 boxed cooler and the core
goes up to 69 which is still 31 below the critical level.

Regarding the patch - I guess you can add 0x17 soon. This is the new
Penryn core Intel will bring to market in november. Question is only if
there is somebody to test.

Greetings,

Jan

   ------------------------------------------------------------------
  / Dr. Jan Richling - http://www.richling.de                      /
 / Member of Computer Architecture and Communication Group -      /
/ Department of Computer Science - Humboldt University Berlin    /

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2007-10-07 17:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-07 11:42 [lm-sensors] [PATCH] coretemp driver and Celeron 430 - works Rudolf Marek
2007-10-07 14:49 ` Jan Richling
2007-10-07 16:46 ` Rudolf Marek
2007-10-07 17:10 ` Jan Richling [this message]
2007-10-07 17:17 ` Rudolf Marek
2007-10-09  2:17 ` Mark M. Hoffman

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=470912ED.3040301@richling.de \
    --to=jan@richling.de \
    --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.