* [lm-sensors] Inconsistents results
2007-02-01 5:44 [lm-sensors] Inconsistents results Georges Giralt
@ 2007-02-04 15:03 ` Rudolf Marek
2007-02-04 18:37 ` Georges Giralt
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Rudolf Marek @ 2007-02-04 15:03 UTC (permalink / raw)
To: lm-sensors
Hello,
Georges Giralt wrote:
> Hi !
> I own a recent Asus mainboard (M2NPV-VM) with an Athlon 64X2 3600+ (the
> cheap low cache version, low power consumption).
> The results I get with ACPI and sensors are inconsistent :
> The Mobo BIOS gives 28~30 ? C for the proc and 1?C above for the mobo
> so 29~31 ?C)
> Under Linux (Fedora Core 6 2.6.19-1.2895.fc6 X86-64) I get :
> # cat /proc/acpi/thermal_zone/THRM/temperature
> temperature: 40 C
Please can you provide the dsdt.bin file?
cat /proc/acpi/dsdt > /tmp/dsdt.bin
(this command will create it in the /tmp directory)
> #sensors
> k8temp-pci-00c3
> Adapter: PCI adapter
> Core0 Temp:
> +13?C
> Core1 Temp:
> +27?C
>
> it8716-isa-0290
> Adapter: ISA adapter
> VCore: +1.02 V (min = +0.00 V, max = +4.08 V)
> VDDR: +3.25 V (min = +0.00 V, max = +4.08 V)
> +3.3V: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
> +5V: +4.84 V (min = +0.00 V, max = +6.85 V)
> +12V: +11.78 V (min = +0.00 V, max = +16.32 V)
> in5: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
> in6: +0.00 V (min = +0.00 V, max = +3.82 V) ALARM
> 5VSB: +4.68 V (min = +0.00 V, max = +6.85 V)
> VBat: +2.91 V
> fan1: 2860 RPM (min = 0 RPM)
> fan2: 1391 RPM (min = 0 RPM)
> fan3: 0 RPM (min = 0 RPM)
> temp1: +18?C (low = -1?C, high = +127?C) sensor = diode
> temp2: +28?C (low = -1?C, high = +127?C) sensor = thermistor
> temp3: +25?C (low = -1?C, high = +127?C) sensor = thermistor
> vid: +0.000 V
> #
> Two things bother me : First, the discrepancy between core0 temp and
> core1 temp. As they are into the same package, they should even out,
> should'nt they ? The second thing is that the spread ot temperature I
> get : 13, 18, 25, 27, 28 and 40 ?C ...
You mean when you try to raise the temperature - CPU usage?
> If anybody has an answer, a lead, or an idea, it will have my gratitude !
The ACPI versus lm-sensors temperature may be explained after I will have the
dsdt.bin
Add +49
13 62 3E 0011 1110
18 67 43 0100 0011
25 74 4A 0100 1010
27 76 4C 0100 1100
28 77 4D 0100 1101
40 89 59 0101 1001
I added the 49 value to get back the raw value, no bit is stuck. Btw the diode
reading reads 18C - quite close to 13C - maybe the internal CPU sensors is not
well calibrated?
28-25 is the thermistor temperature of motherboard and not processor.
Please also include the cat /proc/cpuinfo
Thanks,
Rudolf
^ permalink raw reply [flat|nested] 8+ messages in thread* [lm-sensors] Inconsistents results
2007-02-01 5:44 [lm-sensors] Inconsistents results Georges Giralt
2007-02-04 15:03 ` Rudolf Marek
@ 2007-02-04 18:37 ` Georges Giralt
2007-02-04 19:22 ` Rudolf Marek
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Georges Giralt @ 2007-02-04 18:37 UTC (permalink / raw)
To: lm-sensors
Hi Rudolf !
Thanks a lot for your answer !
You'll find enclosed the dsdt.bin and cpuinfo files and my comments inline :
Rudolf Marek a ?crit :
> Hello,
>
> Georges Giralt wrote:
>> Hi !
>> I own a recent Asus mainboard (M2NPV-VM) with an Athlon 64X2 3600+ (the
>> cheap low cache version, low power consumption).
>> The results I get with ACPI and sensors are inconsistent :
>> The Mobo BIOS gives 28~30 ? C for the proc and 1?C above for the mobo
>> so 29~31 ?C)
>> Under Linux (Fedora Core 6 2.6.19-1.2895.fc6 X86-64) I get :
>> # cat /proc/acpi/thermal_zone/THRM/temperature
>> temperature: 40 C
>
> Please can you provide the dsdt.bin file?
>
> cat /proc/acpi/dsdt > /tmp/dsdt.bin
>
> (this command will create it in the /tmp directory)
>
>> #sensors
>> k8temp-pci-00c3
>> Adapter: PCI adapter
>> Core0 Temp:
>> +13?C
>> Core1 Temp:
>> +27?C
>>
>> it8716-isa-0290
>> Adapter: ISA adapter
>> VCore: +1.02 V (min = +0.00 V, max = +4.08 V)
>> VDDR: +3.25 V (min = +0.00 V, max = +4.08 V)
>> +3.3V: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
>> +5V: +4.84 V (min = +0.00 V, max = +6.85 V)
>> +12V: +11.78 V (min = +0.00 V, max = +16.32 V)
>> in5: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
>> in6: +0.00 V (min = +0.00 V, max = +3.82 V) ALARM
>> 5VSB: +4.68 V (min = +0.00 V, max = +6.85 V)
>> VBat: +2.91 V
>> fan1: 2860 RPM (min = 0 RPM)
>> fan2: 1391 RPM (min = 0 RPM)
>> fan3: 0 RPM (min = 0 RPM)
>> temp1: +18?C (low = -1?C, high = +127?C) sensor = diode
>> temp2: +28?C (low = -1?C, high = +127?C) sensor = thermistor
>> temp3: +25?C (low = -1?C, high = +127?C) sensor = thermistor
>> vid: +0.000 V
>> #
>> Two things bother me : First, the discrepancy between core0 temp and
>> core1 temp. As they are into the same package, they should even out,
>> should'nt they ? The second thing is that the spread ot temperature I
>> get : 13, 18, 25, 27, 28 and 40 ?C ...
>
> You mean when you try to raise the temperature - CPU usage?
No, no the discrepancies between the two core temps, and the temp seen
by the mobo regarding the CPU temp. it goes from 13 to 40 ?C depending
which way you use to find it...
>
>> If anybody has an answer, a lead, or an idea, it will have my gratitude !
>
> The ACPI versus lm-sensors temperature may be explained after I will have the
> dsdt.bin
>
> Add +49
>
>
>
> 13 62 3E 0011 1110
>
> 18 67 43 0100 0011
>
> 25 74 4A 0100 1010
>
> 27 76 4C 0100 1100
>
> 28 77 4D 0100 1101
>
> 40 89 59 0101 1001
>
> I added the 49 value to get back the raw value, no bit is stuck. Btw the diode
> reading reads 18C - quite close to 13C - maybe the internal CPU sensors is not
> well calibrated?
>
> 28-25 is the thermistor temperature of motherboard and not processor.
This is low regarding BIOS readings : When the CPU is at 28?C the mobo
is about 31 ?C for the BIOS. (BTW I've the latest BIOS : Rev 0603)
>
> Please also include the cat /proc/cpuinfo
>
> Thanks,
> Rudolf
>
>
Thanks a lot for your help and answers !
--
Ce message est constitu? d'au moins 50 % d'?lectrons recycl?s.
S'il vous pla?t, aidez nous ? conserver nos ressources,
recyclez vos ?lectrons !
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dsdt.bin
Type: application/octet-stream
Size: 33216 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20070204/52c979ae/attachment-0001.bin
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cpuinfo
Url: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20070204/52c979ae/attachment-0001.pl
^ permalink raw reply [flat|nested] 8+ messages in thread* [lm-sensors] Inconsistents results
2007-02-01 5:44 [lm-sensors] Inconsistents results Georges Giralt
2007-02-04 15:03 ` Rudolf Marek
2007-02-04 18:37 ` Georges Giralt
@ 2007-02-04 19:22 ` Rudolf Marek
2007-02-05 5:32 ` Georges Giralt
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Rudolf Marek @ 2007-02-04 19:22 UTC (permalink / raw)
To: lm-sensors
Georges Giralt wrote:
> Hi Rudolf !
Hi,
Please always CC the list! So we have this for future generations ;)
>> Please can you provide the dsdt.bin file?
>>
>> cat /proc/acpi/dsdt > /tmp/dsdt.bin
>>
>> (this command will create it in the /tmp directory)
It reads temp1 (0x29)
Method (RTMP, 0, NotSerialized)
{
Store (GBYT (0x29), Local0)
FindSetLeftBit (Local0, Local1)
If (LEqual (Local1, 0x08))
{
if highest bit set
And (Local0, 0x7F, Local0)
Multiply (Local0, 0x0A, Local0)
use the low 7 bits * 10
Subtract (0x0AAC, Local0, Local0)
substract 2732 because of kelvins and it suppose to be in tenth of kelvins
}
Else
{
Multiply (Local0, 0x0A, Local0)
*10
Add (0x0AAC, Local0, Local0)
Add 2732 if temp is positive
}
If (LEqual (SSHU, 0x01))
{
Return (0x0C3C)
But your case is this. if variable called SSHU is set to 1, return always 40C
So mystery is solved.
}
Else
{
Return (Local0)
}
}
And from asus ATK0110 ACPI device:
Store (TSR1, Local0)
Store (0x00, Local1)
While (LEqual (Local0, 0x80))
{
Store (TSR1, Local0)
If (LEqual (Local1, 0x000186A0))
{
Break
}
Add (Local1, 0x01, Local1)
}
Multiply (Local0, 0x0A, Local0)
Return (Local0)
This is a bit strange code. It reads the temp, if the temp is 0x80 it re-reads
the temp 100000 (186A0) times.
>>> #sensors
>>> k8temp-pci-00c3
>>> Adapter: PCI adapter
>>> Core0 Temp:
>>> +13?C
>>> Core1 Temp:
>>> +27?C
>>>
>>> it8716-isa-0290
>>> Adapter: ISA adapter
>>> VCore: +1.02 V (min = +0.00 V, max = +4.08 V)
>>> VDDR: +3.25 V (min = +0.00 V, max = +4.08 V)
>>> +3.3V: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
>>> +5V: +4.84 V (min = +0.00 V, max = +6.85 V)
>>> +12V: +11.78 V (min = +0.00 V, max = +16.32 V)
>>> in5: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
>>> in6: +0.00 V (min = +0.00 V, max = +3.82 V) ALARM
>>> 5VSB: +4.68 V (min = +0.00 V, max = +6.85 V)
>>> VBat: +2.91 V
>>> fan1: 2860 RPM (min = 0 RPM)
>>> fan2: 1391 RPM (min = 0 RPM)
>>> fan3: 0 RPM (min = 0 RPM)
>>> temp1: +18?C (low = -1?C, high = +127?C) sensor = diode
>>> temp2: +28?C (low = -1?C, high = +127?C) sensor >>> thermistor
>>> temp3: +25?C (low = -1?C, high = +127?C) sensor >>> thermistor
>>> vid: +0.000 V
>>> #
>>> Two things bother me : First, the discrepancy between core0 temp and
>>> core1 temp. As they are into the same package, they should even out,
>>> should'nt they ? The second thing is that the spread ot temperature I
>>> get : 13, 18, 25, 27, 28 and 40 ?C ...
>>
>> You mean when you try to raise the temperature - CPU usage?
> No, no the discrepancies between the two core temps, and the temp seen
> by the mobo regarding the CPU temp. it goes from 13 to 40 ?C depending
> which way you use to find it...
Aha now I understand.
13 - I think some calibration went wrong in this core
18 - it has same source as 13C it just use analog wire and diode.
25C - this temp will never move because they put the resitor there instead of
thermistor, so just forget about temp3
27C looks OK
28C is motherboard temp
40C is fake temperature for some reason.
> This is low regarding BIOS readings : When the CPU is at 28?C the mobo
> is about 31 ?C for the BIOS. (BTW I've the latest BIOS : Rev 0603)
Maybe it just get hotter in the BIOS. The asus APCI programming shows that temp1
is CPU and temp2 is MB. Temp3 is not used at all - 25C means just some resistor
is placed instead of thermistor.
>
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 15
> model : 75
It seems you have revision F of the CPU, perhaps it has really just misplaced
the thermal calibration.
I hope it helps,
Rudolf
^ permalink raw reply [flat|nested] 8+ messages in thread* [lm-sensors] Inconsistents results
2007-02-01 5:44 [lm-sensors] Inconsistents results Georges Giralt
` (2 preceding siblings ...)
2007-02-04 19:22 ` Rudolf Marek
@ 2007-02-05 5:32 ` Georges Giralt
2007-02-07 17:39 ` Georges Giralt
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Georges Giralt @ 2007-02-05 5:32 UTC (permalink / raw)
To: lm-sensors
Rudolf Marek a ?crit :
> Georges Giralt wrote:
>> Hi Rudolf !
> Hi,
>
> Please always CC the list! So we have this for future generations ;)
>
>>> Please can you provide the dsdt.bin file?
>>>
>>> cat /proc/acpi/dsdt > /tmp/dsdt.bin
>>>
>>> (this command will create it in the /tmp directory)
>
> It reads temp1 (0x29)
>
> Method (RTMP, 0, NotSerialized)
>
> {
>
> Store (GBYT (0x29), Local0)
>
> FindSetLeftBit (Local0, Local1)
>
> If (LEqual (Local1, 0x08))
>
> {
> if highest bit set
>
> And (Local0, 0x7F, Local0)
>
> Multiply (Local0, 0x0A, Local0)
>
> use the low 7 bits * 10
>
> Subtract (0x0AAC, Local0, Local0)
>
>
> substract 2732 because of kelvins and it suppose to be in tenth of kelvins
>
> }
>
> Else
>
> {
>
> Multiply (Local0, 0x0A, Local0)
>
> *10
> Add (0x0AAC, Local0, Local0)
>
> Add 2732 if temp is positive
>
> }
>
>
>
> If (LEqual (SSHU, 0x01))
>
> {
>
> Return (0x0C3C)
> But your case is this. if variable called SSHU is set to 1, return always 40C
> So mystery is solved.
>
> }
>
> Else
>
> {
>
> Return (Local0)
>
> }
>
> }
>
> And from asus ATK0110 ACPI device:
>
> Store (TSR1, Local0)
>
> Store (0x00, Local1)
>
> While (LEqual (Local0, 0x80))
>
> {
>
> Store (TSR1, Local0)
>
> If (LEqual (Local1, 0x000186A0))
>
> {
>
> Break
>
> }
>
>
>
> Add (Local1, 0x01, Local1)
>
> }
>
>
>
> Multiply (Local0, 0x0A, Local0)
>
> Return (Local0)
>
> This is a bit strange code. It reads the temp, if the temp is 0x80 it re-reads
> the temp 100000 (186A0) times.
>
>>>> #sensors
>>>> k8temp-pci-00c3
>>>> Adapter: PCI adapter
>>>> Core0 Temp:
>>>> +13?C
>>>> Core1 Temp:
>>>> +27?C
>>>>
>>>> it8716-isa-0290
>>>> Adapter: ISA adapter
>>>> VCore: +1.02 V (min = +0.00 V, max = +4.08 V)
>>>> VDDR: +3.25 V (min = +0.00 V, max = +4.08 V)
>>>> +3.3V: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
>>>> +5V: +4.84 V (min = +0.00 V, max = +6.85 V)
>>>> +12V: +11.78 V (min = +0.00 V, max = +16.32 V)
>>>> in5: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
>>>> in6: +0.00 V (min = +0.00 V, max = +3.82 V) ALARM
>>>> 5VSB: +4.68 V (min = +0.00 V, max = +6.85 V)
>>>> VBat: +2.91 V
>>>> fan1: 2860 RPM (min = 0 RPM)
>>>> fan2: 1391 RPM (min = 0 RPM)
>>>> fan3: 0 RPM (min = 0 RPM)
>>>> temp1: +18?C (low = -1?C, high = +127?C) sensor = diode
>>>> temp2: +28?C (low = -1?C, high = +127?C) sensor >>>> thermistor
>>>> temp3: +25?C (low = -1?C, high = +127?C) sensor >>>> thermistor
>>>> vid: +0.000 V
>>>> #
>>>> Two things bother me : First, the discrepancy between core0 temp and
>>>> core1 temp. As they are into the same package, they should even out,
>>>> should'nt they ? The second thing is that the spread ot temperature I
>>>> get : 13, 18, 25, 27, 28 and 40 ?C ...
>>> You mean when you try to raise the temperature - CPU usage?
>> No, no the discrepancies between the two core temps, and the temp seen
>> by the mobo regarding the CPU temp. it goes from 13 to 40 ?C depending
>> which way you use to find it...
>
> Aha now I understand.
>
> 13 - I think some calibration went wrong in this core
> 18 - it has same source as 13C it just use analog wire and diode.
>
> 25C - this temp will never move because they put the resitor there instead of
> thermistor, so just forget about temp3
>
> 27C looks OK
> 28C is motherboard temp
>
> 40C is fake temperature for some reason.
>
>> This is low regarding BIOS readings : When the CPU is at 28?C the mobo
>> is about 31 ?C for the BIOS. (BTW I've the latest BIOS : Rev 0603)
>
> Maybe it just get hotter in the BIOS. The asus APCI programming shows that temp1
> is CPU and temp2 is MB. Temp3 is not used at all - 25C means just some resistor
> is placed instead of thermistor.
>
>> processor : 0
>> vendor_id : AuthenticAMD
>> cpu family : 15
>> model : 75
>
> It seems you have revision F of the CPU, perhaps it has really just misplaced
> the thermal calibration.
>
> I hope it helps,
>
> Rudolf
>
>
Hi all !
So here it goes :
At cold boot up the readings are :
Core0 Temp:
+9?C
Core1 Temp:
+26?C
temp1: +15?C (low = -1?C, high = +127?C) sensor = diode
temp2: +25?C (low = -1?C, high = +127?C) sensor = thermistor
So pretty consistent with the internal CPU probe.
After a while the temps stabilize as follow :
Core0 Temp:
+11?C
Core1 Temp:
+28?C
temp1: +17?C (low = -1?C, high = +127?C) sensor = diode
temp2: +27?C (low = -1?C, high = +127?C) sensor = thermistor
It seems the MOBO gets warm during the initialization phase and then
stick to the 25~30 ?C
And that the CPU slowly rise from the cold to the 17~27 ?C (when I let
the CPU go idle it fall to 17 ?C so CPU freq scqlling is working ;-) )
Thanks a lot Rudolf for your help and advices !
--
Ce message est constitu? d'au moins 50 % d'?lectrons recycl?s.
S'il vous pla?t, aidez nous a` conserver nos ressources,
recyclez vos ?lectrons !
^ permalink raw reply [flat|nested] 8+ messages in thread* [lm-sensors] Inconsistents results
2007-02-01 5:44 [lm-sensors] Inconsistents results Georges Giralt
` (3 preceding siblings ...)
2007-02-05 5:32 ` Georges Giralt
@ 2007-02-07 17:39 ` Georges Giralt
2007-02-08 19:47 ` Rudolf Marek
2007-02-08 20:21 ` Georges Giralt
6 siblings, 0 replies; 8+ messages in thread
From: Georges Giralt @ 2007-02-07 17:39 UTC (permalink / raw)
To: lm-sensors
Rudolf Marek a ?crit :
> Georges Giralt wrote:
>> Hi Rudolf !
> Hi,
>
> Please always CC the list! So we have this for future generations ;)
>
>>> Please can you provide the dsdt.bin file?
>>>
>>> cat /proc/acpi/dsdt > /tmp/dsdt.bin
>>>
>>> (this command will create it in the /tmp directory)
>
> It reads temp1 (0x29)
>
> Method (RTMP, 0, NotSerialized)
>
> {
>
> Store (GBYT (0x29), Local0)
>
> FindSetLeftBit (Local0, Local1)
>
> If (LEqual (Local1, 0x08))
>
> {
> if highest bit set
>
> And (Local0, 0x7F, Local0)
>
> Multiply (Local0, 0x0A, Local0)
>
> use the low 7 bits * 10
>
> Subtract (0x0AAC, Local0, Local0)
>
>
> substract 2732 because of kelvins and it suppose to be in tenth of kelvins
>
> }
>
> Else
>
> {
>
> Multiply (Local0, 0x0A, Local0)
>
> *10
> Add (0x0AAC, Local0, Local0)
>
> Add 2732 if temp is positive
>
> }
>
>
>
> If (LEqual (SSHU, 0x01))
>
> {
>
> Return (0x0C3C)
> But your case is this. if variable called SSHU is set to 1, return always 40C
> So mystery is solved.
>
> }
>
> Else
>
> {
>
> Return (Local0)
>
> }
>
> }
>
> And from asus ATK0110 ACPI device:
>
> Store (TSR1, Local0)
>
> Store (0x00, Local1)
>
> While (LEqual (Local0, 0x80))
>
> {
>
> Store (TSR1, Local0)
>
> If (LEqual (Local1, 0x000186A0))
>
> {
>
> Break
>
> }
>
>
>
> Add (Local1, 0x01, Local1)
>
> }
>
>
>
> Multiply (Local0, 0x0A, Local0)
>
> Return (Local0)
>
> This is a bit strange code. It reads the temp, if the temp is 0x80 it re-reads
> the temp 100000 (186A0) times.
>
>>>> #sensors
>>>> k8temp-pci-00c3
>>>> Adapter: PCI adapter
>>>> Core0 Temp:
>>>> +13?C
>>>> Core1 Temp:
>>>> +27?C
>>>>
>>>> it8716-isa-0290
>>>> Adapter: ISA adapter
>>>> VCore: +1.02 V (min = +0.00 V, max = +4.08 V)
>>>> VDDR: +3.25 V (min = +0.00 V, max = +4.08 V)
>>>> +3.3V: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
>>>> +5V: +4.84 V (min = +0.00 V, max = +6.85 V)
>>>> +12V: +11.78 V (min = +0.00 V, max = +16.32 V)
>>>> in5: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
>>>> in6: +0.00 V (min = +0.00 V, max = +3.82 V) ALARM
>>>> 5VSB: +4.68 V (min = +0.00 V, max = +6.85 V)
>>>> VBat: +2.91 V
>>>> fan1: 2860 RPM (min = 0 RPM)
>>>> fan2: 1391 RPM (min = 0 RPM)
>>>> fan3: 0 RPM (min = 0 RPM)
>>>> temp1: +18?C (low = -1?C, high = +127?C) sensor = diode
>>>> temp2: +28?C (low = -1?C, high = +127?C) sensor >>>> thermistor
>>>> temp3: +25?C (low = -1?C, high = +127?C) sensor >>>> thermistor
>>>> vid: +0.000 V
>>>> #
>>>> Two things bother me : First, the discrepancy between core0 temp and
>>>> core1 temp. As they are into the same package, they should even out,
>>>> should'nt they ? The second thing is that the spread ot temperature I
>>>> get : 13, 18, 25, 27, 28 and 40 ?C ...
>>> You mean when you try to raise the temperature - CPU usage?
>> No, no the discrepancies between the two core temps, and the temp seen
>> by the mobo regarding the CPU temp. it goes from 13 to 40 ?C depending
>> which way you use to find it...
>
> Aha now I understand.
>
> 13 - I think some calibration went wrong in this core
> 18 - it has same source as 13C it just use analog wire and diode.
>
> 25C - this temp will never move because they put the resitor there instead of
> thermistor, so just forget about temp3
>
> 27C looks OK
> 28C is motherboard temp
>
> 40C is fake temperature for some reason.
>
>> This is low regarding BIOS readings : When the CPU is at 28?C the mobo
>> is about 31 ?C for the BIOS. (BTW I've the latest BIOS : Rev 0603)
>
> Maybe it just get hotter in the BIOS. The asus APCI programming shows that temp1
> is CPU and temp2 is MB. Temp3 is not used at all - 25C means just some resistor
> is placed instead of thermistor.
>
>> processor : 0
>> vendor_id : AuthenticAMD
>> cpu family : 15
>> model : 75
>
> It seems you have revision F of the CPU, perhaps it has really just misplaced
> the thermal calibration.
>
> I hope it helps,
>
> Rudolf
>
>
Hi !
May I add the response from AMD regarding the difference between the
Core 0 temp and Core 1 temp ?
I quote :
==================================
En ce qui concerne la diff?rence de temp?rature entre les deux core, il
semblerait que lors du test, un seul des core soit actif car la charge
de travail ne devait pas n?cessiter l activation du deuxieme core. En
effet 17? correspond a peu pres a la temperature de l environement ou` le
PC est plac?.
En ce qui concerne la difference de temperature annonc? part la carte
mere, il est normal qu elle soit legerement differente car moins
precise. En effet la capteur de temperature du processeur est in?gr? a
celui ci donc plus fiable.
==================================As it is in French, I translate it roughly as : "the cause of the
difference is that the second core is not used at all because the
workload is too low. The core 1 temp is about the ambient temp.
Regarding the difference between the temp of the core0 as seen by the
AMD 64 sensor and the Mobo the cause is a difference in precision, the
mobo being less precise/accurate thand the in CPU sensor."
So my conclusion is that the Fedora Kernel scheduler only use one core
unless the load is high. (I'm trying to prove it doing huge compilations
whith optimisation turned on)
Thanks to all who helped so far !
--
Ce message est constitu? d'au moins 50 % d'?lectrons recycl?s.
S'il vous pla?t, aidez nous a` conserver nos ressources,
recyclez vos ?lectrons !
^ permalink raw reply [flat|nested] 8+ messages in thread* [lm-sensors] Inconsistents results
2007-02-01 5:44 [lm-sensors] Inconsistents results Georges Giralt
` (4 preceding siblings ...)
2007-02-07 17:39 ` Georges Giralt
@ 2007-02-08 19:47 ` Rudolf Marek
2007-02-08 20:21 ` Georges Giralt
6 siblings, 0 replies; 8+ messages in thread
From: Rudolf Marek @ 2007-02-08 19:47 UTC (permalink / raw)
To: lm-sensors
Hello again,
> Hi !
> May I add the response from AMD regarding the difference between the
> Core 0 temp and Core 1 temp ?
> I quote :
> ==================================
> En ce qui concerne la diff?rence de temp?rature entre les deux core, il
> semblerait que lors du test, un seul des core soit actif car la charge
> de travail ne devait pas n?cessiter l activation du deuxieme core. En
> effet 17? correspond a peu pres a la temperature de l environement ou` le
> PC est plac?.
>
> En ce qui concerne la difference de temperature annonc? part la carte
> mere, il est normal qu elle soit legerement differente car moins
> precise. En effet la capteur de temperature du processeur est in?gr? a
> celui ci donc plus fiable.
> ==================================> As it is in French, I translate it roughly as : "the cause of the
> difference is that the second core is not used at all because the
> workload is too low. The core 1 temp is about the ambient temp.
> Regarding the difference between the temp of the core0 as seen by the
> AMD 64 sensor and the Mobo the cause is a difference in precision, the
> mobo being less precise/accurate thand the in CPU sensor."
Well is the 18C possible? Have you some heatpipes CPU?
You may for example load both CPUs running following command 2 times:
dd if=/dev/urandom of=/dev/null
dd if=/dev/urandom of=/dev/null
And see what happens. (Of course you need to have the SMP kernel)
Rudolf
^ permalink raw reply [flat|nested] 8+ messages in thread* [lm-sensors] Inconsistents results
2007-02-01 5:44 [lm-sensors] Inconsistents results Georges Giralt
` (5 preceding siblings ...)
2007-02-08 19:47 ` Rudolf Marek
@ 2007-02-08 20:21 ` Georges Giralt
6 siblings, 0 replies; 8+ messages in thread
From: Georges Giralt @ 2007-02-08 20:21 UTC (permalink / raw)
To: lm-sensors
Rudolf Marek a ?crit :
> Hello again,
>> Hi !
>> May I add the response from AMD regarding the difference between the
>> Core 0 temp and Core 1 temp ?
>> I quote :
>> ==================================
>> En ce qui concerne la diff?rence de temp?rature entre les deux core, il
>> semblerait que lors du test, un seul des core soit actif car la charge
>> de travail ne devait pas n?cessiter l activation du deuxieme core. En
>> effet 17? correspond a peu pres a la temperature de l environement ou` le
>> PC est plac?.
>>
>> En ce qui concerne la difference de temperature annonc? part la carte
>> mere, il est normal qu elle soit legerement differente car moins
>> precise. En effet la capteur de temperature du processeur est in?gr? a
>> celui ci donc plus fiable.
>> ==================================>> As it is in French, I translate it roughly as : "the cause of the
>> difference is that the second core is not used at all because the
>> workload is too low. The core 1 temp is about the ambient temp.
>> Regarding the difference between the temp of the core0 as seen by the
>> AMD 64 sensor and the Mobo the cause is a difference in precision, the
>> mobo being less precise/accurate thand the in CPU sensor."
>
> Well is the 18C possible? Have you some heatpipes CPU?
>
> You may for example load both CPUs running following command 2 times:
>
> dd if=/dev/urandom of=/dev/null
> dd if=/dev/urandom of=/dev/null
>
> And see what happens. (Of course you need to have the SMP kernel)
>
> Rudolf
>
>
>
Hi Rudolf !
The 18?C is quite true.
This is the temp a few seconds after boot up on a quite cold room.
The PC box is a Textrom with really ggod cooling properties and the CPU
is one of the latest AMD one, with rather low power disspiation (I think
it has the cooper wires inside).
i've tried, yesterday, to load the 2 core by compiling a big piece of
code with -g 3 flag. Unfortunatelly, I missed some required dependencies
so compilation aborted pretty soon, but the temp raised a bit.
Using the 2 dd above for 5 minutes raised temp like this :
8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:
+33?C
Core1 Temp:
+44?C
The 44 ?C is the highest record I've seen since I own this CPU ! Stop
Global warming !
The core 0 is raising slowly but I doubt it will reach the core 1 temp.
Regarding the SMP kernel, on Fedora bxes all kernels are SMP, so I'm
confident on this one.
Last but not least, I run X86-64 version of kernel (and OS, of course) I
wonder if this helps or not..
So all this to say I'm quite impressed by the AMD and the mobo. My
previous old Athlon 1700+ (0.18 ? ) was running hot (I should say
melting hot, regarding the figures I get with this one) So the gap is
quite huge...
Thanks for all your help, folks !
--
Ce message est constitu? d'au moins 50 % d'?lectrons recycl?s.
S'il vous pla?t, aidez nous a` conserver nos ressources,
recyclez vos ?lectrons !
^ permalink raw reply [flat|nested] 8+ messages in thread