Package: linux-image-2.6.12-1-amd64-k8 Version: 2.6.12-1 (and I suspect also later kernels)
Hardware Environment: HP nx6125 (AMD Turion ML 34, ATI Radeon express 200M chipset, onboard ATI X300) Software Environment: Kernel 2.6.12-1-amd64-k8 (booting with no_timer_check to avoid double timer interrupts), Debian amd64 (testing/unstable), WM = KDE 3.4.2. Problem Description: ACPI thermal events rarely get processed, especially under moderate to high CPU load. This results in *no* or erratic fan use and potential (cumulative) damage to the machine/electronics. However, if the CPU temperature exceeds a thermal trip point and then one issues a cat /proc/acpi/thermal_zone/TZ?/temperature or an acpi -t, then, after a brief machine pause, the thermal event is processed by the kernel and the fans respond. This can be observed by stopping acpid and doing a cat /proc/acpi/event, which gives the most graphic evidence. A further and more detailed desciption/diagnosis of the problem can be found here ==> http://lists.debian.org/debian-amd64/2005/10/msg01002.html Steps to reproduce: With a warm processor < 58 degrees C (less than first thermal trip point), run glxgears and wait about a minute or so. Your fan will 90% of the time not kick in. Then execute an acpi -t or a cat /proc/acpi/thermal_zone/TZ?/temperature and almost immediately you will observe that (i) at least one of your thermal trip points have been exceeded and (ii) as a response to the cat command, the fans immediately turn on. Visual evidence can be had by first, before you do anything, stopping acpid and doing a cat /proc/acpi/event (as root). Then do the above procedure. You will observe no thermal event register *until* you do the cat or acpi -t. Background info: I am using Debian GNU/Linux 3.1 (testing/unstable) with kernel 2.6.12-1-amd64-k8. I have also tried vanilla kernels from (www.kernel.org) up to 2.6.14.1 and all exhibit this same problem. I have reported this bug to bugzilla.kernel.org (bug # 5534), but nothing has been done as yet. I have looked very briefly at the amd64 acpi thermal code and it seems that the behaviour is to poll the thermal zones (TZs) at various time intervals (I could be wrong). My guess is that somehow the time interval calculation gives a time interval which is too large and hence the kernel seldom polls the TZs. I will gladly provide other info if required. I'd really like to get this bug fixed. Richard -- Richard Mace School of Physics, University of KwaZulu-Natal, Howard College Campus Durban 4041, South Africa Tel.: +27 (0)31 260 1402 FAX: +27 (0)31 261 6550 -------------------------------------------------------------------- Please find our disclaimer at http://www.ukzn.ac.za/disclaimer -------------------------------------------------------------------- <<<<gwavasig>>>> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]