[LENOVO 766734M] suspend/resume failure

[Michael Gratton]

Suspend/resume is working 4-5 times then the machine refuses to suspend unless I issue "/etc/acpi/sleep.sh force" as root. However after doing this the machine appears to resume, but X never makes it back. After power cycling, this error report is generated.

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: LENOVO 766734M
Package: linux-image-2.6.28-11-generic 2.6.28-11.41
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=8597dd3d-4bf8-4ed9-9f26-d51914282af0 ro acpi_sleep=s3_bios quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.41-generic
SourcePackage: linux
Tags: resume suspend
Title: [LENOVO 766734M] suspend/resume failure
UserGroups:

[Jim Lieb (lieb)]

Can you confirm this issue exists with the most recent Karmic Koala 9.10 Beta release? ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/ . If the issue remains with Karmic it would be great to then also test the latest upstream mainline kernel available. This will allow additional upstream developers to examine this issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Thanks in advance.

[Michael Gratton (mjog)]

I haven't had this problem with my X61s 766734M since before jaunty.

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