Most recent kernel where this bug did not occur: N/A Distribution: Debian Hardware Environment: Thinkpad G41 Software Environment: Debian testing Problem Description: This has happened with both suspend2 and swsusp. If I suspend every night instead of shutting down normally or leave my laptop running, the CPU starts to become sensitive. That is, it starts to overheat easily, producing "temperature above threshold" warnings. I'm not worried that my CPU will overheat since the P4 is protected from it, but I'm worried about other components in my laptop that are close to the CPU from being damaged. Also it wastes more energy as well as killing my battery. If I shutdown and let my computer rest, it has no problems. It is also fine if I let my laptop run for days or months. But if I start using suspend to disk, on startup the CPU runs hotter. Normal operation (after shutdown) it about 46C to 54C, after suspend it runs in the 60s and with some network traffic will go into the 70s and sometimes into the 80s. Steps to reproduce: Suspend to disk, resume. I'll let my system cool down again, and then see if it does it on the first resume or if it takes a few times to get it going. But since I'm writing this on my effected laptop, I will have to add a comment to say how long it takes to cause a problem.
Please cat /sys/power/disk. if it is "platform", please change it to "shutdown" mode, and report back any difference.
$ cat /sys/power/disk shutdown It's already in shutdown mode.
i don't suppose that suspend to RAM works on this box and behaves differently?
Sorry, suspand to ram works, but resume from ram does not :(
could you try if "platform" in /sys/power/disk works?
Please reopen this bug if: - it is still present in kernel 2.6.18 and - you can provide the requested information.