Lenovo INVALID suspend/resume failure

[George Hein]

Problem with Debian, Ubu-9.04 & 9.10, easypeasy, SUSE.

Suspend (according to /var/log) completes but either simply locks up or (previously) has a screen blinking erratically, necessitating a power-off.

Hibernation works well. S2BOTH locks up as suspend but after power off it will restore upon booting.

I think I have opened problem on this in the past.

IdeaPad Y530 (4051) - GMA (February 2009)
CCFL Mini PCIe
Widescreen or Cam-Integrated SATA SATA 802.11 Top Blue-ENERGY Vista Avail

Type-model Processor GHz Memory display LED era graphics disk optical wireless color tooth STAR 4.0 preload date
===========================================================================================
4051-68U T3400 2.16 2GB 15.4" WXGA LED Cam GMA 250GB DVD±RW Intel 5100 Black Prem 32 Feb 09
===

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gjh 2515 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd4200000 irq 22'
   Mixer name : 'Intel G45 DEVCTG'
   Components : 'HDA:10ec0888,17aa3d78,00100202 HDA:10573055,17aa3d7d,00100700 HDA:80862802,80860101,00100000'
   Controls : 42
   Simple ctrls : 24
Date: Tue Sep 22 01:43:50 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=c463eacf-3771-4eee-a45a-9ac21fde058d
InterpreterPath: /usr/bin/python2.6
MachineType: Lenovo INVALID
Package: linux-image-2.6.31-10-generic 2.6.31-10.34
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=9a54e584-6da8-48b6-ae28-4a0609b68cf9 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-10-generic N/A
 linux-firmware 1.19
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: resume suspend
Title: [Lenovo INVALID] suspend/resume failure
Uname: Linux 2.6.31-10-generic x86_64
UserGroups:

dmi.bios.date: 02/25/2009
dmi.bios.vendor: Lenovo
dmi.bios.version: 10CN41WW
dmi.board.asset.tag: Lenovo Assert TAG
dmi.board.name: INVALID
dmi.board.vendor: Lenovo
dmi.board.version: 10CN41WW
dmi.chassis.asset.tag: Lenovo Assert TAG
dmi.chassis.type: 10
dmi.chassis.vendor: Lenovo
dmi.chassis.version: 10CN41WW
dmi.modalias: dmi:bvnLenovo:bvr10CN41WW:bd02/25/2009:svnLenovo:pnINVALID:pvrLenovoIdeaPadY530:rvnLenovo:rnINVALID:rvr10CN41WW:cvnLenovo:ct10:cvr10CN41WW:
dmi.product.name: INVALID
dmi.product.version: Lenovo IdeaPad Y530
dmi.sys.vendor: Lenovo
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gjh 1334 F.... pulseaudio
 /dev/snd/pcmC0D0p: gjh 1334 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd4200000 irq 22'
   Mixer name : 'Intel G45 DEVCTG'
   Components : 'HDA:10ec0888,17aa3d78,00100202 HDA:10573055,17aa3d7d,00100700 HDA:80862802,80860101,00100000'
   Controls : 27
   Simple ctrls : 15
DistroRelease: Ubuntu 10.04
Frequency: Once a day.
HibernationDevice: RESUME=UUID=69727f18-9e3c-4449-b439-ab508c373f57
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100122)
IwConfig: Error: [Errno 2] No such file or directory
MachineType: Lenovo INVALID
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=(hd0,6)/vmlinuz root=/dev/sda6 ro splash resume=/dev/sda5
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Regression: No
RelatedPackageVersions: linux-firmware 1.33
Reproducible: No
RfKill: Error: [Errno 2] No such file or directory
Tags: lucid suspend resume needs-upstream-testing
UdevDb: Error: [Errno 2] No such file or directory
Uname: Linux 2.6.32-19-generic x86_64
UserGroups: adm admin cdrom dialout grp lp lpadmin plugdev sambashare
WifiSyslog: Apr 3 06:26:29 z8 kernel: [ 3149.926008] ZZoIN= OUT=wlan0 SRC=192.168.1.8 DST=91.189.89.224 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=55070 DF PROTO=TCP SPT=45161 DPT=443 WINDOW=137 RES=0x00 ACK RST URGP=0
dmi.bios.date: 02/25/2009
dmi.bios.vendor: Lenovo
dmi.bios.version: 10CN41WW
dmi.board.asset.tag: Lenovo Assert TAG
dmi.board.name: INVALID
dmi.board.vendor: Lenovo
dmi.board.version: 10CN41WW
dmi.chassis.asset.tag: Lenovo Assert TAG
dmi.chassis.type: 10
dmi.chassis.vendor: Lenovo
dmi.chassis.version: 10CN41WW
dmi.modalias: dmi:bvnLenovo:bvr10CN41WW:bd02/25/2009:svnLenovo:pnINVALID:pvrLenovoIdeaPadY530:rvnLenovo:rnINVALID:rvr10CN41WW:cvnLenovo:ct10:cvr10CN41WW:
dmi.product.name: INVALID
dmi.product.version: Lenovo IdeaPad Y530
dmi.sys.vendor: Lenovo

[Jeremy Foshee (jeremyfoshee)]

Hi George,

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

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

apport-collect -p linux 434874

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

apport information

[George Hein (gjhein)]

Currently with latest version of LUCID: suspend appears to work normal up to shutoff, leds and hard-drive remain running, power off required to proceed. I have had similar problem with other PC's in past.

[George Hein (gjhein)]

With karmic>lucid32 upgrade same problem with suspend, fails to closeup requires power-off; hibernate works OK

With fresh install of lucid64 ditto with suspend; hibernate does not shutdown, requires power-off and boots up restoring SLOWLY
Also, sys:pref:power-mgr, although set to "ASK" at power-sw, simply shuts down. This has happened occasionally with beta testing of lucid64 but not with lucid32 testing.

Using Lenovo-Ideapad-Y530 which is not fully recognized by Linux.

I have also reported this bug in Re: Fw: [Bug 335570] Re: [LENOVO 7454CTO] suspend/resume failure

[singer (andrppv)]

Yes, the bug still remains. My Lenovo Y510 is mostly recognized by Linux/

[xgong (xgong)]

The latest kernel update still cannot fix this problem !

[George Hein (gjhein)]

same problem under Maverick64 as well as Lucid32+64: suspend fails to complete, requiring a power-off.

Note, for hibernation I added following to execute at startup, without this I need to power-off:

  echo shutdown > /sys/power/disk

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