[LENOVO 20266] hibernate/resume failure

Bug #1294087 reported by Jean Martina
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Lenovo Yoga 2 Pro does not come back from sleep.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-17-generic 3.13.0-17.37
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic x86_64
Annotation: This occured during a previous hibernate and prevented it from resuming properly.
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jeanmartina 2039 F.... pulseaudio
 /dev/snd/controlC0: jeanmartina 2039 F.... pulseaudio
Date: Tue Mar 18 08:59:28 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
InstallationDate: Installed on 2014-03-12 (5 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140309)
InterpreterPath: /usr/bin/python3.4
MachineType: LENOVO 20266
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-17-generic.efi.signed root=UUID=edbaa033-c440-4e73-8460-2239177e36b4 ro resume=/dev/disk/by-uuid/edbaa033-c440-4e73-8460-2239177e36b4 quiet acpi_backlight=vendor 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.13.0-17-generic N/A
 linux-backports-modules-3.13.0-17-generic N/A
 linux-firmware 1.126
SourcePackage: linux
Title: [LENOVO 20266] hibernate/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 10/31/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 76CN31WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Yoga2
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 2 Pro
dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
dmi.product.name: 20266
dmi.product.version: Lenovo Yoga 2 Pro
dmi.sys.vendor: LENOVO

Revision history for this message
Jean Martina (jean-martina) 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 :

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

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Jean Martina (jean-martina) wrote :

bug still exist upstream

tags: added: kernel-bug-exists-upstream
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Yuv (yuv) wrote :

Has an upstream bug report been filed?

The exact same issue affects a SONY Vaio Pro 13 (Haswell ULV CPU).

Which one is the latest trusty mainline kernel? sorted by last modified date, it seems to be [0] from less than ten days ago, but sorted by version number it seems to be [1] from four months ago.

Also quite confusing is that by both version number and date, there are far newer utopic kernels. I can't test utopic on this laptop at this point. I would expect that those mainline kernels builds are automated, in which case is there a reason for them not being made available for the latest LTS Ubuntu release?

Thanks for helping me help you make Ubuntu better.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.6-trusty/
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc2-trusty/

Revision history for this message
madbiologist (me-again) wrote :

Yuv - we don't want you to test the latest Trusty mainline kernel. I'm not sure there is even such a thing. We want you to test the latest mainline kernel, without any trusty/utopic suffix (currently 4.8.1). This is because the most useful action is to test the most recent kernel version. However, you have different hardware than the original reporter, so it is unlikely that you are experiencing the exact same issue. I would recommend that you run ubuntu-bug to file a new bug report.

Revision history for this message
madbiologist (me-again) wrote :

Jean Martina - can you please update to the latest BIOS available from http://support.lenovo.com/au/en/products/Laptops-and-netbooks/Yoga-Series/Yoga-2-Pro-Lenovo?tabName=Downloads&linkTrack=Mast:SubNav:Support:Drivers%20and%20Software|Drivers%20and%20Software&beta=false and let us know if the issue is fixed?

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Jean Martina (jean-martina) wrote : Re: [Bug 1294087] Re: [LENOVO 20266] hibernate/resume failure

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I updated kernel to upstream 4.8.1-040801-generic and seems more
stable now. As I don't have windows any more, updating the bios will
be painful.

I have been running this kernel for a week now a no more hangs such
the ones I reported.

Regards,

Jean

On 09-10-2016 03:35, madbiologist wrote:
> Jean Martina - can you please update to the latest BIOS available
> from
> http://support.lenovo.com/au/en/products/Laptops-and-netbooks/Yoga-
>
>
Series/Yoga-2-Pro-
> Lenovo?tabName=Downloads&linkTrack=Mast:SubNav:Support:Drivers%20and%2
0Software|Drivers%20and%20Software&beta=false
>
>
and let us know if the issue is fixed?
>
> ** Changed in: linux (Ubuntu) Status: Triaged => Incomplete
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJYDVTsAAoJEFT5UIZQZaMYcUIQAI9NCZlCK5ZeRgdjg4ZF8AXT
qPMnhyUCSYE3/aKBHUbmj4xW2+bO28GNeayckPFLS2fz8IQ2MtEJpYMAD2TH4iKK
LYevPMFa6V5mTp9cwRnksd5vRJpzoKEvcMUHENCMrwU4XLHaTz2GnUZQjUd1QJcY
uwlE+faMiVVQTEvwWBthcQsf1R4IHq7mOEDqFsb0H1eLuh9XcvsBqPV5Dgb8HgBH
DCxFKuw94g7UfKurKgUkkoXgLAcP79gHs0sIlT79sD13I8VZmSadfVz0ZzJ6Aoev
DSQzDnjb5qY20iVVIGSVMSU+A4FiYDRQnocHcNzQ1MFUtSEIEN4hT1mm5rg101gs
onfL7zM3X8xUhGvAPsn5VGh6ZeEXZwnmZTjI0yTl+NdGCpUIjI+guNTMe5dqWUWO
+Bn5Cn91KGXyqlNjiFeLnQa+4hW8d/C3KUz2/e/RDy+qY6fE9E9Oi4oj3y/02fzr
oeVNyttmxKRWJ+pOx89yALKJ7kSGcXxvJ3T4t6BBpjuXA9UebbkcizRroQDX/z9e
tY1VMKVAX9s4UwHvUfjMPHytr0fY7uEzHUusGPt48Vk5v/eYEVSxcmLf0IYC90FL
3oW9YcHTrZduoHHxffG0cxJ2wcSsaUbBx8yz6ZERgOEWXENbOsB0FfAEAh/KwOOe
vBHAM4BxCAB+cjAl+ouT
=Cuk8
-----END PGP SIGNATURE-----

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
madbiologist (me-again)
Changed in linux (Ubuntu):
status: Expired → Fix Released
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.