[LENOVO INVALID] suspend/resume failure

[Isriya Paireepairit]

Linux gnosis 2.6.28-11-generic #36-Ubuntu SMP Fri Mar 20 19:40:40 UTC 2009 i686 GNU/Linux

Ubuntu 2.6.28-11.36-generic

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 INVALID
Package: linux-image-2.6.28-11-generic 2.6.28-11.36
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=f68b6a40-677b-4902-b548-583238328c0a ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.36-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: [LENOVO INVALID] suspend/resume failure
UserGroups:

[Leann Ogasawara (leannogasawara)]

*This is an automated response*

Could you please take a look the triage and debugging guide at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume, specifically the Information Gathering section. Please provide any answers to the additional questions outlined there. Thanks.

[Bernie Bernstein (bernie9998)]

Let me provide answers as I can observe from my laptop-- Lenovo Y530 laptop, model 405166U:

Did the machine break while going to sleep or waking up?
It appears to be breaking while going into sleep. The screen blanks out and the CAPS/NUM/SCROLL lock leds all blink once. After the LED's blink, nothing else happens. No other leds change to indicate a low power state and there is no response from CAPS lock or the wifi kill switch. Despite the screen blanking, the laptop is clearly not in a sleep state-- the cpu fan remains on and heat is still dissipating from the laptop.

Is it reproducible?
With exception of two attempts, this behavior always occurs.

With the first of the other two exceptions, the laptop woke up immediately during the suspend process. In the second exception, the laptop went into the usual state, however, still responded to CAPS lock with the led, and woke up shortly thereafter.

I managed to capture the dmesg portion of the suspend process during this second exception and will post it as an attachment.

Did it work before?
This is a new laptop for me and has never worked before. I have only tried Ubuntu version 8.10 and the latest alpha of 9.04. I have not tried any other versions.

Do you end up with flashing caps-lock or similar?
Other than the single flash of the LEDs, indicative of a power state change, no consistent blinking of any led's had occurred, leading to believe that this was not a kernel panic.

[Bernie Bernstein (bernie9998)]

I had mentioned earlier that the screen blanks when going into sleep-- this is not actually the case. Usually, The screen simply goes black with a blinking cursor at the top left of the screen. Occasionally, however, the laptop will attempt to suspend but immediately wakeup instead.

[Leann Ogasawara (leannogasawara)]

Care to test and confirm if this issue remains with the latest Karmic 9.10 Alpha development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . You should be able to test suspend using a LiveCD. Please let us know your results. Thanks.

[Bernie Bernstein (bernie9998)]

This issue is still not resolved in the latest karmic build. I tried suspending while booted into the livecd in the karmic alpha 3 build.

When trying to suspend, the keyboard led's (caps lock, scroll lock and num lock) all blink once in unison and then the laptop immediately locks up. The machine becomes completely unresponsive and has to be powered down and brought back up again.

This time however, the screen does not blank as before-- when suspending from the gui, the desktop remains on the screen completely frozen.

Attempting to suspend from the command line was also attempted with the command "echo mem > /sys/power/state" being run as root. The same results occured-- the computer became completely unresponsive. No screen blanking occurs-- the screen remains frozen, including the cursor, which no longer blinks.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, 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.]

[Bernie Bernstein (bernie9998)]

This is still happening for me on my laptop with 9.10. I have not yet tested with the oncoming 10.04 though.

[Bernie Bernstein (bernie9998)]

This issue is still occurring for me with the latest ubuntu release, 10.04.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.