Bug 1100978 - Fail to shut power off at end of hibernation process [NEEDINFO]
Summary: Fail to shut power off at end of hibernation process
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-24 22:32 UTC by Morgan Leijström
Modified: 2014-12-10 15:45 UTC (History)
29 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-12-10 15:02:07 UTC
Type: Bug
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)

Description Morgan Leijström 2014-05-24 22:32:19 UTC
Description of problem:
At end of hibernation it hangs instead of powering off;
 user loose work -> severe bug.


Version-Release number of selected component: kernel 3.14.4-200.fc20.x86_64 ;
Up to date fc20 64 bit, with nouveau graphics and kdump, KDE.


How reproducible: Always

Steps to Reproduce:  from KDE menu: select hibernate

Actual results: switch to text screen, i see it saves image, screen get black (and here it should power off i presume) but computer give a short beep like at power on and the suspend lamp start blinking - like i believe it it do when kernel panics.

I need to hold down power switch 4 seconds to power off.
When I power on again it boots normally, not resuming.
Sa i guess it somehow tried to immediately reboot instead of powering off, and failed.
(If it had failed to save the session it should have stopped there with a written error message i presume?)


Expected results:
Power off at step noted above, and on manual power on resume (including user somewhere having to enter LUKS key)


Additional info:
Power off and reboot commands always works as they should.
Machine is often but not always having problem to resume from suspend, Bug 1096989  
Machine: Thinkpad R61; Intel Centrino Duo, 2GB RAM, nvidia quadro NVS140 GPU.
SSD disk partitioned as
 500 MB ext4 /boot
 many GB LVM, containing ext4 /, and ext4 user data partitions
 many GB LUKS encrypted LVM containing swap, and ext4 /home

Comment 1 Morgan Leijström 2014-06-02 12:16:59 UTC
Regression.

I installed fedora 16 on another disk and it suspend, hibernate and resume perfectly after default install without any setup, in both gnome and KDE.

Partitioning: separate ext4 /boot, then a LVM containing  /, /home, swap.

(No encryption, which is a difference from the fc20 install, but as it seem to hang after saving and fail to power down i believe it do not fault because of that.)

Tested the same disks (fc16 and fc20) in both a tinkpad T61 and a R61, and see that which of those machine the system runs on is irrelevant.

Comment 2 Morgan Leijström 2014-06-04 15:17:37 UTC
Further testing see https://bugzilla.redhat.com/show_bug.cgi?id=1096989#c16

I believe bere are two probably separate issues:
1) it do not power off.  I let this bug be about that.
2) when encryptipon is used on swap it fail restoring,
   splitting that off to -> bug 1104749

Comment 3 Morgan Leijström 2014-07-01 11:26:55 UTC
Tested again today and it hibernates correctly :)  kernel 3.14.9

(sidenote: now graphics driver vesa; uninstalled noveau for tests in another bug)

Comment 4 Morgan Leijström 2014-07-01 18:48:03 UTC
Ah, using vesa driver hibernating works.
But when using nouveau it still hangs as subscribed.

Who should have a look at this?
Would it help ifi can log the hibernating process?
How should i do then?

Comment 5 Justin M. Forbes 2014-11-13 16:02:56 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 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  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 21, and are still experiencing this issue, please change the version to Fedora 21.

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

Comment 6 Justin M. Forbes 2014-12-10 15:02:07 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 7 Morgan Leijström 2014-12-10 15:45:48 UTC
If someone could have responded with some help about how to produce some relevant data it would have been provided...


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