[Chromebook Pixel] suspend/resume failure

Bug #1224689 reported by James M. Leddy
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Chromium
Unknown
Unknown
Linux
Unknown
Unknown
linux (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Closed the laptop lid and when I opened again it booted as normal.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-7-generic 3.11.0-7.13 [modified: boot/vmlinuz-3.11.0-7-generic]
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jack 1836 F.... pulseaudio
Date: Thu Sep 12 15:42:51 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=69785465-9ec4-47e1-bd86-43f2ac0b1357
InstallationDate: Installed on 2013-09-12 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130912)
InterpreterPath: /usr/bin/python3.3
MachineType: GOOGLE Link
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-7-generic root=UUID=d3937f64-31ba-43f3-9597-ee5f94b711c8 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-7-generic N/A
 linux-backports-modules-3.11.0-7-generic N/A
 linux-firmware 1.113
SourcePackage: linux
StagingDrivers: isl29018
Title: [GOOGLE Link] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 12/10/2012
dmi.bios.vendor: coreboot
dmi.chassis.type: 3
dmi.chassis.vendor: GOOGLE
dmi.modalias: dmi:bvncoreboot:bvr:bd12/10/2012:svnGOOGLE:pnLink:pvr1.0:cvnGOOGLE:ct3:cvr:
dmi.product.name: Link
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE

Revision history for this message
James M. Leddy (jm-leddy) 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 :

Did you have an actual suspend or resume failure? Or did you just get the apport dialog box?

Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
gordo lowrey (linuxinit) wrote :

i've been having this problem as well.

it's reproducible every single time, on the second resume.

first suspend/resume works fine.

second suspend works, resume fails.

Revision history for this message
gordo lowrey (linuxinit) wrote :
Revision history for this message
gordo lowrey (linuxinit) wrote :

fix: modprobe tpm_tis force=1 interrupts=0

Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Benjamin Gemmill (benjamin-gemmill) wrote :

The workaround no longer works since the tpm_tis module fails to load in kernels 3.13 and newer. This means that the only way to make 14.04 Trusty to work is to apply the workaround listed here and downgrade the kernel to 3.12.

Revision history for this message
Zooko Wilcox-O'Hearn (zooko-j) wrote :

Confirming that the workaround from https://bugs.launchpad.net/linux/+bug/1224689/comments/7 doesn't work for me with Ubuntu 14.04.1 with (my own locally-compiled) kernel 3.18.1

Revision history for this message
Zooko Wilcox-O'Hearn (zooko-j) wrote :

This stopped happening for me, and I happily ran with fully operational suspend/resume for a long time using the Linux-4.1.y series. Most recently Linux-4.1.17. However, a few days ago I upgraded from Linux-4.1.17 to the 4.4.y series — currently Linux-4.4.1 — and now the same symptoms happen again: after closing the lid, when I open the lid later I find it has powered down and it is now booting up.

Rebooting back into my Linux-4.1.17 kernel fixes it — as long as I've booted to that kernel then I can suspend-and-resume to my heart's content.

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.