[TOSHIBA Satellite Pro M40] suspend/resume failure

Bug #349397 reported by Peter Cooper
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

The system came backup such that I could see a mouse pointer, but on a black screen, no other response. Also the application apport crashed three times during the attempt to process this error. Not sure if this is connected or not.

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
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: TOSHIBA Satellite Pro M40
Package: linux-image-2.6.28-11-generic 2.6.28-11.37
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=82d0b0c2-b7e1-4840-a61e-6b11a1c6dccd ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.37-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: [TOSHIBA Satellite Pro M40] suspend/resume failure
UserGroups:

Revision history for this message
Peter Cooper (pcooper-gaitor) wrote :
Revision history for this message
Andy Whitcroft (apw) wrote :

Could you please follow the triage and debugging guide (https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume) and report back here.

Changed in linux:
status: New → Incomplete
Revision history for this message
Peter Cooper (pcooper-gaitor) wrote :

This error occurs during a resume. Having shut the lid on the laptop for suspend, I then attempt a resume. There is really no response from the machine, the power button which is slowly flashing orange turns to green but no other response, the machine fan does start but then stops. At this point the machine has a black screen.

An interesting point is that I am unable to turn the machine off. Holding the power button results in a momentary power-off followed by an immediate restart (power-up) into the fault mode. There appears to be no 'boot' process here, no loss of power to the machine, its all immediate. The only way to recover the machine is to remove the battery.

This is a repeatable event.

This is an almost Vanilla Jaunty install, I use this laptop as a test bed for development testing. However note that I believe this bug to have existed in Intrepid as well. I have looked in the BIOS in an attempt to prevent the 'nonpower-off' problem but there appears to be no options that may be relevant.

Revision history for this message
xteejx (xteejx) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu version (10.04). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

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
Revision history for this message
fig_wright (fig-wright) wrote :

I also have this problem.

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.