http://bugzilla.kernel.org/show_bug.cgi?id=11428
Summary: [regression] LID switch events are no longer reported
using /dev/input/event*
Product: ACPI
Version: 2.5
KernelVersion: 2.6.26-rc3
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Latest working kernel version: 2.6.25
Earliest failing kernel version: 2.6.26-rc3 (bisecting in progress)
Distribution: Debian
Hardware Environment: Clevo D410J
Software Environment:
Problem Description:
Zhao Yakui wrote:
> > On Sat, 2008-08-23 at 23:43 +0200, Márton Németh wrote:
>> >> Hi,
>> >>
>> >> I am using Linux 2.6.27-rc4 on Clevo D410J laptop and the I can
>> >> query the LID switch state like this:
>> >>
>> >> # cat /proc/acpi/button/lid/LID/state
>> >> state: open
>> >> # cat /proc/acpi/button/lid/LID/state
>> >> state: closed
>> >>
>> >> If I check the event4, I get no events when the LID switch is pushed:
>> >>
>> >> # evtest /dev/input/event4
>> >> Input driver version is 1.0.0
>> >> Input device ID: bus 0x19 vendor 0x0 product 0x5 version 0x0
>> >> Input device name: "Lid Switch"
>> >> Supported events:
>> >> Event type 0 (Sync)
>> >> Event type 5 (?)
>> >> Event code 0 (?)
>> >> Testing ... (interrupt to exit)
> > It seems that the status of LID device is correct, but there is no LID
> > input event. Right?
> > Will you please enable the CONFIG_ACPI_DEBUG in kernel configuration and
> > boot the system with the option of "acpi.debug_layer=0x00090004
> > acpi.debug_level=0x01f"?
> > After pressing the LID switch several times, please attach the output of
> > dmesg.
> >
> > It will be great if you can attach the output of acpidump.
> >
> > Of course you can open a new bug in bugzilla and attach the output of
> > dmesg, acpidump.
> >
> > http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
> >
> > Thanks.
>> >> The events are only reported if I suspend to RAM with "s2ram -f -p -s".
Steps to reproduce:
1. Execute "s2ram -f -p -s". Now the system suspends to RAM.
2. Push the LID switch and hold it down.
3. Wake the system with the POWER button.
4. After the system is up, release the LID switch to see the screen.
5. "evtest" reports the following line:
Event: time 1219526119.163805, type 5 (?), code 0 (?), value 1
6. Execute "s2ram -f -p -s" again.
7. Wake the system with the POWER button.
8. "evtest" reports the following line:
Event: time 1219526913.208803, type 5 (?), code 0 (?), value 0
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
