[lm-sensors] No temperature output with k10temp for AMD II X3 435

[lm-sensors] No temperature output with k10temp for AMD II X3 435

[Florian Schwade]

Hello,
I have an AMD II X3 435 cpu. Sensors-detect successfully detects the 
k10temp module is needed.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           Success!
     (driver `k10temp')
AMD Family 11h thermal sensors...                           No
Intel Core family thermal sensor...                         No
Intel Atom thermal sensor...                                No
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No


I also checked that it is loaded correctly.

[florian@errorkiste ~]$ lsmod |grep k10temp
k10temp                 2827  0

If I run sensors to get the temperature the output is just:

[florian@errorkiste ~]$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1:       +21.0°C  (high = +70.0°C)

21°C is impossible to be the correct temperature. The BIOS reports my 
CPU running at something like 36°.
The Kernel is: 2.6.33-ARCH
lm-sensors version: lm_sensors 3.1.2-1

I would appreciate any help. Thanks a lot!
Regards

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

Re: [lm-sensors] No temperature output with k10temp for AMD II X3

[Florian Schwade]

On 15.05.2010 09:06, Jean Delvare wrote:
> Hi Florian,
>
> On Sun, 09 May 2010 22:19:11 +0200, Florian Schwade wrote:
>    
>> Hello,
>> I have an AMD II X3 435 cpu. Sensors-detect successfully detects the
>> k10temp module is needed.
>>      
> There's something missing in your CPU name. Is is an "Athlon II X3" or
> a "Phenom II X3"? I guess the former.
>
>    
>> Some south bridges, CPUs or memory controllers contain embedded sensors.
>> Do you want to scan for them? This is totally safe. (YES/no): y
>> Silicon Integrated Systems SIS5595...                       No
>> VIA VT82C686 Integrated Sensors...                          No
>> VIA VT8231 Integrated Sensors...                            No
>> AMD K8 thermal sensors...                                   No
>> AMD Family 10h thermal sensors...                           Success!
>>       (driver `k10temp')
>> AMD Family 11h thermal sensors...                           No
>> Intel Core family thermal sensor...                         No
>> Intel Atom thermal sensor...                                No
>> Intel AMB FB-DIMM thermal sensor...                         No
>> VIA C7 thermal sensor...                                    No
>> VIA Nano thermal sensor...                                  No
>>
>>
>> I also checked that it is loaded correctly.
>>
>> [florian@errorkiste ~]$ lsmod |grep k10temp
>> k10temp                 2827  0
>>
>> If I run sensors to get the temperature the output is just:
>>
>> [florian@errorkiste ~]$ sensors
>> k10temp-pci-00c3
>> Adapter: PCI adapter
>> temp1:       +21.0째C  (high = +70.0째C)
>>
>> 21째C is impossible to be the correct temperature. The BIOS reports my
>> CPU running at something like 36째.
>>      
> Maybe the BIOS applies an arbitrary offset, or they get the temperature
> from an external sensor connected to a hardware monitoring device.
>
>    
>> The Kernel is: 2.6.33-ARCH
>> lm-sensors version: lm_sensors 3.1.2-1
>>
>> I would appreciate any help. Thanks a lot!
>>      
> Did you force driver loading? Embedded sensors are known to be
> unreliable on the DR-BA, DR-B2, DR-B3, RB-C2 and HY-D0 revisions of the
> family 10h CPU. The driver won't bind to such CPUs by default.
>
> Maybe you have found one more unreliable revision. Please provide the
> contents of /proc/cpuinfo for your CPU, as well as the socket format.
> That being said, unreliability is essentially linked to the socket
> format, so the detection code currently in the driver should work even
> for future CPU models.
>
>    
Hi.
Yes it is an AMD Athlon II x3 on Socket AM3. Sorry.
The content of /proc/cpu info is:

cat /proc/cpuinfo
processor    : 0
vendor_id    : AuthenticAMD
cpu family    : 16
model        : 5
model name    : AMD Athlon(tm) II X3 435 Processor
stepping    : 2
cpu MHz        : 800.000
cache size    : 512 KB
physical id    : 0
siblings    : 3
core id        : 0
cpu cores    : 3
apicid        : 0
initial apicid    : 0
fpu        : yes
fpu_exception    : yes
cpuid level    : 5
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt 
pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc 
extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic 
cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt
bogomips    : 5790.26
TLB size    : 1024 4K pages
clflush size    : 64
cache_alignment    : 64
address sizes    : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

processor    : 1
vendor_id    : AuthenticAMD
cpu family    : 16
model        : 5
model name    : AMD Athlon(tm) II X3 435 Processor
stepping    : 2
cpu MHz        : 800.000
cache size    : 512 KB
physical id    : 0
siblings    : 3
core id        : 1
cpu cores    : 3
apicid        : 1
initial apicid    : 1
fpu        : yes
fpu_exception    : yes
cpuid level    : 5
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt 
pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc 
extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic 
cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt
bogomips    : 5789.20
TLB size    : 1024 4K pages
clflush size    : 64
cache_alignment    : 64
address sizes    : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

processor    : 2
vendor_id    : AuthenticAMD
cpu family    : 16
model        : 5
model name    : AMD Athlon(tm) II X3 435 Processor
stepping    : 2
cpu MHz        : 800.000
cache size    : 512 KB
physical id    : 0
siblings    : 3
core id        : 2
cpu cores    : 3
apicid        : 2
initial apicid    : 2
fpu        : yes
fpu_exception    : yes
cpuid level    : 5
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt 
pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc 
extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic 
cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt
bogomips    : 5789.22
TLB size    : 1024 4K pages
clflush size    : 64
cache_alignment    : 64
address sizes    : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

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

Re: [lm-sensors] No temperature output with k10temp for AMD II X3

[Clemens Ladisch]

Jean Delvare wrote:
> On Sun, 09 May 2010 22:19:11 +0200, Florian Schwade wrote:
> > [florian@errorkiste ~]$ sensors
> > k10temp-pci-00c3
> > Adapter: PCI adapter
> > temp1:       +21.0°C  (high = +70.0°C)
> > 
> > 21°C is impossible to be the correct temperature. The BIOS reports my
> > CPU running at something like 36°.

The temperature values returned by k10temp are relative; AMD says:
| Tctl is the processor temperature control value, used by the platform to
| control cooling systems. Tctl is a non-physical temperature on an
| arbitrary scale measured in degrees. It does _not_ represent an actual
| physical temperature like die or case temperature. Instead, it specifies
| the processor temperature relative to the point at which the system must
| supply the maximum cooling for the processor's specified maximum case
| temperature and maximum thermal power dissipation.

Apparently, on your CPU, the reported values are about 15 °C lower.

lm-sensors currently does not indicate that values are not absolute.

> Maybe the BIOS applies an arbitrary offset,

AMD doesn't publish any method to derive this offset.

> or they get the temperature from an external sensor connected to a
> hardware monitoring device.

This is usually the case, especially since most mainboards also have
a bunch of other temperature sensors handled by the same hwmon device.


Regards,
Clemens

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