acpi/sensors temperature on nx6325

acpi/sensors temperature on nx6325

[Mircea Bardac]

Hi all,

I'm currently running kernel 2.6.21.3 on a HP nx6325.

I like having in the taskbar information about cpu/mem/temperature/etc. I 
found a strange behaviour monitoring the ACPI provided temperature. It 
currently shows for example 48C constantly, for lots of minutes. 

Doing a: dd if=/dev/urandom of=/dev/null increases the CPU usage and 
temperature should increase too. The ACPI temperature stays the same though.

I have also loaded the lm_sensors modules which, after some monitoring, appear 
to be working right, meaning "it shows an increasing temperature if the CPU 
usage increases".

# cat /proc/acpi/thermal_zone/TZ1/temperature && sensors
temperature:             48 C
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:
             +54°C
Core1 Temp:
             +53°C


The ACPI temperature increases only when the trip-point is reached. I hear the 
fans starting. When the fans stop, the temperature drops "hard" to the 
previous value.

I've changed the polling frequency to 1:
# cat /proc/acpi/thermal_zone/TZ1/polling_frequency
polling frequency:       1 seconds

I got the same effect: I can't see the temperature change dynamically, degree 
by degree. Also, in a test, the sensor went up to 60-65C and the trip-point 
did't activate. This was with polling set to 1.

If you need any more information, let me know.


Regards,
Mircea
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: acpi/sensors temperature on nx6325

[Mircea Bardac]

On Monday 11 June 2007 13:10:23 you wrote:
> I got the same effect: I can't see the temperature change dynamically,
> degree by degree. Also, in a test, the sensor went up to 60-65C and the
> trip-point did't activate. This was with polling set to 1.

Clarification:

Using a polling frequency of 1 second (*) I didn't see the ACPI temperature 
increase at all.


"sensors" has shown the temperature increasing, but reaching 60-65C the 
trip-point didn't activate.


* The frequency is measured in "times/second" or Hz.
Shouldn't "polling_frequency" be renamed to "polling_interval" if it is 
measured in seconds?


Regards,
Mircea

Re: acpi/sensors temperature on nx6325

[Maciej Rutecki]

[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

Mircea Bardac pisze:
> Hi all,
> 
> I'm currently running kernel 2.6.21.3 on a HP nx6325.
> 
> I like having in the taskbar information about cpu/mem/temperature/etc. I 
> found a strange behaviour monitoring the ACPI provided temperature. It 
> currently shows for example 48C constantly, for lots of minutes. 
> 
> Doing a: dd if=/dev/urandom of=/dev/null increases the CPU usage and 
> temperature should increase too. The ACPI temperature stays the same though.
> 
> I have also loaded the lm_sensors modules which, after some monitoring, appear 
> to be working right, meaning "it shows an increasing temperature if the CPU 
> usage increases".
> 
> # cat /proc/acpi/thermal_zone/TZ1/temperature && sensors
> temperature:             48 C
> k8temp-pci-00c3
> Adapter: PCI adapter
> Core0 Temp:
>              +54°C
> Core1 Temp:
>              +53°C
> 
> 
> The ACPI temperature increases only when the trip-point is reached. I hear the 
> fans starting. When the fans stop, the temperature drops "hard" to the 
> previous value.
> 
> I've changed the polling frequency to 1:
> # cat /proc/acpi/thermal_zone/TZ1/polling_frequency
> polling frequency:       1 seconds
> 
> I got the same effect: I can't see the temperature change dynamically, degree 
> by degree. Also, in a test, the sensor went up to 60-65C and the trip-point 
> did't activate. This was with polling set to 1.
> 

Similar on nx6310. Sometimes when I turn on laptop when CPU temperature
(first thermal zone - TZ0) is above 1st trip point the fan doesn't turn
on now, but only when second trip point was reached.

-- 
Maciej Rutecki
http://www.maciek.unixy.pl


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3265 bytes --]

Re: acpi/sensors temperature on nx6325

[Maciej Rutecki]

[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]

Thomas Renninger pisze:


[...]
> 
> BTW: Temperature passed through _TMP is:
> 1/10 Kelvin
> Means 40C is a value of:
> (273 + 40 ) * 10 = 3130 (0xC3A)
> You might search for a hard coded value like that which matches yours.

DSDT: http://www.unixy.pl/maciek/download/kernel/dsdt.dsl

_TMP and _ACx (for TZ0):
Method (_AC0, 0, NotSerialized)
{
Return (C300 (C2F6, Zero))
}

Method (_AC1, 0, NotSerialized)
{
Return (C300 (C2F5, Zero))
}
Method (_AC2, 0, NotSerialized)
{
Return (C300 (C2F4, Zero))
}
Method (_AC3, 0, NotSerialized)
{
Return (C300 (C2F3, Zero))
}
Method (_CRT, 0, Serialized)
{
Return (C300 (0x04, Zero))
}
Method (_TMP, 0, Serialized)
{
Return (C305 (Zero))
}

1st trip point is at 50*C=0xC9E (not found).

