Date:	Sat, 02 Jun 2012 10:34:41 +0200
From:	Clemens Ladisch <clemens@...isch.de>
To:	Mark B <markieb.lists.20090330@...il.com>,
	Zhang Rui <rui.zhang@...el.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: thermal_zone trip_point_0_temp 200°C

Mark B wrote:
> My Acer Aspire 5552-7260, AMD phenom II N970 cpu, is giving me very
> bizarre temp limit readings; the main reason I'm noticing it is that
> it is heating up to 70° without much of a load, 63° at startup under
> virtually no load; works well in windows, 48° as equivalent to the
> linux 63°, so my gradual conclusion is that it's some kernel-level
> code that needs changing?
>
> Can't fancontrol/pwmconfig as apparently — from my limited knowledge
> of how to double-check, I've tried looking in all the relevant /sys
> nodes — there are no pwm-capable fans; lm_sensors, however, gives the
> 200°C temp limit as does acpiclient; I'm noticing that there are some
> kernel patches affecting the area, although it is unclear to me how
> far that would even make it the kernel's responsibility; I've tried
> all the acpi_osi=Linux, acpi_osi="Linux", acpi_osi=\\\"Linux\\\",
> acpi_enforce_resources=lax, acpi.power_nocheck=1 alternatives without
> sign of change; as I recalled from my eeepc that that was the way of
> preventing the newer, non-fully-functional, acpi kernel module, from
> loading, forcing legacy acpi/pwm support; in fact the overheating
> eeepc is one more reason I'm writing to the kernel list now, as I'm
> seeing a kind of pattern of computers overheating in linux when in
> principle all that it should need would be faster fan speeds / lower
> soft limits;
>
> Looking carefully at the modules list, I see k10temp as the most
> obvious sensor module, unsure how relevant that is

The k10temp module provides nothing but a sensor for monitoring
applications.  Your thermal zones are managed by the acpitz driver,
which is compiled into the kernel and uses its own sensor.

> my understanding of it is that the Kernel/the Bios manages the fan
> speed in 'automatic' mode, as distinguished from fancontrol-type
> 'manual' mode; given that windows manages it properly, I'd have to
> conclude it wouldn't normally be the Bios's fault?

The ACPI tables are provided by the BIOS.

For documentation about the thermal zone files, see
<Documentation/thermal/sysfs-api.txt>.

> $ cat /proc/version
> Linux version 3.3.7-1.fc17.x86_64
> (mockbuild@...-11.phx2.fedoraproject.org) (gcc version 4.7.0 20120507
> (Red Hat 4.7.0-5) (GCC) ) #1 SMP Mon May 21 22:32:19 UTC 2012
>
> $ grep -r . /sys/class/thermal/thermal_zone*
> /sys/class/thermal/thermal_zone0/power/async:disabled
> /sys/class/thermal/thermal_zone0/power/runtime_status:unsupported
> /sys/class/thermal/thermal_zone0/power/runtime_usage:0
> /sys/class/thermal/thermal_zone0/power/runtime_active_kids:0
> /sys/class/thermal/thermal_zone0/power/runtime_enabled:disabled
> /sys/class/thermal/thermal_zone0/power/control:auto
> /sys/class/thermal/thermal_zone0/power/runtime_suspended_time:0
> /sys/class/thermal/thermal_zone0/power/runtime_active_time:0
> grep: /sys/class/thermal/thermal_zone0/power/autosuspend_delay_ms:
> Input/output error
> /sys/class/thermal/thermal_zone0/type:acpitz
> /sys/class/thermal/thermal_zone0/temp:62000
> /sys/class/thermal/thermal_zone0/mode:enabled
> /sys/class/thermal/thermal_zone0/trip_point_0_type:critical
> /sys/class/thermal/thermal_zone0/trip_point_0_temp:200000
> /sys/class/thermal/thermal_zone0/trip_point_1_type:passive
> /sys/class/thermal/thermal_zone0/trip_point_1_temp:90000
> /sys/class/thermal/thermal_zone0/cdev0_trip_point:1
> /sys/class/thermal/thermal_zone0/cdev1_trip_point:1
> /sys/class/thermal/thermal_zone0/cdev2_trip_point:1
> /sys/class/thermal/thermal_zone0/cdev3_trip_point:1


Regards,
Clemens
--
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