suspend to ram won't work anymore after upgrading to feisty

Bug #112659 reported by Mariano Draghi
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Brian Murray

Bug Description

Binary package hint: linux-source-2.6.20

After successfully upgrading to Feisty from Edgy on my laptop, suspend to ram doesn't work anymore.
Suspend to disk works (and it's much more reliable than in Edgy), but suspend to ram never works.

Whenever I start the suspend process (either by pressing Fn-Esc, lid-closing on battery power or from g-p-m), it seems to go well; screen blanks, wi-fi stops, fan stops, and power led starts to blink, but after one or two seconds, the laptop wakes up by itself. Upon unlocking the screen, I get an alert from g-p-m telling me that the computer failed to suspend.

My specs are: Dell Inspiron 640m, Ubuntu 7.04 with all the updates as of may 5th.

$ uname -a
Linux joyride 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

I skimmed through many bugreports here at launchpad, and on Ubuntuforums, but none of the problems reportes seem to be like mine. The closest bug I could find is #95594, where the OP also reports that the laptop wakes up immediately. But he's reporting other issues after the restart, which I don't have.

The strange thing is that as per some reviews in LaptopTestingTeam, and my own experience with Edgy on this very same hardware, suspend to ram should work fine.

Revision history for this message
Mariano Draghi (chaghi) wrote : sudo lspci -vvnn
Revision history for this message
Mariano Draghi (chaghi) wrote : dmsg
Revision history for this message
Mariano Draghi (chaghi) wrote :

After further diggin' in launchpad, now I'm think that this might be a duplicate of #89983. But I'm not sure.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug does not meet the criteria for a stable release update and is being marked as Won't Fix for this particular version of the kernel. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates .
However, the issue that you reported is one that should be possible to test with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed kernel. You can find out more about the development release at http://www.ubuntu.com/testing/ .
If you do decide to test with the development release of Ubuntu please comment on this bug report and include at least the minimal information requested at http://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help.

Changed in linux-source-2.6.20:
assignee: nobody → brian-murray
importance: Undecided → Medium
status: New → Won't Fix
Revision history for this message
Mariano Draghi (chaghi) wrote :

Brian, thanks for your comments.

Last time I checked (with Feisty LiveCD, actually), this kind of thing couldn't be tested with the LiveCD, because suspend and hibernation were disabled. Is this now enabled in Gutsy LiveCD, *without* installing it?

I'm willing to give Tribe 5 a spin... but only if someone can confirm that this features are enabled on the Live CD.

Revision history for this message
Brian Murray (brian-murray) wrote : Re: [Bug 112659] Re: suspend to ram won't work anymore after upgrading to feisty

On Thu, Aug 30, 2007 at 02:27:32AM -0000, Mariano Draghi wrote:
> Brian, thanks for your comments.
>
> Last time I checked (with Feisty LiveCD, actually), this kind of thing
> couldn't be tested with the LiveCD, because suspend and hibernation were
> disabled. Is this now enabled in Gutsy LiveCD, *without* installing it?

That is why I mentioned it, however only Suspend aka suspend to RAM will
be testable. As there is no physical drive partition used for swap the
Live CD, Hibernation aka suspend to disk will not be testable.

Revision history for this message
Mariano Draghi (chaghi) wrote :

I can confirm that suspend to ram works again in Gutsy Tribe 5.

I have some (minor?) issues after resume:

 * Sometimes (but not always) g-p-m will pop the notification telling me that the computer failed to suspend, which is wrong.

 * Sometimes (but not always) I get a black screen, and I have to swhich back-and-forth from virtual screen 7 to a text console to get video again.

 * The sound is muted, always.

 * After resume, something with the wireless subsystem ends up totally messed up, and I can no longer connect to my wireless network.

... but I assume all of those are not kernel bugs, and have to do more with hal and/or the suspend/resume scripts or something.

Revision history for this message
Brian Murray (brian-murray) wrote :

On Sat, Sep 01, 2007 at 06:38:40PM -0000, Mariano Draghi wrote:
> I can confirm that suspend to ram works again in Gutsy Tribe 5.
>
> I have some (minor?) issues after resume:

It would be helpful if you were to submit all of these issues as
separate bug reports so we can work on getting them resolved in Gutsy.

> * Sometimes (but not always) g-p-m will pop the notification telling me
> that the computer failed to suspend, which is wrong.

The package for that bug should be gnome-power-manager.

> * Sometimes (but not always) I get a black screen, and I have to swhich
> back-and-forth from virtual screen 7 to a text console to get video
> again.

The package for that bug should be xorg, please include
'/etc/X11/xorg.conf' and '/var/log/Xorg.0.log' after resuming.

> * The sound is muted, always.

The package for that bug would be linux-source-2.6.22, please include
the output requested at https://wiki.ubuntu.com/DebuggingSoundProblems .

> * After resume, something with the wireless subsystem ends up totally
> messed up, and I can no longer connect to my wireless network.

This could be network-manager or your wireless driver.

> ... but I assume all of those are not kernel bugs, and have to do more
> with hal and/or the suspend/resume scripts or something.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.