Red Hat Bugzilla – Bug 627980
fails to hibernate/suspend to disk
Last modified: 2012-06-04 11:22:39 EDT
Created attachment 441532 [details]
shows attempt to suspend
Description of problem:
Have KDE set to suspend to disk after X minutes of inactivity. Came in this morning to find the computer still running. Fan(s) was going full blast. Computer light was on. Can't remember if displays were still on. Keyboard and mouse did not respond. Pushing computer power button did nothing. Had to hold down computer power button to shut it off. Logs with anything interesting will be attached.
Version-Release number of selected component (if applicable):
only tried once
Steps to Reproduce:
1. set KDE to suspend after X minutes of inactivity
2. wait for computer to attempt to hibernate
Computer to be off with state suspended to disk.
Created attachment 441534 [details]
Think last line here is when it attempts to suspend.
Please try kernel-18.104.22.168-47.fc13 when it becomes available in updates-testing.
I'm still seeing the same problem. One additional note, the displays were off when I came in but they appeared to re-awaken when I pushed the power button. They both showed a blinking underline cursor in the upper-left corner. This is also now happening when I set it to Suspend to RAM whereas that used to work in 2.6.33.x.
Just saw the notice for 22.214.171.124-54. Will try that shortly.
(In reply to comment #4)
> Just saw the notice for 126.96.36.199-54. Will try that shortly.
Did it work?
nope, this time I got kernel dumps. I'll upload /var/log/messages. Let me know if you would like anything else. Just search for 'GPU lockup'.
Created attachment 447251 [details]
kernel: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
kernel: radeon 0000:04:00.0: GPU lockup CP stall for more than 1000msec
kernel: ------------[ cut here ]------------
kernel: WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:235 radeon_fence_wait+0x24c/0x2ea [radeon]()
kernel: Hardware name: Studio XPS 435MT
kernel: GPU lockup (waiting for 0x02357F30 last fence id 0x02357F2F)
Does it still happen without the vbox drivers?
Yes, similar symptoms happened after I rmmod vbox* and allowed it to hibernate. I'll upload another copy of /var/log/messages that shows what happened this morning.
Created attachment 447780 [details]
/var/log/messages after rmmod vbox*
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
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 prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
This is still happening in f15 kernel-188.8.131.52-27.fc15.x86_64 with or without the virtualbox drivers loaded. I'll upload some logs after this.
Created attachment 502553 [details]
Created attachment 502556 [details]
Created attachment 502557 [details]
f15 Xorg log
Created attachment 502558 [details]
f15 suspend log
[Mass hibernate bug update]
Dave Airlied has found an issue causing some corruption in the i915 fbdev after a resume from hibernate. I have included his patch in this scratch build:
This will probably not solve all of the issues being tracked at the moment, but it is worth testing when the build completes. If this seems to clear up the issues you see with hibernate, please report your results in the bug.