All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rudolf Marek <r.marek@assembler.cz>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] k8temp
Date: Fri, 18 May 2007 09:10:17 +0000	[thread overview]
Message-ID: <464D6D79.2040709@assembler.cz> (raw)
In-Reply-To: <200703212247.05783.tomcw@adelphia.net>

Hello all,

For Philip :
>No, that command *writes* 7A to PCI space register offset E4.

Yeah of course. I was half sleeping when I wrote the mail.
> 
> Just to clarify, the 32 bit register at 0xE4 of the AMD64x2 is the
> thermotrip status register:- 
> 	
> Bits   Function                                         R/W    Reset
> 31     Software Thermtrip  	                         W      0
> 30–29  reserved                                          R      0
> 28-24  Tj Offset                                         R      0
> 23-14  Current Temperature                               R
> 13–8   Diode Offset                                      R
> 7	reserved                                         R      0
> 6      Thermal Sensor Select                           R/W      0
> 5      Thermtrip Enabled                                 R
> 4      Thermtrip Sense 1                                 R
> 3      Thermtrip Sense 0                                 R
> 2      Thermal Sensor Core Select                      R/W      0
> 1      Thermtrip    					 R
> 0	reserved	   				 R      0
> 
> So reading 0xE6 gets the current temperature from one of the four
> sensors  selected by setting or clearing bits 2 and 6 in 0xe4
> (the bottom two bits of the temperature, which are the high two bits in
> 0xE5 represent fractions of a degree, but can be ignored by K8temp
> without a problem)  

Yes this was not added yet.

> As K8temp correctly implements, the temperature is given by: (Snipped
> from AMD documentation), 
> 
>        Revision F encodings bits 23-16 (ignore bits 15-14)
>        00h = -49C
>        01h = -48C
>        ...
>        ffh = 206C
> 
> 
>        Revision G encodings bits 23-14
>        000h = -49.00C
>        001h = -48.75C
>        002h = -48.50C
>        003h = -48.25C
>        004h = -48.00C
>        ...
>        0C4h = 0.00C
>        ...
>        3ffh = 206.75C
> 
> 
> 
> So the examples I gave show K8temp reporting temperatures at or below
> 0C. Examining the register at 0xE6 confirms that K8temp is working
> correctly.
> 
> Rudolph, you mention having seen this problem before.  It would
> certainly be a hardware bug and my reason for mentioning it is so that
> k8temp does not get a bad name with the community.
> Have you heard whether AMD are proposing to do something about it?

Well I'm in touch with author of "coretemp" utility for windows. It seems all
brisbane processors (same cpuid as yours) are affected. Some have offset 15-20
(compared to diode measured temp with ext sensor) some have even more, like yours.

As for the diode offset. Your CPU has set this to 0x20 so it is
10000 and complement of 011111 -52+31 offset is -21C if I count correctly
(probably not ;)  This is quite interesting because my CPU has offset 0x3 (but
have revE must check if the bits are same)

Question is how to apply the offset? They say TMax = diode + offset;
I still think that the offset field is for real diode only, however here it
indicates that something went wrong...

I will think about it later, gotta go now.

Rudolf

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

  parent reply	other threads:[~2007-05-18  9:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22  2:47 [lm-sensors] k8temp Tom Weichmann
2007-03-22  6:03 ` Curt Blank
2007-05-16 21:00 ` Rudolf Marek
2007-05-16 21:16 ` Philip Pokorny
2007-05-16 23:15 ` John Tindle
2007-05-18  9:10 ` Rudolf Marek [this message]
2007-05-18 23:25 ` John Tindle
2007-05-18 23:30 ` John Tindle

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=464D6D79.2040709@assembler.cz \
    --to=r.marek@assembler.cz \
    --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.