Latest working kernel version: n/a Earliest failing kernel version: n/a Distribution: Gentoo Hardware Environment: NB Asus A6JC 2x Genuine Intel(R) CPU T2300 @ 1.66GHz Software Environment: gcc 4.2.3 Problem Description: The open lid event is not send, only first event is send when I close the lid. The /proc/acpi/button/lid/LID/state shows the state correctly. Here's evdump "Lid Switch" 1208550333 EV_SW SW_LID 1 1208550333 EV_SYN SYN_REPORT 0 1208550345 EV_SYN SYN_REPORT 0 1208550616 EV_SYN SYN_REPORT 0 I've also put printk into acpi_button_notify in button.c and it doesn't show anything when I open the lid. Can this be kernel bug or is it bios bug?
Will you please attach the output of acpidump, lspci -vxxx? Thanks.
Created attachment 15823 [details] lspci
Created attachment 15824 [details] acpidump
Please kill acpid, and cat /proc/acpi/event, Does any message pop up when you close and open the lid?
Does this happen in any earlier kernels, say 2.6.23?
> Please kill acpid, and cat /proc/acpi/event Only when I close the lid, when I open it doesn't pop up anything. button/lid LID 00000080 00000001 button/lid LID 00000080 00000002 button/lid LID 00000080 00000003 button/lid LID 00000080 00000004 I have the feeling that it didn't happen in earlier kernels but I'm not sure, will check.
Looks like it was just a feeling, it doesn't work in 2.6.23 too.
Please make sure CONFIG_ACPI_DEBUG is set echo 0x44 > /sys/module/acpi/parameters/debug_layer echo 0x8800001f > /sys/module/acpi/parameters/debug_level. there should be some messages every time an ACPI interrupt is fired, so would you please check if there is an interrupt when closing the lid and attach the dmesg output after the test? (Please point out which messages are generated when closing the lid)
Created attachment 15953 [details] dmesg When I open the lid interrupts aren't generated. I've added info to the log, the info starts with ">>>>".
lid event when lid is opened is not mandatory. I suspect this is not unusual for windows. Do you have a chance to run this laptop in windows? I guess windows enter sleep state once the lid is closed and resume when lid is opened, thus it doesn't need the lid event.
Well I don't need the lid event when I want to resume notebook form sleep, because I have to press a key to resume the notebook. Actually I don't need the open event so much (it would be better if the open event was send to make Kopete change its status from away back to online), but the problem is that kernel only sends first close event and then remembers the state and doesn't send next close events. So if I want to make Kopete change status to away when I close the lid it works only for the first time (after boot), next time the event isn't send, because kernel thinks that the lid was never opened.
Since opening lid can't generate interrupt, looks the behavior is expected. I'll mark the bug as invalid.