[LENOVO ThinkPad X201] suspend/resume failure

Bug #1268113 reported by Richard Appleby
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Fresh install of 13.10 on new SSD. System previously running 12.10 (on a HDD) without problem.

Symptoms are that system is now extremely fragile when using suspend/resume to memory. Symptoms exhibit themselves in two main ways:
(a) System will often (~ more than 1 time in 3) fail to fully resume from suspend. When the error occurs, the graphical console appears to always hang at a black screen, at which point text consoles (CTRL-ALT-F1 etc) are no longer responsive either. Only option at this point is to force a power-off-restart. Often (about 50% of the time) this first restart also fails to boot cleanly, and fails to get as far as the greeter screen. However, CTRL-ALT-F1 etc are active at this point, and the system appears to be up, just NOT the graphical subsystem. A further reboot from one of the text consoles *usually* (but not always) brings up the system cleanly.

(b) System will sometimes apparently power off during suspend. Suspend appears to work correctly, but on returning to the system some time later, the system will be powered completely off.

In both cases, the use of a docking station appears to exacerbate the problem (so, suspending in the docking station, then removing the laptop from the dock, and then resuming *seems* to increase the likelihood of (a), and suspending off the docking station, plugging back into the dock *seems* to increase the likelihood of (b)).

I'm on the latest Lenovo BIOS, and all OS fixes/updates are applied.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-15-generic
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: richard 2575 F.... pulseaudio
CurrentDmesg:
 [ 14.401329] init: plymouth-stop pre-start process (1774) terminated with status 1
 [ 15.937910] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
 [ 15.937970] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Date: Sat Jan 11 10:01:33 2014
ExecutablePath: /usr/share/apport/apportcheckresume
ExecutableTimestamp: 1386693790
Failure: suspend/resume
HibernationDevice: RESUME=UUID=a1896162-7e68-42e3-9cec-5835e1aedd0f
InstallationDate: Installed on 2014-01-03 (8 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
InterpreterPath: /usr/bin/python3.3
MachineType: LENOVO 3626AZ8
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcCwd: /
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=/dev/mapper/Ubuntu-RootVol ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/1f199eb6-b2ad-4014-9f8d-41954bf1a417,lvm=Ubuntu 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.11.0-15-generic N/A
 linux-backports-modules-3.11.0-15-generic N/A
 linux-firmware 1.116
SourcePackage: linux
Title: [LENOVO 3626AZ8] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 10/11/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET70WW (1.40 )
dmi.board.name: 3626AZ8
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:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3626AZ8:pvrThinkPadX201:rvnLENOVO:rn3626AZ8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3626AZ8
dmi.product.version: ThinkPad X201
dmi.sys.vendor: LENOVO

Revision history for this message
Richard Appleby (disposable01) 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
tags: added: saucy
Revision history for this message
penalvch (penalvch) wrote :

SixedUp, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux REPLACE-WITH-BUG-NUMBER

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc7

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: latest-bios-1.40 needs-suspend-logs needs-upstream-testing
tags: added: regression-potential
summary: - [LENOVO 3626AZ8] suspend/resume failure
+ [LENOVO ThinkPad X201] suspend/resume failure
tags: added: needs-bisect regression-release
removed: regression-potential
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Richard Appleby (disposable01) wrote :

Additional information from ongoing testing: If I suspend/resume off the docking station, it *appears* to always work correctly. If I suspend/resume on the docking station, again, it *appears* to always work correctly. If I suspend on the docking station, remove my thinkpad from the docking station, and then resume, *BLAM* ... it *appears* to hang *every* time.

So, as my docking station contains a SATA DVD writer, I think my suspend/resume problem (part (a)) might be a manifestation of kernel bug 62801, see http://bit.ly/1ccXSYv. This is a deadlock problem introduced by a change in kernel 3.10. As far as I can tell (I'm no expert!), there is no official fix yet.

However, this still doesn't explain the failure to start the graphical subsystem on some subsequent reboots after this hang.

It also doesn't explain the other failure mode (part (b)) where I have been seeing the system apparently power-off during suspend. I now believe that this only happens *sometimes* when I suspend off the docking station, dock the thinkpad while suspended, and then leave the thinkpad suspended on the docking station for some time (typically overnight).

Re request to test with the latest development release, yes, now I have a guaranteed way to recreate, I can do that for you. I will test that and report the results (probably tomorrow) before (I suspect) moving onto testing the upstream kernel.

Revision history for this message
Richard Appleby (disposable01) wrote :

I am unable to reproduce the problem with yesterdays (13th January) development release of 14.04. The kernel in that release reported itself as 3.13.0-2.

Revision history for this message
penalvch (penalvch) wrote :

SixedUp, would you need a backport to a release prior to 14.04, or may this be closed as Status Invalid?

Revision history for this message
Richard Appleby (disposable01) wrote :

I discussed this with our internal support team, and as thinkpads with docking stations are a common configuration for us, we suspect we could have a reasonable number of people affected by this (high tens) so we'd appreciate a backport for Ubuntu 13.10 if possible.

Revision history for this message
penalvch (penalvch) wrote :

SixedUp, Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268113/comments/5 the bug has been fixed in the latest development version of Ubuntu - Trusty Tahr.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

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