From: Pavel T. <pa...@si...> - 2005-07-31 05:25:36
|
> > It's exactly as the subject says - /proc/acpi/event is totally dummy > > It might be something particular to your configuration or hardware? > I've just tried 2.6.13-rc4's /proc/acpi/event on my TP 600X and it's > working okay. 'cat /proc/acpi/event' produces lid events, and acpid > is reading from it into the /var/log/apcid > Hi! I was trying to debug it a bit: 1) I put some printk's in drivers/acpi/bus.c, in acpi_bus_generate_event() and acpi_bus_receive_event(). They proved that neither of these functions is even called. 2) I modified /proc/acpi/debug_level. I've found that when I set the ACPI_LV_EXEC bit, every event generates a line osl-0698 [04] os_queue_for_execution: Scheduling function [c024bbdd(dbe5a900)] for deferred execution. (it is always the same regardless of the event which caused it). So the events are generated by hardware and at least osl knows about them. It seems that the execution is deferred ad infinitum :-). I didn't find any other bit which would generate anything more. Now I'm stuck a bit, I don't know how to continue with debugging. Any help is greatly appreciated. With regards, Pavel Troller |