Kernel Bug Tracker – Bug 7194
ACPI related problems (Thermal, Fan, BIOS Bad State) with recent HP Laptops
Last modified: 2007-02-15 22:52:33 UTC
Most recent kernel where this bug did not occur: none AFAICT
Hardware Environment: HP nx6325, AMD Turion X2, latest F.02 BIOS
Software Environment: 32-bit, SMP, preempt Kernel
This is meant as a collection of different bugs to have it all in one place. I
hope that's ok.
wich are all related and fit exactly my problems. Which are:
- Thermal events won't get processed. Running CPU hogs won't result in higher
fan speed due to rising temperature. Thermal events won't get processed because
there simply are none until I do a cat /proc/acpi/thermal_zone/TZ*/*. Battery
state does trigger events and does get processed. So do lid switch and power botton.
Doing an echo 1 > /proc/acpi/thermal_zone/TZ1/polling_frequency results in no
updates of temps and fan state at all anymore.
The original F.00 BIOS had many DSDT related problems that showed during iasl
-dc but F.02 is much better with 0 errors and warnings (only a disassemble problem).
In 2.6.16 and ealier 2.6.17 kernels, without patching the only trip point that
got processed was the 105
Created attachment 9085 [details]
Created attachment 9086 [details]
Created attachment 9087 [details]
lspci -vv output
Created attachment 9088 [details]
cat thermal zones
Created attachment 9089 [details]
Created attachment 9090 [details]
Pointing to thermal and fan:
Do the thermal/fan related problems persist with the patches in comments #159
and #160 from bug #5534 and in comments #37 and #38 from bug #7122?
Thermal / fans are ok with patches in comments #159 and #160 from bug #5534.
Changed back to non-suspend kernel. So didn't test comments #37 and #38 from bug
Did you have any luck trying suspend/resume patches from bug #7122
Sorry, no. Quite busy. I'll see if I can try it tomorrow.
Please note, that there were several updates for that bug. The patches you'll
need are the following:
Since there is no responce from submitter, and patches are already available
for described problems (refer to bug #7122, #7570), I'm setting the status of
this bug to RESOLVED.
Please, re-open if problem persists with the patches from the above bugs
*** This bug has been marked as a duplicate of 7122 ***