[LENOVO 20344] suspend/resume failure

Bug #1443810 reported by honzasvasek
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

after update

ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-13-lowlatency 3.19.0-13.13
ProcVersionSignature: Ubuntu 3.19.0-13.13-lowlatency 3.19.3
Uname: Linux 3.19.0-13-lowlatency x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.17-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: honza 2048 F.... pulseaudio
 /dev/snd/controlC0: honza 2048 F.... pulseaudio
Date: Tue Apr 14 10:13:11 2015
DuplicateSignature: suspend/resume:LENOVO 20344:96CN22WW(V1.08)
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=cd99ed21-c6fd-4e24-ad4e-85899aecc59d
InstallationDate: Installed on 2015-03-29 (15 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150328)
InterpreterPath: /usr/bin/python3.4
MachineType: LENOVO 20344
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-lowlatency root=UUID=a453b7e7-5868-483d-b483-a9985e353342 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.19.0-13-lowlatency N/A
 linux-backports-modules-3.19.0-13-lowlatency N/A
 linux-firmware 1.143
SourcePackage: linux
Title: [LENOVO 20344] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 05/09/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 96CN22WW(V1.08)
dmi.board.asset.tag: 31900058Std
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 31900058Std
dmi.chassis.asset.tag: 31900058Std
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 2 13
dmi.modalias: dmi:bvnLENOVO:bvr96CN22WW(V1.08):bd05/09/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoYoga213:
dmi.product.name: 20344
dmi.product.version: Lenovo Yoga 2 13
dmi.sys.vendor: LENOVO

Revision history for this message
honzasvasek (honzasvasek) 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 :

honzasvasek, thank you for reporting this and helping make Ubuntu better. As per http://support.lenovo.com/us/en/products/laptops-and-netbooks/yoga-series/yoga-2-13-notebook-lenovo an update to your computer's buggy and outdated BIOS is available (1.15). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, 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

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

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed.

Thank you for your understanding.

tags: added: bios-outdated-1.15
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
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.