[LENOVO 80K6] hibernate/resume failure

Bug #1560025 reported by MK
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

closing my laptop or starting pm-himernate doesn't stop computer work. The computer is working but the monitor is "black" and I can't do anything but power off.

ProblemType: KernelOops
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-14-generic 4.4.0-14.30
ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly.
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mkrol 1655 F.... pulseaudio
 /dev/snd/controlC1: mkrol 1655 F.... pulseaudio
Date: Mon Mar 21 14:00:30 2016
DuplicateSignature: hibernate/resume:LENOVO 80K6:C2CN17WW(V1.03)
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
HibernationDevice: RESUME=UUID=7714fe69-9bc8-4b11-8d65-7f96f5122d6d
InstallationDate: Installed on 2016-02-10 (40 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209)
InterpreterPath: /usr/bin/python3.5
MachineType: LENOVO 80K6
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-14-generic.efi.signed root=/dev/mapper/ubuntu--vg-root 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-4.4.0-14-generic N/A
 linux-backports-modules-4.4.0-14-generic N/A
 linux-firmware 1.156
SourcePackage: linux
Title: [LENOVO 80K6] hibernate/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 03/19/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: C2CN17WW(V1.03)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo Z51-70
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Z51-70
dmi.modalias: dmi:bvnLENOVO:bvrC2CN17WW(V1.03):bd03/19/2015:svnLENOVO:pn80K6:pvrLenovoZ51-70:rvnLENOVO:rnLenovoZ51-70:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoZ51-70:
dmi.product.name: 80K6
dmi.product.version: Lenovo Z51-70
dmi.sys.vendor: LENOVO

Revision history for this message
MK (niechzyje) 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
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

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

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.5-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
MK (niechzyje) wrote :

I can't say it began after update/upgrade. It is possible. It started about 2-3 weeks ago. Before everything worked. I will try to use the latest kernel and I'll let you know. Thanks for response!

Revision history for this message
MK (niechzyje) wrote :

The mainline kernel does not fix this bug.

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