suspend to ram doesn't work--computer keeps running

[Bogdan Butnaru]

Hello! This is about latest Ubuntu on a Dell Latitude D620:

Suspend-to-RAM used to work OK on Gutsy, and it worked on Hardy, too. However, a few updates ago it stopped working (I didn't notice it immediately). When I suspend the computer, everything seems to be prepared for sleep, but the screen turns black with an underscore cursor (the backlight is still on), and the computer doesn't turn off. It doesn't respond to keys, but if I close the lid and open it again it acts just as it would when “resuming”, and gives me the login prompt. I looked around a bit, and I found Bug #67710, which looks very much like my problem: the posters there report having Intel 9xx chipsets, one even has exactly the same laptop. However, on that bug suspend apparently works, and resume doesn't. Here, it seems the reverse is happening.

$ uname -a
Linux arioch 2.6.24-19-generic #1 SMP Wed Jun 4 16:35:01 UTC 2008 i686 GNU/Linux

[Bogdan Butnaru (bogdanb)]

Here is what appears in /var/log/messages after a suspend attempt.

(I pressed suspend and waited for everything to settle (in the black screen with blinking white underscore state). Then I closed and reopened the lid, got the password dialog, entered the password. Then I posted this bug.)

[Nick Ellery (nick.ellery)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information requested at [WWW] https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

[Bogdan Butnaru (bogdanb)]

OK, here they come. By the way, I noticed two more things yesterday:

1) Hibernate works, even though suspend doesn't
2) Probably irrelevant, but: just before the screen turns black (both for hibernate and suspend) it turns bright green for a fraction of a second. This never happened before.

[Bogdan Butnaru (bogdanb)]

The hibernate moment is when the timestamp jumps from 2 AM to 9 AM.

[Bogdan Butnaru (bogdanb)]

Oh, I forgot, the /var/log/kern.log I just added also contains at least one suspend attempt, before the successful hibernate. Compare the timestamps with those in var-log-messages above (the suspend attempts are marked by a message from the power manager).

This is the final attachment; note that "# cp -r /proc/acpi/ tmp/" gave a certain error:
cp: cannot open `/proc/acpi/event' for reading: Device or resource busy

[Nick Ellery (nick.ellery)]

Thanks for your bug report.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Ralph Janke (txwikinger)]

The Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27 Ubuntu kernel. It would be great if you could test and verify if this is still an issue. The status is being set to Incomplete until we receive further feedback. Thanks.

[Bogdan Butnaru (bogdanb)]

Hello Ralph, I haven't noticed this on Intrepid in the last month or so. I assume it's fixed, since nobody else mentioned it.

[Kazupon (kazupon-up)]

This problem is almost same problem that I have.

architecture: i386
nonfreedriver: ATI radeon
linux version 2.6.24-23