Suspend no longer works after upgrade to 7.10

[Adam Petaccia]

I'm not sure if my issue is a duplicate of other's, but suspend no longer works on my system after upgrading to the latest -beta. This is on an AMD64 (64-bit install) with an nVidia card, proprietary drivers not loaded. I started running tests (gotten from http://www.mjmwired.net/kernel/Documentation/power/basic-pm-debugging.txt) in "recovery mode" to test Suspend / Resume:
Running:" echo reboot > /sys/power/disk; echo disk > /sys/power/state" reboots my computer, but trashes my swapfile. After re-running mkswap on /dev/hda4 (and adding resume=/dev/hda4 to grub command line), I am able to resume, but the text console is corrupted. Its difficult to describe, but pressing enter just scrolls the ubuntu logo (which never goes away) to the left. At the bottom, there is a garbled white strip with random pixel noise that increases by one pixel each time I press enter. It does look as if it responds to commands, though.

Runing: "echo test > /sys/power/disk; echo disk > /sys/power/state" brings the system back fine, repeatedly.

[Adam Petaccia (mighmos)]

Oops, test just locked the system -- it looks like its come back (cursor blinking) but it isn't responding to anything.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

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 does not yet have enough information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
4. Please follow https://wiki.ubuntu.com/DebuggingKernelSuspend .

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

[Adam Petaccia (mighmos)]

I'm not sure I can follow the instructions for debugging kernel suspend b/c AFAIK pm-trace is i386 only.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Ok thank you, I'm marking this as triaged and assigning to the kernel team.

[Igor (igor47)]

I am actually having very simular problems after upgrade to gusty beta from fiesty. This is on a Thinkpad X40. The Fn-F4 combo no longer works to suspend the machine - it doesn't appear to do anything as far as I can tell.

Attempting to suspend manually by doing "echo -n mem > /sys/power/state" suspend the machine. However, when it wakes up, I am logged out of my X session. I get the GDM(?) login screen, but there is a broad line of random noise across the top of the screen. The machine works, but all the windows are sort of jumbled around, with window decorations missing (metacity).

Linux mcfly 2.6.22-14-generic #1 SMP Tue Oct 9 09:51:52 GMT 2007 i686 GNU/Linux

[Igor (igor47)]

I am not sure how useful the debugging instructions will be since my machine successfully wakes up...

[Ketil Malde (ketil-ii)]

I have a Dell C810 (Core 2 Duo with a nVidia graphics card, using proprietary (nvidia-glx-new 100.14.19+2.6.22.4-14.9) drivers).

At work, it is connected to a docking station with an external monitor, and I can suspend (echo mem > /sys/power/state), release it, take it home, and wake it up by opening the lid. (I have to switch to a console and back to fix the display (Ctrl-F1 Ctrl-F7), but it was like that under Feisty, and I can live with that).

However, when I suspend it again and then resume, I'm unable to get the display working. I.e., the machine appears to wake up, but the screen stays black. This happens regardless of whether I connect to the docking station or not.

-k

[Ben Collins (ben-collins)]

Looks like a good candidate for the suspend/resume testing that will be available in the hardy kernel.

[Ketil Malde (ketil-ii)]

Resume now works for me if I switch to a text console before suspending. This is with the various suggestions from #34043 applied, don't know if they have any effect.

[Leann Ogasawara (leannogasawara)]

The Hardy Alpha2 release should be is available shortly (should be around Dec 20). If you could please test and verify if this issue still exists, that would be great. I'll update this report when Alpha2 is available. Thanks!

[Leann Ogasawara (leannogasawara)]

Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

[Adam Petaccia (mighmos)]

Suspend does the same thing on Hardy Alpha 2 as stable Gutsy -- drives spin down (but not fans, etc), but the machine never enters the final "standby" state.

[Leann Ogasawara (leannogasawara)]

Thanks for testing Adam. Care to attach the following information for the newer Hardy Alpha2 release. Please be sure to attach each file as a separate attachment.

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

It might also be helpful to capture and attach your dmesg output after you attempt to suspend/resume. Refer to the following link for more help: https://wiki.ubuntu.com/DebuggingKernelSuspend . For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

[Adam Petaccia (mighmos)]

I can't attach a dmesg, due to the fact that my machine fails to suspend, but dies halfway through.

Seems that hibernate works most of the time, but suspend just blanks the screen after switching to VT, the disks spin down, and then nothing happens. The machine is stuck in some half sleep state (possibly S1?) that can't wake up.

[Adam Petaccia (mighmos)]

Provided the needed information.

[Leann Ogasawara (leannogasawara)]

Thanks Adam. It would also be helpful if you could test the latest kernel and just verify the issue still exists and reattach an updated dmesg output after a failed suspend/resume cycle as you did previously. I'm reassigning to the kernel team. Also please note that we'll keep this open against the actively kernel but will be closed against 2.6.22. Thanks.

[Adam Petaccia (mighmos)]

What? I said I tested it with the Latest Alpha in Hardy and it didn't work! My machine hangs when I try to suspend. I can't attach a dmesg output. Why is this WONTFIX?

[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.

[Leann Ogasawara (leannogasawara)]

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".