Red Hat Bugzilla – Bug 485583
Immediate wakeup after suspend to ram
Last modified: 2009-12-18 02:55:18 EST
Description of problem:
Performing a suspend to RAM with an ASUS M2NPV-VM results in an immediate wakeup, just after the suspend.
Version-Release number of selected component (if applicable):
Under "standard" hardware conditions, always.
Some hardware changes result in proper S2R.
Steps to Reproduce:
rtcwake -s 30 -m mem
The PC goes into S2R and it wakes up immediatly.
The PC should stay 30 seconds in S2R and then wakeup.
First of all, it seems there are already some reports about this board and/or a similar problem, see:
One possible solution seems to enable the USB stdby power, changing some motherboard jumpers.
In this case the solution is not acceptable, since I do not want to power any USB device during S2R.
Another suggestion is to disable USB wakeup from /proc/acpi/wakeup, but with this kernel everything seem to be already disabled there.
Furthemore, someone suggested to remove the USB modules just before S2R. This is also not possible, since the keyboard is USB...
Second. If I detach all USB devices, then the S2R works. Maybe until some USB peripheral is attached.
Final word. It seems to me that S2R was working some kernel ago, maybe with F9, not really sure.
If there is any koji kernel to test, please let me know.
Though you did more searching and got some decent ideas, just pointing to
https://bugzilla.redhat.com/show_bug.cgi?id=471672 (specifically mentioning second attempt)
https://bugzilla.redhat.com/show_bug.cgi?id=463097 (which doesn't mention that).
My experience so far has been that if I alternate between suspend and hibernate, suspend will keep working as if it was the first time.
It seems that kernel-220.127.116.11-191.fc11.x86_64 fixes the issue, at least under F-11.
Try 18.104.22.168-93.fc10 from updates-testing if it ever gets there.
(In reply to comment #3)
> Try 22.214.171.124-93.fc10 from updates-testing if it ever gets there.
Ops, sorry, I thought comment #2 made clear I upgraded to F-11, so I cannot test the new kernel for F-10, in this respect.
Maybe others can...
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 '10'.
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 10'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 10 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:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.