Bug 5112
Summary: | S3 resume eventually resets thermal parameters | ||
---|---|---|---|
Product: | ACPI | Reporter: | Sanjoy Mahajan (sanjoy) |
Component: | Power-Thermal | Assignee: | Konstantin Karasyov (konstantin.karasyov) |
Status: | REJECTED INVALID | ||
Severity: | normal | CC: | acpi-bugzilla |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.13-rc6 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: |
acpidmp output
DSDT debug info patch |
Description
Sanjoy Mahajan
2005-08-22 07:14:47 UTC
Created attachment 5724 [details]
acpidmp output
Created attachment 6697 [details] DSDT debug info patch It is not clear if the trip points are updated by _WAK method, i.e. on system's wakeup, or under another circumstances. Here is the DSDT debugging patch. It adds debug prints on trip points updates (i.e. Notify(.., 0x81)) and trip point methods calls (i.e. _AC0, _PSV) for thermal zones THM0, THM2. Boot with option acpi_debug=0xffffffff just to be sure ;) To see the corelation between BIOS and kernel, please use the applied DSDT patch with this one: http://bugzilla.kernel.org/attachment.cgi?id=6678&action=view Sorry this response took so long. In the last few weeks I'd noticed a new but related problem: the trip point would revert to the default even if the laptop had never been to sleep (in addition to the usual behavior of doing it a while after waking up). I just switched to 2.6.15 and the new problem went away. However, the old problem of the trip points changing after wakeup is still there. Here's the dmesg output right after wakeup. The kernel and DSDT's have the patches you gave and I booted with acpi_debug=0xffffffff. [ACPI Debug] String: [0x26] "------- TWAK: Notify (\_TZ.THM0, 0x81)" ------------------ Got thermal event 0x81 [ACPI Debug] String: [0x26] "------- TWAK: Notify (\_TZ.THM2, 0x81)" [ACPI Debug] String: [0x1B] "------- THM0._PSV: 00000E49" [ACPI Debug] String: [0x1B] "------- THM0._AC0: 00000E30" ------------------ Got thermal event 0x81 [ACPI Debug] String: [0x1B] "------- THM0._AC0: 00000C32" ------------------ Got thermal event 0x81 ------------------ Got thermal event 0x81 Here's the dmesg output after the latest change, which was 30 minutes after waking from S3 (the wake script puts up the trip points, so the output below is from when they spontaneously dropped back to the default, or maybe a bit after in case the temperature wasn't high enough when they dropped back): [ACPI Debug] String: [0x26] "------- _Q42: Notify (\_TZ.THM2, 0x81)" ------------------ Got thermal event 0x81 [ACPI Debug] String: [0x1B] "------- THM0._AC0: 00000BFB" ------------------ Got thermal event 0x80 -Sanjoy Well, the trip points are being updated by the _WAK method on wakeup (first case), and by the event _Q42 from the embedded controller (second case). I don't know the reason of the trip points reseting, possibly to prevent too high thermal limit setting. To avoid it you can comment out appropriate code lines and re-compile the DSDT. |