[LENOVO ThinkPad X220] suspend/resume failure

[rolfc]

It seem to me that this is a strange problem. After suspend, there is no resume. The strange thing is that after installing a new kernelpackage it work as it should for 2 or 3 times, the it start failing again.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-9-generic 3.11.0-9.16
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rolfc 2312 F.... pulseaudio
 /dev/snd/seq: timidity 1375 F.... timidity
Date: Tue Oct 1 20:24:13 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=26a91e75-e73a-4504-831f-5088ed794e48
InstallationDate: Installed on 2012-05-22 (497 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/python3.3
MachineType: LENOVO 42914CG
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=0e70b3de-2758-4c05-aee2-4955f07e0e7c ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-9-generic N/A
 linux-backports-modules-3.11.0-9-generic N/A
 linux-firmware 1.115
SourcePackage: linux
Title: [LENOVO 42914CG] suspend/resume failure
UpgradeStatus: Upgraded to saucy on 2013-09-09 (21 days ago)
UserGroups:

dmi.bios.date: 02/14/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET58WW (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 42914CG
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:bvr8DET58WW(1.28):bd02/14/2012:svnLENOVO:pn42914CG:pvrThinkPadX220:rvnLENOVO:rn42914CG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 42914CG
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 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.12-rc3-saucy/

[Christopher M. Penalver (penalvch)]

rolfc, as per http://download.lenovo.com/express/ddfm.html an update is available for your BIOS (1.39). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

[rolfc (rolfcronberg)]

Hi, I have updated the bios and the effekt is like changeing kernel. Everything seem to work a few times, maybe five times then the suspend doesn't work any more. I can here the fan working for som time, then it stops and the lights go out.

The output of the command is
rolfc@thinker:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
8DET69WW (1.39 )
07/18/2013

[Christopher M. Penalver (penalvch)]

rolfc, did this problem not occur in a release prior to Saucy?

[rolfc (rolfcronberg)]

Hi,
No I did not have this problem before updating. It was working very well. For me it is not a big problem, I am waiting for a new laptop to make fresh install.

[Christopher M. Penalver (penalvch)]

rolfc, the next step is to bisect from the previously working release to Saucy, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Mark Stosberg (markstos)]

I'm also experiencing intermittent failures after suspend/resume with X220 i7. I experienced the suspend problems first with 12.04, and recently tried the 14.04 Live CD, and experienced them there as well.

I appear to have better luck with a HDD than an SDD in it, but that may be coincidental.

[Mark Stosberg (markstos)]

This Ubuntu 12.04 X220 user suggested in a fix that involves ACPI configuration rather than a kernel change that you might try:

http://fstyle.de/hp_fstyle/wordpress/2012/08/10/ubuntu-12-04-acpi/

[Mark Stosberg (markstos)]

Here's my latest test result, using:
   - X220 i7
   - Samsung 840 Pro SSD
   - BIOS 1.39
  - Ubuntu 12.04.3
  - Kernel 3.8.0-33

Using "sudo pm-suspend", the first cycle completes normally.
On the second cycle, I see an "Unable to dock!" message as it's suspending. It resumes to show a black screen with the "Unable to dock" message on it.

I use can "Alt-F1" to see a screen with a login prompt, but I can't login.

After a hard-power-off and restarting, I check /var/log/pm-suspend.log and find that the last suspend is logged, but there is no detail at all about resume.

The only indication of a problem I see in /var/log/pm-suspend.log is
"Having NetworkManager put all interfaces to sleep...Failed",
but that happens on the first, successful suspend cycle as well.

From having looked at other variations of this issue as I've tried to work through it, I think what's happening is that the OS is running after resume, but I/O to the hard drive has failed. That explains why the "resume" portion of the logging is completely missing, and why I can get as far as the login screen, but login (presumably it's started to load something from the drive at that point, and is failing).

In the BIOS, I tried changing the SATA connection from "AHCI" to Legacy, but it doesn't help. (Above it's in Legacy mode still, I think). I also tried an Intel 520 Cherryville SSD with similar results.

Using a mechanical Hitachi drive, I was able to 10 successful suspend/resume cycles in a row, but I want this to work with one of these two SSDs.

As noted above, I also tried 14.04 on this laptop, and had problems with suspend as well. My last notes on that contain a different failure mode, though:

" Suspended via Fn-F4, Screen came back, but was very dim, and mouse was frozen."

I'm willing to try either 12.04 or 14.04, if you have suggestions of things to try.

12.04 is currently on the SSD, while 14.04 is on a Live USB drive.

[Christopher M. Penalver (penalvch)]

Mark Stosberg, so your hardware may be tracked, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]