All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH 1/2] k8temp warn about errata
Date: Sun, 09 Nov 2008 20:47:05 +0000	[thread overview]
Message-ID: <20081109214705.3e9114ef@hyperion.delvare> (raw)
In-Reply-To: <48E3F505.40401@assembler.cz>

Hi Jean-Marc,

Thanks for your comments.

On Sun, 26 Oct 2008 21:18:42 -0400, Jean-Marc Spaggiari wrote:
> Sound like a good idea to me
> 
> For those values:
> 
> k8temp-pci-00c3
> Adapter: PCI adapter
> Core0 Temp:  +26 C
> Core1 Temp:  +24 C
> 
> k8temp-pci-00c3
> Adapter: PCI adapter
> Core0 Temp:  +17°C
> Core1 Temp:  +25°C
> 
> I think they are correct. In winter, I place my computer outside
> (-10C/-15C). The idle core temp can be pretty low.

They can be correct, but the fact is that we can't be certain (that's
more or less the definition of a heuristic.) Maybe these machines had
working diodes and were in a very cool environment. Or maybe these
machines had broken diodes and were in a very hot environment.

> So it's important
> to give the user a way to force the sensor activation or adjust the
> temperatures level for the heuristic.

Definitely, yes.

> So in this statement:
> * Average of the 4 sensors is below 15 degrees C.
> * Minimum of the 4 sensors is below 5 degrees C
> 
> The user need to be able to update 15 and 5.

This was part of my original proposal :) Either that of a boolean
option to simply force the driver to bind.

> Also, since in all examples the average temperature is lower than 15
> degrees C (-4,75;  -15,25; -6,25; 3; 5,75) I will recommand to put it
> closer to 10 degrees C.

You forgot the first entry in the list:

k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:  +17 C
Core0 Temp:   +3 C
Core1 Temp:  +21 C
Core1 Temp:   +5 C

That one has an average temperature of 11.5 degrees C, so a limit of 10
degrees C would consider it good - which it clearly isn't. That being
said, there's no perfect limit, so maybe it is OK if the above is
considered OK by the driver even if I'm certain it isn't.

OTOH, the above is an interesting case. What strikes me here is not the
temperature values themselves but the difference between them which is
pretty unrealistic. So maybe this can be another check in the heuristic.

-- 
Jean Delvare

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

  parent reply	other threads:[~2008-11-09 20:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 22:09 [lm-sensors] [PATCH 1/2] k8temp warn about errata Rudolf Marek
2008-10-25 12:43 ` Jean Delvare
2008-10-27  1:18 ` Jean-Marc Spaggiari
2008-11-09 19:56 ` Rudolf Marek
2008-11-09 20:47 ` Jean Delvare [this message]
2008-11-09 20:54 ` Jean Delvare
2008-11-10  1:27 ` Jordan Crouse
2008-11-10  9:38 ` Jean Delvare
2008-11-18  8:41 ` Andreas Herrmann
2008-11-18  8:55 ` Andreas Herrmann
2008-11-18  9:06 ` Jean Delvare
2008-11-18  9:25 ` Andreas Herrmann
2008-11-18 10:10 ` Andreas Herrmann
2008-11-18 10:40 ` Jean Delvare
2008-11-18 11:18 ` Andreas Herrmann
2008-11-18 11:26 ` Andreas Herrmann
2008-11-18 12:33 ` Jean Delvare
2008-11-18 12:57 ` Jean Delvare
2008-11-18 17:46 ` Jordan Crouse
2008-11-18 18:15 ` 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=20081109214705.3e9114ef@hyperion.delvare \
    --to=khali@linux-fr.org \
    --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.