Bug 211579 - kacpid does not trigger on power fail
kacpid does not trigger on power fail
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-10-20 04:29 EDT by Bengt Hammarlin
Modified: 2015-01-04 17:29 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-10-20 17:46:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bengt Hammarlin 2006-10-20 04:29:07 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20060313 Fedora/ Firefox/ pango-text

Description of problem:
kacpid does not always trigger on a powerfail signal shorter than 125 msec and never if the signal is shorter than ~95 msec.
This is important since there is usually time to at least save buffers and sync filesystems on the remaining capacitor charge in the power supply. The power supply in some small systems delivers a powerfail signal with a duration of 100 msec +- 10 msec.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.send power button signal generated at 90 msec... nothing happens
2.send power button signal generated at 100 msec... 
      power down sequence starts 30% of the time
3.send power button signal generated at 125 msec...
      power down sequence starts every time

Actual Results:

Expected Results:

Additional info:
Comment 1 Phil Knirsch 2006-10-20 06:13:59 EDT
This is kernel acpi related though, so i'll reassign it to the proper component.

Read ya, Phil
Comment 2 Dave Jones 2006-10-20 17:46:25 EDT
there's absolutely no guarantee that kacpid is going to be scheduled in any
given timeframe.

Note You need to log in before you can comment on or make changes to this bug.