> 
> Which kernel are you using?
> Best you try the latest...

>From 2.6.16 to 2.6.21 and many -mm.

> 
> Is psmouse compiled as module?
> 
> Psmouse is known that it could interfere with ACPI on HP laptops and
> lm_sensor modules also. Is it better without?


Yes, I know this problem. Also is good idea compile i8042 as module [1]

[1] http://emisca.altervista.org/nx7400/ (other hp notebook)

> 
> If latest kernel is affected, you best open a bug bugzilla.kernel.org,
> attach dmesg, acpidump and everything else you find out. Pls CC me then.

Already I search solution for read-only trip points (control fans from
userspace)... [2]

[2] http://bugzilla.kernel.org/show_bug.cgi?id=8495 (rejected)

When I find any solution, then I think about test it. I don't risk using
latest kernel, when critical trip point is about 256*C...

-- 
Maciej Rutecki
http://www.maciek.unixy.pl

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3265 bytes --]

Re: acpi/sensors temperature on nx6325

[Thomas Renninger]

On Mon, 2007-06-11 at 21:58 +0200, Maciej Rutecki wrote:
> Mircea Bardac pisze:
> > Hi all,
> > 
> > I'm currently running kernel 2.6.21.3 on a HP nx6325.
> > 
> > I like having in the taskbar information about cpu/mem/temperature/etc. I 
> > found a strange behaviour monitoring the ACPI provided temperature. It 
> > currently shows for example 48C constantly, for lots of minutes. 
> > 
> > Doing a: dd if=/dev/urandom of=/dev/null increases the CPU usage and 
> > temperature should increase too. The ACPI temperature stays the same though.
> > 
> > I have also loaded the lm_sensors modules which, after some monitoring, appear 
> > to be working right, meaning "it shows an increasing temperature if the CPU 
> > usage increases".
> > 
> > # cat /proc/acpi/thermal_zone/TZ1/temperature && sensors
> > temperature:             48 C
> > k8temp-pci-00c3
> > Adapter: PCI adapter
> > Core0 Temp:
> >              +54°C
> > Core1 Temp:
> >              +53°C
> > 
> > 
> > The ACPI temperature increases only when the trip-point is reached. I hear the 
> > fans starting. When the fans stop, the temperature drops "hard" to the 
> > previous value.
> > 
> > I've changed the polling frequency to 1:
> > # cat /proc/acpi/thermal_zone/TZ1/polling_frequency
> > polling frequency:       1 seconds
A value of 1 sec is a bad idea, I remember a report were things got
stuck because of too high polling freq.
The HPs normally throw thermal events correctly, better disable it and
set it to 0.
> > 
> > I got the same effect: I can't see the temperature change dynamically, degree 
> > by degree. Also, in a test, the sensor went up to 60-65C and the trip-point 
> > did't activate. This was with polling set to 1.
> > 
> 
> Similar on nx6310. Sometimes when I turn on laptop when CPU temperature
> (first thermal zone - TZ0) is above 1st trip point the fan doesn't turn
> on now, but only when second trip point was reached.

I've sent a little How-To some days ago:
Documentation - How to debug ACPI Problems

Len, what is your opinion about the HowTo?
Will you add it as it is?

I'd start to disassemble the DSDT.
Have a look at the _TMP code. There often are hard coded temperature
values. I expect they come from some BIOS setting or could be triggered
through applications that access the fan/temp directly. It could also be
that your EC is confused or something else.

You could (see the HowTo):
 - 3.2.3 Using ACPI_DEBUG ASL debug object
   -> Go to the _TMP func and cluster everything with
   store (MONITOR_VAR, debug)

 - 3.2.4 Using ACPI_DEBUG acpi_dbg_layer and acpi_dbg_level kernel
   variables
   -> Go to drivers/acpi/thermal.c when the temperature is invoked,
   increase acpi_debug_level before evaluate_...("_TMP",..) is invoked
   and decrease it afterwards. Only set flags you think are useful, I'd
   start with exec, value, IIRC there also is some I/O or hardware
   access flag. Always let the last 5 bit set 0x1F 
   (err,warn,deb,info,..)

BTW: Temperature passed through _TMP is:
1/10 Kelvin
Means 40C is a value of:
(273 + 40 ) * 10 = 3130 (0xC3A)
You might search for a hard coded value like that which matches yours.

Which kernel are you using?
Best you try the latest...

Is psmouse compiled as module?

Psmouse is known that it could interfere with ACPI on HP laptops and
lm_sensor modules also. Is it better without?

If latest kernel is affected, you best open a bug bugzilla.kernel.org,
attach dmesg, acpidump and everything else you find out. Pls CC me then.

   Thomas

-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: acpi/sensors temperature on nx6325

[Len Brown]

> I got the same effect: I can't see the temperature change dynamically, degree 
> by degree. Also, in a test, the sensor went up to 60-65C and the trip-point 
> did't activate. This was with polling set to 1.
> 
> If you need any more information, let me know.

Try 2.6.22-rc5 with polling set to 0 and let me know if that doesn't work.

thanks,
-Len