[Lenovo ThinkPad X201] suspend/resume failure

Bug #1300436 reported by Václav Šmilauer
20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Failed to suspend (stuck in the middle of suspending, not reacting to anything).

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-20-generic 3.13.0-20.42
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: eudoxos 2823 F.... pulseaudio
                      lightdm 5862 F.... pulseaudio
Date: Mon Mar 31 17:51:22 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=5e6ca17d-f099-4f60-8759-5cce9419d11d
InstallationDate: Installed on 2010-10-25 (1253 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python3.4
MachineType: LENOVO 3680D79
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=5e6ca17d-f099-4f60-8759-5cce9419d11d ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-20-generic N/A
 linux-backports-modules-3.13.0-20-generic N/A
 linux-firmware 1.126
SourcePackage: linux
SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli'
Title: [LENOVO 3680D79] suspend/resume failure
UpgradeStatus: Upgraded to trusty on 2013-03-29 (367 days ago)
UserGroups:

WifiSyslog:

dmi.bios.date: 04/26/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET45WW (1.15 )
dmi.board.name: 3680D79
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: 6900025198
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6QET45WW(1.15):bd04/26/2010:svnLENOVO:pn3680D79:pvrThinkPadX201:rvnLENOVO:rn3680D79:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3680D79
dmi.product.version: ThinkPad X201
dmi.sys.vendor: LENOVO

Revision history for this message
Václav Šmilauer (eudoxos) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: [LENOVO 3680D79] suspend/resume failure

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Václav Šmilauer (eudoxos) wrote :

Tested with upstream, it works fine, added the tag as requested. (will double-check that the ubuntu kernel oopses consistently).

tags: added: kernel-fixed-upstream
penalvch (penalvch)
tags: added: bios-outdated-1.40
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
summary: - [LENOVO 3680D79] suspend/resume failure
+ [Lenovo ThinkPad X201] suspend/resume failure
Revision history for this message
Václav Šmilauer (eudoxos) wrote :

This was fixed in the distribution kernel already, apparently.

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
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.