http://bugzilla.kernel.org/show_bug.cgi?id=10658
------- Comment #64 from [EMAIL PROTECTED] 2008-09-07 03:36 ------- (in reply to comment #61) > Another idea specific to this ASL implementation: > There is exactly one way how BIOS can tell the OS to check for the temperature > asynchronoulsy (without polling). This is: > \_GPE._L1D # HW issues an ACPI (SCI) interrupt with id 0x1D > +-> NEVT() > +-> SMIE() > +-> Notify (\_TZ.THM, 0x80) > > Has there already been double checked whether thermal acpi events come in > through /proc/acpi/event (couldn't find anything by a quick search in this > bug) Bingo! Yes, as the chip heats up, the count in /sys/firmware/acpi/interrupts/gpe1D starts increasing. Then the following come through on /proc/acpi/event as the chip heats up and then Matthew's patch causes it to be throttled: processor CPU0 00000080 00000001 processor CPU0 00000080 00000000 Presumably this is what Windows is using to detect the overheat on this machine, then. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
