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]
Date:	Wed, 30 Apr 2008 11:51:10 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	Kasper Sandberg <lkml@...anurb.dk>,
	Rudolf Marek <r.marek@...embler.cz>,
	Maxim Levitsky <maximlevitsky@...il.com>, trenn@...e.de,
	Len Brown <lenb@...nel.org>, Matthew <jackdachef@...il.com>,
	linux-acpi@...r.kernel.org, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, "Zhang, Rui" <rui.zhang@...el.com>
Subject: Re: Linux 2.6.25 (coretemp reads high temperatures)

On Wed, 30 Apr 2008, Jean Delvare wrote:
> On Wed, 30 Apr 2008 02:11:14 +0200, Kasper Sandberg wrote:
> > On Wed, 2008-04-30 at 00:14 +0200, Rudolf Marek wrote:
> > > Well again, I tried hard at Intel and I really could not get any info on some
> > > calibration bit. The temperature is non-physical on arbitrary scale. I changed
> > > that so for some people it jumped to 100C, for some it remained.
> > 
> > So, im confused.. The reason for this is that the internal sensor is
> > operating on some sort of weird scale, and thus when you interpolate it
> > into "your" scale, it doesent quite come out in the actual degrees
> > celcius the cpu temperature really is?
> 
> It's really only an offset, rather than scaling. The temperature
> reported by the Core and Core2 CPUs is a relative temperature. It tells
> how far you are from the maximum temperature the CPU can survive. The
> value is expressed in (relative) degrees C.

Ah, please ignore my email about ITUs (Intel thermal units), then.  The
above means 1ITU=1°C, but their zeros are at different places.

> Rudolf did his best to find out the (absolute) temperature each CPU
> model can survive (known as TJmax) so that the coretemp driver can
> provide an absolute temperature to user-space, as all other hardware
> monitoring drivers do. Our hope was to limit the confusion, but it
> seems we failed ;) Maybe it would be better if the driver was reporting
> the relative temperature value directly when we don't know the TJmax
> value for sure - but then all user-space tools would need to learn how
> to deal with this.

Actually, just libsensors would, and the local admin can adjust it at
will using the config file.

Nobody in userspace should be reading hwmon sysfs directly without the
use of libsensors.  If they are, it is their bug, and it is unsupported
AFAIK.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