[LENOVO 20344] suspend/resume failure

Bug #1419518 reported by Mathieu Marquer
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Screen stays black when trying to resume, I have to power off the computer and start it again.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.18.0-12-generic 3.18.0-12.13
ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
Uname: Linux 3.18.0-12-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.16-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lightdm 1507 F.... pulseaudio
                      mathieu 2358 F.... pulseaudio
 /dev/snd/controlC1: lightdm 1507 F.... pulseaudio
                      mathieu 2358 F.... pulseaudio
Date: Sun Feb 8 21:03:40 2015
DuplicateSignature: suspend/resume:LENOVO 20344:96CN29WW(V1.15)
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
InstallationDate: Installed on 2014-12-09 (60 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
InterpreterPath: /usr/bin/python3.4
MachineType: LENOVO 20344
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-12-generic.efi.signed root=UUID=e5668ab6-1bae-42da-9c57-a68bef726b9f 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.18.0-12-generic N/A
 linux-backports-modules-3.18.0-12-generic N/A
 linux-firmware 1.141
SourcePackage: linux
Title: [LENOVO 20344] suspend/resume failure
UpgradeStatus: Upgraded to vivid on 2015-01-04 (34 days ago)
UserGroups:

dmi.bios.date: 10/16/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 96CN29WW(V1.15)
dmi.board.asset.tag: 31900058WIN
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 31900058WIN
dmi.chassis.asset.tag: 31900058WIN
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 2 13
dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
dmi.product.name: 20344
dmi.product.version: Lenovo Yoga 2 13
dmi.sys.vendor: LENOVO

Revision history for this message
Mathieu Marquer (slasher-fun) wrote :
tags: removed: need-duplicate-check
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
penalvch (penalvch) wrote :

Mathieu Marquer, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to 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 by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

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.15
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Mathieu Marquer (slasher-fun) wrote :

Same issue with kernel 3.19 (latest available at the time).

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-fixed-upstream kernel-fixed-upstream-3.19
tags: added: kernel-exists-upstream kernel-exists-upstream-3.19
removed: kernel-fixed-upstream kernel-fixed-upstream-3.19
tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.19
removed: kernel-exists-upstream kernel-exists-upstream-3.19
Revision history for this message
penalvch (penalvch) wrote :

Mathieu Marquer, did this problem not occur in a release prior to 15.04?

Also, could you please test for this with the latest mainline kernel 4.0-rc1 and advise to the results?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Mathieu Marquer (slasher-fun) wrote :

Tried to reproduce with both current vivid kernel and 4.0-rc2, so far this bug didn't reappear, I'll update if it does.

I never tried Ubuntu 14.10 or earlier on that computer.

Revision history for this message
penalvch (penalvch) wrote :

Mathieu Marquer, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1419518/comments/6 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

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