Red Hat Bugzilla – Bug 119330
Last modified: 2015-01-04 17:05:08 EST
On two FC2 Test 2 machines, /proc/acpi/event is unreadable, which
means that acpid cannot start. root cannot 'cat /proc/acpi/event',
/bin/cat: /proc/acpi/event: Device or resource busy
and acpid also complains that it cannot open /proc/acpi/event.
Therefore, acpid does not start. This happens regardless of whether
SELinux is in enforcing mode or not.
anything in dmesg re acpi ?
does it work with selinux=0 ?
What is the output of ps -ef | grep `fuser /proc/acpi/event | awk
selinux=0 kernel panics (attempt to kill init) I'm attempting to yum
upgrade to find out.
kernel version is: 2.6.3-220.127.116.11.1
Does this work in current trees?
Its still broken. Doing a 'sudo cat /proc/acpi/event' still returns
busy. The fuser/awk thing also doesn't work, as fuser
/proc/acpi/event | awk ... returns nothing, hence grep has nothing to
you need to talk to acpid. the event file can only be opened exclusively, and
acpid stole it already.