Distribution:Debian testing + debian "unstable" kernel 2.6.11-1 Hardware Environment: asus V6V notebook (i915pm + Dothan 1.73 ) Software Environment: Problem Description: when loading battery kernel module, events seem to be pooled in a queue (exception : power button, and LID ) Exemple : After loading battery module, the next acpi event (button other than PWR or LID) does not appear. Sending sevreal events (between 2 to 8 !) while make the first event be send to acpid (or /proc/acpi/event). Actions on battery seems to "pool" invisible events to the queue : exemple : Send an event to ACPI. It does not appear (as expected). Read several times the /proc/acpi/battery/BAT0/info or state file (between 2 to 8) the event is send to acpid (or /proc/acpi/event). As said : PWRB and LID are not impacted. but SLEEP button is (Fn + F1). All other events are impacted. Steps to reproduce: shutdown acpid, modprobe the battery module and start playing around whith acpi events (Fn + buttons, AC unplugging ) while monitoring event file.
Created attachment 5009 [details] ACPI dsdt original (BIOS REV 0702) 0702A BIOS DSDT
Created attachment 5010 [details] lspci -vv on asus v6v
Created attachment 5011 [details] dmesg
still an issue in 2.6.13?
I have the same issue with kernel 2.6.12-12mdk (Mandriva kernel). I have an Asus M6Ne notebook. With fresh 2.6.13.2 kernel unpatched, it still isn't fixed. But with 2.6.13.2 + acpi-20050902 patch, it works fine. With older kernel, the solution was to compile with Preemptive kernel and HPET Timer Support enabled in kernel, but with 2.6.13.2 + acpi-20050902, preemptive kernel is no more needed.