Re: [lm-sensors] k8temp

From: Rudolf Marek <r.marek@assembler.cz>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] k8temp
Date: Wed, 16 May 2007 21:00:13 +0000	[thread overview]
Message-ID: <464B70DD.10508@assembler.cz> (raw)
In-Reply-To: <200703212247.05783.tomcw@adelphia.net>

Hello John,

Sorry for the delay. I will CC the mailing list.

> I may well be mistaken but it is my belief that K8temp cannot report
> correct on-die temperatures because of a design fault with the 0Fh
> series of Athlon64x2 chip. (See the end of this email for possible
> evidence)

Yes I know about that, so far only one case was spotted by me.

> If you already know this, please do not bother to read on,  though if
> you could tell me of a fix I would very much like to know!!

Well I think this is HW bug.

> 
> Here's what my system does under Ubuntu 7.04
> 
> 
> K8temp correctly reports the four 'temperatures' as
> 
> Register 0xe4=		K8temp reports
> 
> 3a			Core0 Temp:              +4째C
> 7a			Core0 Temp:              -9째C
> 3e			Core1 Temp:              +9째C
> 7e			Core1 Temp:              +1째C
> 
> raw data drawn from a PCI inspection .....
> 
> $ sudo setpci -s 00:18.3 e4.Bz

So you are not setting this as the reg value but this  is just a result (7a)

> $ sudo lspci -s 00:18.3 -xxx
> 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
> e0: 00 00 00 00 7a 20 28 00 19 17 00 00 00 00 00 00
> 
> $ sudo setpci -s 00:18.3 e4.B~
> $ sudo lspci -s 00:18.3 -xxx
> 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
> e0: 00 00 00 00 7e 20 32 00 19 17 00 00 00 00 00 00
> 
> $ sudo setpci -s 00:18.3 e4.B>
> $ sudo lspci -s 00:18.3 -xxx
> 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
> e0: 00 00 00 00 3e 20 3a 00 19 17 00 00 00 00 00 00
> 
> $ sudo setpci -s 00:18.3 e4.B:
> $ sudo lspci -s 00:18.3 -xxx
> 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
> e0: 00 00 00 00 3a 20 35 00 19 17 00 00 00 00 00 00
> 
> 
> And here is the CPU ID data
> 
> $ cpuid
>  eax in    eax      ebx      ecx      edx
> 00000000 00000001 68747541 444d4163 69746e65
> 00000001 00060fb1 01020800 00002001 178bfbff
> 80000000 80000018 68747541 444d4163 69746e65
> 80000001 00060fb1 000008cb 0000011f ebd3fbff
> 80000002 20444d41 6c687441 74286e6f 3620296d
> 80000003 32582034 61754420 6f43206c 50206572
> 80000004 65636f72 726f7373 30363320 00002b30
> 80000005 ff08ff08 ff20ff20 40020140 40020140
> 80000006 00000000 42004200 02008140 00000000
> 80000007 00000000 00000000 00000000 0000007f
> 80000008 00003028 00000000 00000001 00000000
> 80000009 00000000 00000000 00000000 00000000
> 8000000a 00000001 00000040 00000000 00000002
> 8000000b 00000000 00000000 00000000 00000000
> 8000000c 00000000 00000000 00000000 00000000
> 8000000d 00000000 00000000 00000000 00000000
> 8000000e 00000000 00000000 00000000 00000000
> 8000000f 00000000 00000000 00000000 00000000
> 80000010 00000000 00000000 00000000 00000000
> 80000011 00000000 00000000 00000000 00000000
> 80000012 00000000 00000000 00000000 00000000
> 80000013 00000000 00000000 00000000 00000000
> 80000014 00000000 00000000 00000000 00000000
> 80000015 00000000 00000000 00000000 00000000
> 80000016 00000000 00000000 00000000 00000000
> 80000017 00000000 00000000 00000000 00000000
> 80000018 00000000 00000000 00000000 00000000
> 
> Vendor ID: "AuthenticAMD"; CPUID level 1

Well did sensors-detect found any other sensors?
Does this bogus temperature change and when you load CPU?

Thanks for the information,

Rudolf

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