Bug 770946 - unable to hibernate/suspend at all
Summary: unable to hibernate/suspend at all
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: pm-utils
Version: 16
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-30 12:28 UTC by Mike Heller
Modified: 2012-01-17 08:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-17 06:48:35 UTC
Type: ---


Attachments (Terms of Use)
pm-utils-bugreport (36.55 KB, text/plain)
2011-12-30 12:28 UTC, Mike Heller
no flags Details

Description Mike Heller 2011-12-30 12:28:55 UTC
Created attachment 550057 [details]
pm-utils-bugreport

Description of problem:
since I upgraded to Fedora 16, I'm unable to hibernate my desktop at all!
The computer will suspend but afterwards it's impossible to resume at all. only a hard reset will solve the freeze.
During hibernation the computer freezes either and only the same solution is possible

With Fedora 15 this worked like a charm.

Version-Release number of selected component (if applicable):
pm-utils-1.4.1-12.fc16.i686

How reproducible:
try to hibernate/standby the computer


  
Actual results:
freezes of the computer

Expected results:
hibernate/suspend the computer

Additional info:

Comment 1 Jaroslav Škarvada 2012-01-10 16:33:09 UTC
Please provide output of:
# pm-utils-bugreport-info.sh
and:
# dmesg

Comment 2 Mike Heller 2012-01-11 15:34:28 UTC
since the kernel upgrade to 3.1.7-1.fc16 hibernation/suspending is working again.
I will have a look during this week if it works fine for several cycles.

I will send another comment either successful or failed test.

If needed I will upload dmesg output

Comment 3 Mike Heller 2012-01-17 06:48:35 UTC
this problem has gone since kernel 3.1.7.

Comment 4 Jaroslav Škarvada 2012-01-17 08:15:31 UTC
Thanks for info.


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