Red Hat Bugzilla – Bug 212092
show a warning when trying to suspend a xen kernel
Last modified: 2013-03-05 22:47:30 EST
Suspend of T60 fails with "Suspend problem" note which asks to refer to FAQ
This comes to /var/log/messages:
Oct 25 05:21:43 tomi-ibm gnome-power-manager: (tomalkki) Suspending computer
because the DBUS method Suspend() was invoked
Oct 25 05:21:47 tomi-ibm kernel: printk: 73 messages suppressed.
Oct 25 05:21:47 tomi-ibm kernel: 4gb seg fixup, process beagled (pid 3480),
Oct 25 05:21:49 tomi-ibm gnome-power-manager: (tomalkki) Resuming computer
does running 'pm-suspend' from a shell work?
I had the same problem on a Thinkpad X60. Fedora was booting into the PAE
kernel by default. If I selected the normal kernel at the grub menu, suspend
works fine. It seems that PAE and suspend don't play well together (also note,
that the 586 kernel was installed mistakenly, as seems to be common in FC6, but
I don't think that this is affecting the suspend).
I resolved that this is because of xen -kernel.
I think there should be at least a clear error message stating that xen -kernel
can't be used to suspend.
(In reply to comment #2)
> I had the same problem on a Thinkpad X60. Fedora was booting into the PAE
> kernel by default. If I selected the normal kernel at the grub menu, suspend
> works fine. It seems that PAE and suspend don't play well together (also note,
On my X41 suspend works fine with a PAE kernel.
Surely we should just fix XEN to suspend?
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.