[LENOVO 7454CTO] suspend/resume failure

Bug #473876 reported by swmike
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: linux-image-2.6.31-14-generic

Lenovo X200 laptop, when resuming from suspend the "moon" is just flashing, nothing more happens.

This happens approx one in five times when doing resume. Karmic, fully updated release.

Linux swm-laptop 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux

$ cat /proc/version_signature
Ubuntu 2.6.31-14.48-generic

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: swmike 2434 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2620000 irq 17'
   Mixer name : 'Conexant CX20561 (Hermosa)'
   Components : 'HDA:14f15051,17aa20ff,00100000'
   Controls : 14
   Simple ctrls : 7
Date: Wed Nov 4 08:02:25 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=/dev/sda6
InterpreterPath: /usr/bin/python2.6
MachineType: LENOVO 7454CTO
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: root=UUID=2a9a0898-4ec3-4685-a9ac-9afae45ad815 ro
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
SourcePackage: linux
Tags: resume suspend
Title: [LENOVO 7454CTO] suspend/resume failure
Uname: Linux 2.6.31-14-generic i686
UserGroups:

WpaSupplicantLog:

dmi.bios.date: 05/18/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET53WW (3.03 )
dmi.board.name: 7454CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6DET53WW(3.03):bd05/18/2009:svnLENOVO:pn7454CTO:pvrThinkPadX200:rvnLENOVO:rn7454CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7454CTO
dmi.product.version: ThinkPad X200
dmi.sys.vendor: LENOVO

Revision history for this message
swmike (ubuntu-s-plass) wrote :
Revision history for this message
swmike (ubuntu-s-plass) wrote :

I would like to supplement this bug report with a correction of what I stated above. The screen does come on before the "moon" LED starts flashing, so basically the password prompt is seen on the screen before everything freezes.

Revision history for this message
swmike (ubuntu-s-plass) wrote :

When I was running 9.04, this wasn't a problem, so it's a regression (was running 9.04 for the whole release cycle).

tags: added: regression-release
Revision history for this message
swmike (ubuntu-s-plass) wrote :

I have tried the workaround found in http://launchpad.net/~x301/ (deactivating CPU cores during suspend/resume) which worked well for me in 8.10, this didn't help (actually gave me "flashing moon" during suspend phase and not only during resume).

I also tried stopping gdm so I had no X server running, and then running /etc/acpi/sleep.sh as root, this resulted in "flashing moon"-freeze during suspend (didn't suspend properly) within 2-3 attempts (replicated twice, first time it happened on second attempt, second time it happened on third attempt).

I so far have not seen the problem occuring when it's actually suspending (only when resuming) when I run with X server running and without the workaround. I'm going to try to use it normally (with X) with the workaround and report back later if it seems to change anything.

Revision history for this message
swmike (ubuntu-s-plass) wrote :

The problem with freeze when running sleep.sh occurs even when doing this from booting with "single" in the grub boot statement. When the freeze occurs, the backlight is still lit, screen looks exactly as it did before pressing "enter", apart from the blinking "moon".

tags: added: karmic
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Sumana Harihareswara (sumanah) wrote :

See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/467877 for another variable: check whether the problem occurs when you start on AC power, suspend, remove the power cord, and then try to resume on battery power.

Revision history for this message
Vigis (chvi77) wrote :

I can confirm this bug. Also, the freeze-up comes at a somewhat later stage. Sometimes, when I'm fast, it freezes after i have written half the password. I'm going to try the power-cord contra battery issue mentioned above as well.

I would very much like to see this fixed as soon as possible, as it is very very annoying to have to restart the laptop and lose all my progress. I would very much hate having to go back to M$ while i wait for this being fixed. :-/

If there is any extra info needed that i can provide, please ask. Eager to help with this one.

Revision history for this message
Søren Jacobsen (sej) wrote :

Vigis, have you tried the workaround described by Kenneth Hsu in:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/467877/comments/3

I haven't had the problem occur since I applied that about a month ago.

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

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.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.