Bug 24502 - Missing lid events
Summary: Missing lid events
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Zhang Rui
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-09 01:35 UTC by Alessandro Guido
Modified: 2012-05-24 07:50 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.37-rc5
Subsystem:
Regression: No
Bisected commit-id:


Attachments
acpidump output (22.83 KB, application/octet-stream)
2010-12-09 09:58 UTC, Alessandro Guido
Details
Interrupts: Laptop freshly booted (2.20 KB, text/plain)
2010-12-09 10:00 UTC, Alessandro Guido
Details
Interrupts: Lid closed for the 1st time (2.20 KB, text/plain)
2010-12-09 10:01 UTC, Alessandro Guido
Details
Interrupts: Lid reopened for the 1st time (2.20 KB, text/plain)
2010-12-09 10:02 UTC, Alessandro Guido
Details
Interrupts: Lid closed for the 2nd time (2.20 KB, text/plain)
2010-12-09 10:02 UTC, Alessandro Guido
Details
Interrupts: Lid reopened for the 2nd time (2.20 KB, text/plain)
2010-12-09 10:03 UTC, Alessandro Guido
Details
acpidump output (binary format) (17.45 KB, application/octet-stream)
2010-12-09 10:07 UTC, Alessandro Guido
Details
acpidump output (81.21 KB, text/plain)
2010-12-14 07:46 UTC, Alessandro Guido
Details

Description Alessandro Guido 2010-12-09 01:35:16 UTC
Using acpi_listen, I noticed that closing and reopening my laptop's lid several times generates just one initial "lid close" event and nothing more.

My laptop is a Sony VAIO VGN-FS215S.
Comment 1 Zhang Rui 2010-12-09 03:05:48 UTC
please attach the acpidump of your laptop.

please run "grep . /sys/firmware/acpi/interrupts/*" both before and after closing/opening the lid.
Comment 2 Alessandro Guido 2010-12-09 09:58:28 UTC
Created attachment 39482 [details]
acpidump output
Comment 3 Alessandro Guido 2010-12-09 10:00:26 UTC
Created attachment 39492 [details]
Interrupts: Laptop freshly booted
Comment 4 Alessandro Guido 2010-12-09 10:01:04 UTC
Created attachment 39502 [details]
Interrupts: Lid closed for the 1st time
Comment 5 Alessandro Guido 2010-12-09 10:02:05 UTC
Created attachment 39512 [details]
Interrupts: Lid reopened for the 1st time
Comment 6 Alessandro Guido 2010-12-09 10:02:37 UTC
Created attachment 39522 [details]
Interrupts: Lid closed for the 2nd time
Comment 7 Alessandro Guido 2010-12-09 10:03:07 UTC
Created attachment 39532 [details]
Interrupts: Lid reopened for the 2nd time
Comment 8 Alessandro Guido 2010-12-09 10:07:21 UTC
Created attachment 39552 [details]
acpidump output (binary format)
Comment 9 Len Brown 2010-12-14 03:16:34 UTC
is it possible to attach the regular output from acpidump without converting it to binary format?

eg. # acpidump > acpidump.out
Comment 10 Alessandro Guido 2010-12-14 07:46:36 UTC
Created attachment 40082 [details]
acpidump output
Comment 11 Zhang Rui 2010-12-27 06:04:39 UTC
please kill acpid and run "cat /proc/acpi/event", do you get the same output as acpi_listen?
Comment 12 Alessandro Guido 2010-12-28 10:17:48 UTC
(In reply to comment #11)
> please kill acpid and run "cat /proc/acpi/event", do you get the same output
> as
> acpi_listen?

No, all lid close event are reported correctly.

$ cat /proc/acpi/event 
button/lid LID0 00000080 00000001
button/lid LID0 00000080 00000002
button/lid LID0 00000080 00000003
button/lid LID0 00000080 00000004
Comment 13 Alessandro Guido 2010-12-28 10:31:04 UTC
(In reply to comment #12)
> (In reply to comment #11)
> > please kill acpid and run "cat /proc/acpi/event", do you get the same
> output as
> > acpi_listen?
> 
> No, all lid close event are reported correctly.
> 
> $ cat /proc/acpi/event 
> button/lid LID0 00000080 00000001
> button/lid LID0 00000080 00000002
> button/lid LID0 00000080 00000003
> button/lid LID0 00000080 00000004

Mhh, it seems that something is broken wrt netlink notification.
With CONFIG_ACPI_PROC_EVENT=y acpid uses /proc/acpi/event and acpi_listen reports all close events.
With CONFIG_ACPI_PROC_EVENT=n or starting acpid with the --netlink argument, not all events are reported.
Comment 14 Zhang Rui 2012-01-18 02:28:53 UTC
(In reply to comment #13)
> (In reply to comment #12)
> > (In reply to comment #11)
> > > please kill acpid and run "cat /proc/acpi/event", do you get the same
> output as
> > > acpi_listen?
> > 
> > No, all lid close event are reported correctly.
> > 
> > $ cat /proc/acpi/event 
> > button/lid LID0 00000080 00000001
> > button/lid LID0 00000080 00000002
> > button/lid LID0 00000080 00000003
> > button/lid LID0 00000080 00000004
> 
> Mhh, it seems that something is broken wrt netlink notification.
> With CONFIG_ACPI_PROC_EVENT=y acpid uses /proc/acpi/event and acpi_listen
> reports all close events.
> With CONFIG_ACPI_PROC_EVENT=n or starting acpid with the --netlink argument,
> not all events are reported.

that's because some events (power button, lid, brightness switching, etc) go to input layer, rather than netlink.

Anyway, it's great that kernel bugzilla is back.

can you please verify if the problem still exists in the latest upstream
kernel?
Comment 15 Zhang Rui 2012-05-24 07:50:10 UTC
bug closed as there is no response from the bug reporter.
please feel free to reopen it if the problem still exists in the latest upstream kernel.

Note You need to log in before you can comment on or make changes to this bug.