Bug 1073514 - recent kernel upgrades seem to break resume from hibernation during upgrade
Summary: recent kernel upgrades seem to break resume from hibernation during upgrade
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-06 15:03 UTC by long
Modified: 2015-02-17 20:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 20:00:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description long 2014-03-06 15:03:59 UTC
Description of problem:
This seems to have happened the last few kernel upgrades.  I'll be running the "old" kernel and Fedora will automatically update it by installing the "new" kernel and making it the default.  That night my system will hibernate while running the "old" kernel.  The next day when I power up the system starts the "new" kernel which does not seem capable of resuming the "old" hibernation image.  Instead I get a black screen, no keyboard response, no network.  I don't believe this used to happen when kernels were upgraded.  This resume problem also doesn't happen if I power up using the same kernel that was used to hibernate.

Version-Release number of selected component (if applicable):
kernel-3.13.5-101.fc19.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Run system with kernel-3.12.11-201.fc19.x86_64
2. Have default kernel set to kernel-3.13.5-101.fc19.x86_64
3. Allow system to hibernate
4. Power up
3.

Actual results:
Black screen, no keyboard, no network

Expected results:
System resumes and operates normally

Additional info:
No log info seems to be produced on resume so I don't have anything to give you there.  I do have whatever is logged during hibernate if you want that.

Comment 1 Justin M. Forbes 2014-03-10 14:49:15 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.13.5-100.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 2 long 2014-03-12 21:37:25 UTC
Bug I reported happened upgrading to kernel-3.13.5-101.fc19.x86_64 so it appears to still be a problem.

Comment 3 Justin M. Forbes 2014-05-21 19:31:32 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.14.4-100.fc19.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.

Comment 4 Szőke Károly 2014-05-22 11:16:45 UTC
Me too, from kernel v. 3.14 my MSI VR610x laptop is not waking up from suspended state, nor hibernated state. It's worked until kernel 3.13. When I try to hibernate my PC, it's go ahead until  the last step: power off the machine, so it doesn't power off. I must do a hard power off. (Sorry for my English)

Comment 5 long 2014-05-23 15:21:13 UTC
Yes, same thing seemed to happen during the upgrade from x86_64-linux-3.13.11-100.fc19.x86_64 to 3.14.4-100.fc19.x86_64.  It upgraded the kernel, then hibernated, then failed to resume.

Comment 6 long 2014-07-25 19:41:27 UTC
Still happening during kernel-3.14.8-100.fc19.x86_64 -> kernel-3.14.13-100.fc19.x86_64 transition

Comment 7 long 2014-08-20 14:52:45 UTC
Happened again during kernel-3.14.15-100.fc19.x86_64 -> kernel-3.14.17-100.fc19.x86_64

Comment 8 Szőke Károly 2014-09-13 06:23:56 UTC
It's work again, the suspend and hibernate state. My actual kernel is 3.15.10.

Comment 9 Fedora End Of Life 2015-01-09 21:12:01 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 10 Fedora End Of Life 2015-02-17 20:00:18 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.