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] k8temp, BE-2350 CPU
Date: Sun, 25 Nov 2007 12:20:03 +0000	[thread overview]
Message-ID: <20071125132003.7fbe2a61@hyperion.delvare> (raw)
In-Reply-To: <46BAABD3.5000103@assembler.cz>

Hi Alistair,

On Mon, 8 Oct 2007 00:53:25 +0100, Alistair John Strachan wrote:
> On Thursday 09 August 2007 07:38:29 Alistair John Strachan wrote:
> > On Thursday 09 August 2007 06:53:23 Rudolf Marek wrote:
> > > Hi,
> > >
> > > Sorry for the delay. I'm CCing the list too please do too.
> > >
> > > Alistair John Strachan wrote:
> > > > Hi,
> > > >
> > > > I've noticed a problem with the k8temp driver on a new BE-2350
> > > > processor. It seems the sensors report bogus values on this CPU. This
> > > > is when it is idling:
> > > >
> > > > root@joyeuse:~# cat /sys/bus/pci/drivers/k8temp/0000\:00\:18.3/temp*
> > > > -5000
> > > > -5000
> > > > -3000
> > > > 1000
> > > >
> > > > And this is under load:
> > > >
> > > > root@joyeuse:~# cat /sys/bus/pci/drivers/k8temp/0000\:00\:18.3/temp*
> > > > 7000
> > > > 12000
> > > > 11000
> > > > 17000
> > > >
> > > > This is a socket AM2 processor. Any idea what's wrong? Using kernel
> > > > 2.6.23-rc1, but it's also broken on Debian's 2.6.22.
> > >
> > > Hmm perhaps the formula does not work anymore :/ Can you send me output
> > > of cat /proc/cpuinfo?
> 
> Sorry to nag, Rudolf, but has there been any progress on this issue?

My understanding is that some K8 CPU series simply have broken thermal
sensors and there's not much we can do about it. In some cases you may
try applying arbitrary offsets to get somewhat realistic (yet
incorrect) values, in others even that won't work.

Maybe we will have to blacklist some CPU series from the k8temp driver
to avoid the confusion.

-- 
Jean Delvare

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

  parent reply	other threads:[~2007-11-25 12:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09  5:53 [lm-sensors] k8temp, BE-2350 CPU Rudolf Marek
2007-08-09  6:38 ` Alistair John Strachan
2007-09-03 10:36 ` Rudolf Marek
2007-09-03 21:38 ` Bernhard Seibold
2007-09-04 18:53 ` Rudolf Marek
2007-09-04 20:55 ` Bernhard Seibold
2007-09-04 21:06 ` Rudolf Marek
2007-09-05 19:01 ` Juergen.Bausa
2007-09-06  7:21 ` Rudolf Marek
2007-10-07 23:53 ` Alistair John Strachan
2007-11-25 12:20 ` Jean Delvare [this message]
2007-11-25 14:13 ` Moebius
2007-11-25 20:55 ` Gerold Gruber
2007-11-26 14:16 ` Moebius

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=20071125132003.7fbe2a61@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.