[ubuntu lucid beta 2] Suspend to ram not working

Bug #562145 reported by a_user
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned
Nominated for Lucid by Brett Johnson

Bug Description

Using latest Ubuntu lucid beta i tried suspend to ram and hibernate. Suspend to ram prepares properly to go to sleep, but at the moment when it should power off most hardware components it simply does nothing, black screen. Pressing the power button or any keybord key has no reaction. I'm forced to manually reboot.

I looked into the pm-suspend.log file but it seems to report all went fine. On the same machine i can boot into karmic. There suspend works perfectly.

Regarding hibernate i encounter similar things. It also does not power down but, due to saving to disk, after i reboot it restores the system. but it does not restore it perfect as tehre are several services that are broken after resume, like alsa.

i attached the log file after such a failed suspend to ram:

Revision history for this message
a_user (a-user-sci) wrote :
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 did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
a_user (a-user-sci) wrote :

sorry. i didn't knew what package to assign. but linux seems logical now. i will consider this in the future.

Revision history for this message
a_user (a-user-sci) wrote :

any news on this? is this currently in investigation? i read in forums that i'm not alone with this or similar problems. i really would like to know this being fixed on final release because otherwise i would be forced to keep karmic.

Revision history for this message
Brett Johnson (linuxturtle) wrote :

I'm seeing the same symptoms, on apparently different hardware. My pm-suspend.log attached...

tags: added: kernel-suspend
tags: added: kj-triage
Revision history for this message
Brett Johnson (linuxturtle) wrote :

Something in the last couple days' updates seems to have resolved this problem for me -- maybe the libdevmapper update? Not sure. In any case, suspend/resume seem to be working again, at least for me.

Revision history for this message
a_user (a-user-sci) wrote :

for me till yesterday night it was still not resolved. well, final release is tomorrow. am curious if it has been fixed.

Revision history for this message
a_user (a-user-sci) wrote :

well, fresh new install: it is not fixed.

additionally i found a new issue that seems to be related to this:

installing ubuntu lucid worked perfect up to the point where i was asked to reboot. i pressed enter to start rebooting. the dialog with the "start reboot" button vanished and that's it... frozen. mouse still moveable but no reaction on "str+alt+del" or switching to terminals. only pressing reset button worked.

i think this might be releated cause maybe there is a deeper pwoering off problem, maybe an acpi problem. but i may be totally wrong.

well, anyhow the problem with suspend and hybernate are still present and it still works on same machine with karmic.

Revision history for this message
a_user (a-user-sci) wrote :

New infos on the problem:
using the mainline kernel 2.6.33 or 2.6.34 fixes this. with that kernels suspend and hibernate are working.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi a_user,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 562145

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
a_user (a-user-sci) wrote :

currently i cannot try what you suggested but i can provide some informations from some previous testing.

i found out that with the latest ubuntu kernel (i guess) 2.6.32.22 (right?) this issue is still active. but using kernels 2.6.33 or above (including latest kernel.org upstream kernel) the issue has gone.
so this problem only occures with the 2.6.32 kernels.

i cannot say when i have the time to test it with the suggested methods to give you more information. currently i got too much to do.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
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.