Hibernate fails if resume is done after X hours (X ~ 3+ hours)

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

Bug Description

I have a strange issue but I'm not the only one (http://ubuntuforums.org/showthread.php?t=2280045).

My hardware is Lenovo t450s with intel Hd 5500. Suspend works fine (Although I haven't tested a long sleep yet). Intel rapidstart is disabled in BIOS. Hibernate saves to disk and resumes fine if I do the wakeup within a few hours. Any long-term hibernates (12 hours) don't resume. The splash screen shows up and then a blank screen and unresponsive keyboard. I don't have a capslock key, so don't know if that is flashing.

I have been on multiple kernels 3.16,3.18,3.19 and 4.0 now. All of them have shown this problem. If there are any specific debugs that I could gather to help narrow down the issue, I would appreciate the guidance. Thanks!
---
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME-Classic:GNOME
DistroRelease: Ubuntu 15.04
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-04-15 (46 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
Package: linux (not installed)
Tags: vivid
Uname: Linux 4.0.0-040000-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to vivid on 2015-04-29 (33 days ago)
UserGroups: adm cdrom dip lpadmin netdev plugdev roccat sambashare sudo tomcat6
_MarkForUpload: True

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1460507

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
oldtuxer (oldtuxer2k15) wrote : JournalErrors.txt

apport information

tags: added: apport-collected vivid
description: updated
Revision history for this message
oldtuxer (oldtuxer2k15) wrote : ProcEnviron.txt

apport information

oldtuxer (oldtuxer2k15)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
oldtuxer (oldtuxer2k15) wrote :

/var/crash/

Changed in linux (Ubuntu):
importance: Undecided → High
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.1 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.1-rc6-unstable/

Changed in linux (Ubuntu):
importance: High → Medium
Revision history for this message
oldtuxer (oldtuxer2k15) wrote :

With 4.1RC6, I have tried to replicate it twice and it worked fine every time after an hibernate of 12+ hours. Would it be worth getting debugs with the earlier kernel to triage the issue.

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.