[LENOVO 7764CTO] suspend/resume failure

Bug #355275 reported by Ken Tanzer
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This morning my laptop failed to resume after going to sleep following inactivity.

This had been working great on 9.04b. It generally worked on 8.10 too, but with 8.10 sometimes networking would be disabled after resuming, which has not been the case with 9.04b.

Sorry I'm really not able to give much details or clues. I know that suspend/resume is something you're looking hard at, though, so I'm reporting it anyway. It's a Thinkpad X61, and it was plugged into its docking station.

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 7764CTO
Package: linux-image-2.6.28-11-generic 2.6.28-11.38
ProcAttrCurrent: unconfined
ProcCmdLine: root=/dev/mapper/datafarm-ubuntu_root 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
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: [LENOVO 7764CTO] suspend/resume failure
UserGroups:

Revision history for this message
Ken Tanzer (ktanzer) wrote :
Revision history for this message
Craig Magina (craig.magina) wrote :

I also experience this issue. I experienced it with Fedora 10 as well. I run the 64-bit systems of both. From what I can tell, it has something to do with docking and undocking. If I do not dock the system, I can suspend and resume as much as I want. Same goes for when I boot it in the dock and leave it there, just suspending and resuming it. But, if I dock or undock the system will not resume.

Revision history for this message
epv (epvubuntu) wrote :

in case anyone cares. it fails to resume most times (but not always) if it's been docked before it was suspended. I.e., laptop is docked; press undock button, wait for green light, remove from dock. syslog shows undocking works (usb instances disappear, Xorg notices changed video situation and adjusts, etc.) Laptop is now runinng undocked. Press fn-f4 to cause powermanager to trigger sleep. Laptop suspends. Try to resume --> screen powers up to text mode, blinking cursor, no X. (presumably it fails somewhere before the chvt back to the X screen) No disk access visible according to the disk activity LED. ctrl-alt-fN does not switch consoles. pushing power button does not run shutdown. keystrokes do not echo. Only recovery is to hold power button until hard power-off, then power back on.

Revision history for this message
epv (epvubuntu) wrote :

Just an update. It does in fact fail to resume from suspend any time it has been docked since booting.

Revision history for this message
^_Pepe_^ (jose-angel-fernandez-freire) wrote :

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 Karmic 9.10 release of Ubuntu? ISO CD images are
available from http://cdimage.ubuntu.com/releases/ .

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

apport-collect -p linux 355275

Thanks in advance

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: jaunty
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 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.]

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.