Bug 200641

This generally means the kernel or system firmware aren't working.  Reassigning
to them.

A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

Could you confirm whether this is still an issue?

Yes, this is still an issue, but a less destructive one. I recently installed
Fedora 7, and now when I try to hibernate, instead of crashing the computer, the
screen briefly switches to a console, but after a few seconds switches back to
X. Would it help to have a listing of my hardware configuration?

That would be good. Dmesg may well be more useful in the short term, though.
Could you also check that "cat /sys/power/state" includes 'disk' in its output?

Created attachment 156827 [details]
Output from dmesg right after running the hibernate script on F7

I've attached the dmesg output generated after calling "hibernate" from the
console. Also, "cat /sys/power/state" simply returns "standby disk".

I'm not sure if it's relevant or visible in the dmesg output, but I also have a
software RAID 1 setup. 

Ok. Your dmesg tells one problem (there may be more we're not seeing yet):

pci_device_suspend(): rt2x00pci_suspend+0x0/0x5f [rt2x00pci]() returns -16
suspend_device(): pci_device_suspend+0x0/0x47() returns -16
Could not suspend device 0000:03:02.0: error -16

Is this a custom kernel? I can't find reference to an rt2x00 in the source 
code.

No, it's the standard kernel from yum. I think the rt2x00 is referring to my
Wifi PCI card. Perhaps this card doesn't support suspension?

Ah. I missed the mention of the update to FC-7 and was looking in the FC-5 
kernel source. Will update that flag.

The driver does have power management support. -16 is -EBUSY, and indicates 
that the card is failing to get into the requested power state in the time 
allowed. A temporary workaround would be to take the interface down and remove 
the module prior to suspending.

To get the issue fixed, I'd suggest contacting the driver authors 
(rt2x00.serialmonkey.com).

And here is the driver author. ;)

I have been made aware of the resume problems some days ago,
and I am looking into the issue. I first thought it had to do with
the firmware but I noticed that this bug is about a rt2500 device
which does not requires firmware.

So I am looking into this issue, and as soon as I have patches/information
I will let you know.

I also have a suspend to disk regression problem , on my compaq nx 6110.

I try : 
rpm -iv ~/kernel-2.6.20-1.2962.fc6.src.rpm 
cd /usr/src/redhat/SPECS/
rpmbuild -ba kernel-2.6.spec --with baseonly --target=i686
rpm -ivh /usr/src/redhat/RPMS/i686/kernel-2.6.20-1.2962.fc7.i686.rpm 
and exactly the same system just boot with kernel-2.6.20-1.2962.fc7 I don't have
any problem.

Just to confirm my situation, after removing the rt2x00 kernel modules, I was
able to hibernate successfully.

Re comment 11, thanks Ivo.

Re comment 12, Sergio, does it relate to the same driver? If not, could you 
please open a fresh bug?

(In reply to comment #14)
> Re comment 12, Sergio, does it relate to the same driver? 
No , sorry , it is just a regression . 

> If not, could you please open a fresh bug?
ok thanks, 

I have finally managed to do some work on the suspend/resume handling inside 
rt2x00 and I think I resolved the issue.
I am at the moment awaiting some test results from people, but if it works 
I'll release rt2x00 2.0.5 which can then be merged with the Fedora kernel.

CC'ed John to this list, since he is usually the one that merges rt2x00 
releases into the Fedora kernel. ;)

rt2x00 2.0.5 has just been released with Suspend/Resume patches.

Great. Sorry for my slowness in following up on this. I see from the cvs log
that there was an update pulling into the rawhide kernel tree:

revision 1.11
date: 2007/07/31 20:32:18;  author: linville;  state: Exp;  lines: +1 -0
iwlwifi, rt2x00, & zd1211rw updates

Chris, have you been able to give it a go? If so, what were the results?

Closing on the assumption that this has been fixed.