[ Digression from testing Alexey's patch that makes the Evo work again with two separate threads ] On Mon, 20 Nov 2006, Linus Torvalds wrote: > > Ok, this one works for me too, and looks much simpler. Hmm. Some more testing shows that fan behaviour after a suspend-to-ram event seems broken, but I suspect the breakage isn't new. It seems that ACPI remembers fan state from before the suspend, and then (incorrectly) uses that to decide whether it should turn fans on or off. So for example, it seems to remember that the fan was already on, so it won't ever turn it on again - even though the suspend will obviously have turned off all fans too. So after running for a while, I get (for example): cat /proc/acpi/thermal_zone/TZ1/* .. state: active[0] temperature: 92 C critical (S5): 99 C passive: 95 C: tc1=1 tc2=2 tsp=100 devices=0xf7e42338 active[0]: 80 C: devices=0xc18d78ec active[1]: 70 C: devices=0xc18d7888 active[2]: 60 C: devices=0xc18d7838 active[3]: 45 C: devices=0xc18d77e8 (it thinks all fans are on), but no fans are actually on: cat /proc/acpi/fan/*/* status: off status: off status: off status: off Of course, I'm not exactly having a lot of trust in ACPI in general, so for all I know this is just more unfixable crap from the firmware. But it smells like "I remember state from before the suspend". Linus - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html