> I need the acpi trace log before _PTS to see what kind of thermal > related methods got called. Alas, I've included all the dmesg's. Below is the script that I use to enter S3 sleep. It unloads rid of troublesome modules and stop services that don't sleep well. Then (for debugging) it sends the kernel version and boot parameters across the serial console (the @@@@ SLEEP line), raises the debug level to 0x1F, does a sync (in case the sleep hangs, since this is my production machine), and then enters mem sleep. So nothing in it should trigger any thermal methods; except that I usually have the THM2 trip point raised to 45C with a polling time of 100 seconds. So once in a while a thermal poll will happen sleep is being set up. I am not sure whether it would be reported in the dmesgs if it happened; but the S3 failure happens much more often than such a thermal polling would happen, so I doubt the S3 failure requires a thermal poll. #!/bin/bash -x # S3 (suspend to memory), with cleanups before and after sync ifdown eth0 remove='prism54 xircom_cb xircom_tulip_cb' remove2='snd_pcm_oss snd_cs46xx' modprobe -rv $remove modprobe -rv $remove2 /etc/init.d/chrony stop > /dev/null sleep 1 (echo "@@@@ SLEEP" ; date ; uname -a ; cat /proc/cmdline ) > /dev/tts/0 echo 0x0000001F > /proc/acpi/debug_level sync sleep 2 echo -n mem > /sys/power/state [stuff for wakeup snipped] - : send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
