linux-kernel - Re: Useless thermal acpi driver ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B20483C.6090309@gmail.com>
Date:	Wed, 09 Dec 2009 19:00:44 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	"J.A. Magallón" <jamagallon@....com>
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Useless thermal acpi driver ?

On 12/09/2009 04:26 PM, J.A. Magallón wrote:
> Hi all...
>
> I have a couple boxes where the thermal acpi driver gives this:
>
> bran:~>  sensors
> acpitz-virtual-0
> Adapter: Virtual device
> temp1:       +26.8°C  (crit = +100.0°C)
>
> bran:~>  acpi -t
> No support for device type: battery
>       Thermal 1: ok, 27.0 degrees C
>
> It stays _always_ the same, there is no difference if I run some number
> crunchin, or even if one of them is overclocked from 2.8 to 3.0 GHz.

There are systems where an ACPI thermal zone exists but isn't really 
hooked up to anything and just reports some dummy temperature value. My 
old system reported 40 degrees C no matter what. (I think it's something 
like the thermal zone support is part of the standard ACPI DSDT template 
the mobo maker got from the BIOS developer and they effectively disabled 
it by putting in the dummy temperature.)

> They are 1U supermicro boxes, ventilation is good, but I don't trust this
> measures...
> It looks like the system is using some kind of 'generic' acpi TZ driver,
> but as I'm used to good-ol' sensors modules, I don't know where to look.
>
> Previously I used the w83627hf module from sensors.

I'm assuming the kernel is preventing that module from loading since the 
ACPI DSDT has operation regions that refer to the device registers. 
There's no guarantee that this means the BIOS actually accesses the 
device, or if it does, that there's a way to get it to report what it 
sees other than to itself. If the BIOS doesn't actually access the 
device then you can use the acpi_enforce_resources=lax to allow it. The 
problem is this might be totally unsafe and the kernel has no way to 
tell if it is or isn't.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/