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: Tue, 18 Nov 2008 18:15:22 +0000	[thread overview]
Message-ID: <20081118191522.420e0837@hyperion.delvare> (raw)
In-Reply-To: <48E3F505.40401@assembler.cz>

On Tue, 18 Nov 2008 10:46:03 -0700, Jordan Crouse wrote:
> Nothing scientific.  The AMD errata team might know more about it.  I 
> can identify the obviously broken sensors - my athlon X2 system for 
> example tells me the cores are 7C and 3C respectfully, but I don't know 
> if you could tell the difference between a well working sensor and a 
> marginally working sensor, especially with differing work conditions. 
> The best you could do is to figure out how cold the core could possibly 
> run, and then omit anything under that.
> 
> You might do a better job if you could compare the core temperature 
> against the system monitor - they should only differ by a few degrees (I 
> think there is some math about how much the external and internal diodes 
> should differ).  That said, thats not the sort of math you could do in 
> the kernel driver, you would need the user land to find the other sensor 
> and do the calculations.

This is the problem: the k8temp driver doesn't have access to other
sensors for comparison purposes. Even if it had, it wouldn't know which
sensor corresponds to the CPU (this is motherboard-specific.) So while
this can be used by the user to determine whether his CPU sensors are
working or not, this cannot be used as a way to automatically discard
CPUs with broken sensors.

-- 
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-18 18:15 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
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 [this message]

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=20081118191522.420e0837@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.