Description of problem:
Unloading the button.ko module shortly before suspending the notebook to RAM
results in it cold-booting the next time the button is pressed. If button.ko is
kept in memory, the problem is not seen.
Version-Release number of selected component (if applicable):
Unload the button ACPI module before S3 (suspend-to-RAM) sleep (e.g., with the
line SUSPEND_MODULES="... button ..." in /etc/sysconfig/pm), and initiate sleep.
Steps to Reproduce:
1. Have button unloaded before sleep.
3. Wake up with Power button.
Machine cold boots (i.e., POSTs, goes to GRUB, system comes back up).
System springs back to original state.
[This comment added as part of a mass-update to all open FC4 kernel bugs]
FC4 has now transitioned to the Fedora legacy project, which will continue to
release security related updates for the kernel. As this bug is not security
related, it is unlikely to be fixed in an update for FC4, and has been migrated
Please retest with Fedora Core 5.
Still there in 2.6.17-1.2187_FC5. Maybe an EC quirk... is it really necessary to
remove button.ko before suspending, or is there a better way to avoid processing
spurious power button events on resume (e.g. fix the user-space utilities or
have the kernel not pass up button events to user space if they were generated
before complete resume)? (I've removed it, but occasionally see the "logout" box
on resume, as if the event has been processed.)
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.
Still there in kernel-2.6.18-1.2200.fc5.
With current kernels we shouldn't need to be unloading 'button' any more.