[LENOVO S10-3] suspend/resume failure [non-free: wl]

Bug #1426137 reported by Eric Chaskes
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Computer would not resume after using suspend fn key. Computer would sometimes think wifi was blocked by hardware switch after this. Had to pull cmos battery to restore. This seems to be a regression to behavior that went away with the 3.10 kernel.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.18.0-13-generic 3.18.0-13.14 [modified: boot/vmlinuz-3.18.0-13-generic]
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
NonfreeKernelModules: wl
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: eric 2061 F.... pulseaudio
Date: Thu Feb 26 16:52:07 2015
DuplicateSignature: suspend/resume:LENOVO S10-3:2ACN31WW
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=c3b175e1-a54e-4278-b11a-2025838bebfd
InstallationDate: Installed on 2015-02-26 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150223)
InterpreterPath: /usr/bin/python3.4
MachineType: LENOVO S10-3
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-13-generic root=UUID=4b7fe0de-12fa-4fb1-9b52-6aaafe5ab9e3 ro quiet splash
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.18.0-13-generic N/A
 linux-backports-modules-3.18.0-13-generic N/A
 linux-firmware 1.141
SourcePackage: linux
Title: [LENOVO S10-3] suspend/resume failure [non-free: wl]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 06/29/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 2ACN31WW
dmi.board.name: Mariana3A
dmi.board.vendor: Lenovo
dmi.board.version: Rev 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Lenovo
dmi.chassis.version: Rev 1.0
dmi.modalias: dmi:bvnLENOVO:bvr2ACN31WW:bd06/29/2010:svnLENOVO:pnS10-3:pvrLenovo:rvnLenovo:rnMariana3A:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
dmi.product.name: S10-3
dmi.product.version: Lenovo
dmi.sys.vendor: LENOVO

Revision history for this message
Eric Chaskes (echaskes) 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
Changed in linux (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 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/v4.0-rc1-vivid/

Changed in linux (Ubuntu):
importance: Critical → Medium
status: Confirmed → Incomplete
tags: removed: need-duplicate-check
Revision history for this message
Eric Chaskes (echaskes) wrote :

Additional information:

1. Before the 3.10.x line, the computer required hpet=disable highres=off nohz=off in order to resume.

2. With the 3.10.x kernel, suspend/resume worked out of the box.

3. Suspend/resume still works with Debian Sid (3.16.x) and Fedora 21 (3.17.x).

4. The grub command line above no longer works.

5. Using kernel v4.0-rc3 did not solve the problem.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
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.