Red Hat Bugzilla – Bug 465778
Resume after WoL causes kacpid and kacpi_notify eat whole CPU
Last modified: 2009-12-18 01:31:03 EST
Description of problem:
Sending magic wake on LAN packet with ether-wake to the notebook resumes from RAM, but kacpid and kacpi_notify kernel processes are running at full speed
88 root 15 -5 0 0 0 S 76.8 0.0 0:22.36 kacpid
89 root 15 -5 0 0 0 R 21.9 0.0 0:06.39 kacpi_notify
Resume from RAM as well as from hibernated state works well.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. suspend to RAM
Suspend to RAM and resume afterwards is OK.
Behaviour as w/ 126.96.36.199
Same behaviour w/
The same shit w/
Je to furt to samé. Kurva fix! Pozdravuju všechny psychopaty.
Whiskey Tango Foxtrot?
Merda. I'm sick of this crap. It was working for 3+ years.
Still the same, over and over again.
Created attachment 321712 [details]
Linux 188.8.131.52 kernel configuration
With this configuration WoL works as before. Also, LCD panel backlight brightness has 8 levels, not 3.
This seems to be a duplicate of Bug 470321 (or the other way around) - however, that bug now has the developers attention.
S2D is screewed too. I'm still wondering why I'm wasting my time w/ this junk.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
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.