Suspend to RAM is doing some cranky things on T43

[Matthew East]

Suspending to RAM is not working properly on the T43 (https://wiki.ubuntu.com/LaptopTestingTeam/ThinkpadT43-1871)

First of all, when I suspend and close the lid, it seems to sleep properly. Then when I open the lid, the computer seems to spring into life for a bit, then goes back to sleep. If I press the power button, then it starts resuming.

However, often when it resumes, it doesn't come up properly: I get a blank screen, or a screen with some garbled video output, but no X. This occasionally would happen in Breezy, but very rarely. Now it seems to be extremely frequent.

If I sleep and then resume immediately, it invariably works, but I think that sleeping for any long period of time fails.

Please tell me if I can provide any more details!

Matt

[Matthew Garrett (mjg59)]

Does editing /etc/defaults/acpi-support and changing POST_VIDEO to false help?

[Matthew East (mdke)]

I will try that change, and report back.

In the meantime, some more details. Basically, the various things I see happening are:

 * It resumes from suspend first time, no problem.
 * It tries to resume, then goes back to sleep. When I press the power button it either (a) wakes up ok, (b) gives me a black/slightly garbled screen, or (c) kicks me into a prompt with an X server error.

When (c) happened last, I saved the log, and will attach it to this bug.

Thanks

[Matthew East (mdke)]

The log from the failed resume, scenario (c).

[Matthew East (mdke)]

On Wed, 2006-04-19 at 18:00 +0000, Matthew Garrett wrote:
> Does editing /etc/defaults/acpi-support and changing POST_VIDEO to false
> help?

This hasn't helped.
--
<email address hidden>
gnupg pub 1024D/0E6B06FF

[DDC (coquet)]

This sounds like the double suspend bug.

https://launchpad.net/distros/ubuntu/+source/acpi-support/+bug/31935

Rather than pressing the power button, try doing a fn-f4 or pressing the lid switch in with a pen or something. It's odd that there seems to be a time factor involved. I've seen the same behavior where suspending for 5 minutes is ok, but an hour causes problems.

[Matthew East (mdke)]

This is now fixed