Subject: Re: ACPI notify events (was: Bogus ACPI battery information in recent current)
To: None <>
From: Sverre Froyen <>
List: current-users
Date: 12/17/2007 13:28:15
On Monday 17 December 2007, Sverre Froyen wrote:
> Hi,
> My issue with the AC adaptor status not being detected correctly turns out
> to be a little broader that I first though.  I put a few printfs in
> acpi_acad.c and noticed that acpiacad_notify_handler was never called. 
> Hence, the flag AACAD_F_AVAILABLE does not get set so the adaptor status
> changes will not be noticed.  (If I make the call to acpiacad_get_status in
> acpiacad_refresh unconditional, envstat detects the status changes
> correctly.)
> It actually looks like no acpi notify method gets called.  A printf in
> acpibat_notify_handler shows that it does not get called when the battery
> is removed.  My power button is also non-operational
> (acpibut_notify_handler?).

Correction!  I added more printfs and also turned on ACPI_DEBUG.  It turns out 
that sometimes I get calls to maybe a couple notify handlers immediately 
after a boot.  Then it looks like that part of the system (ACPI calling the 
notify handlers) gets stuck.  Could this be a locking issue?  How can I tell?