[Dell Inc. Vostro 1700] suspend/resume failure

[Andres Mujica]

running stress log

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: Dell Inc. Vostro 1700
Package: linux-image-2.6.28-11-generic 2.6.28-11.38
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=b355fbdc-37c2-4b46-9f91-dd9b266858d5 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
SourcePackage: linux
Tags: resume suspend
Title: [Dell Inc. Vostro 1700] suspend/resume failure
UserGroups: libvirtd

[Leann Ogasawara (leannogasawara)]

Hi Andres!

I just wanted to check up on this bug and see if you are still having suspend/resume remains with the latest Karmic Alpha 4 - ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/ .

As you already know, the following might also help with debugging - https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume . Thanks!

[Andres Mujica (andres.mujica)]

Hi Leann, how are you?

i'll recreate the stress test this weekend to debug this further. However for normal usage the suspend and resume works about 95% of time. Some times the suspend fails when waking up and brings a gdm login screen or the battery dies before finishing the hibernate process (but that's more a g-p-m thing i believe)

I'm adding some new logs as a dupe from an hibernation failure

[Jeremy Foshee (jeremyfoshee)]

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 release http://www.ubuntu.com/getubuntu/download . 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.]