From: Sander Eikelenboom <linux@eikelenboom.it>
To: Sander Eikelenboom <linux@eikelenboom.it>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: if power button pressed 1x it creates the same ACPI event twice
Date: Mon, 19 Jan 2015 14:09:34 +0100 [thread overview]
Message-ID: <577867575.20150119140934@eikelenboom.it> (raw)
In-Reply-To: <1202643605.20150113174724@eikelenboom.it>
Hello Sander,
Tuesday, January 13, 2015, 5:47:24 PM, you wrote:
> Tuesday, January 13, 2015, 5:35:10 PM, you wrote:
>> Hi Rafael / Len,
>> When i press the power-button on my intel NUC, i get twp ACPI power-events shortly
>> after one another (within a second), instead of just one.
>> It doesn't matter if i have the old /proc/acpi interface enabled or disabled in the kernel config.
>> I have tested a few older kernels lingering around on the box and 3.14 already
>> has this problem. 3.2 (from the debian repo) doesn't have the problem, it only
>> fires one event.
>> I did find another report:
>> Re: lenovo ultrabay docking station: if power button pressed 1x it creates 2x the same ACPI event
>> http://www.spinics.net/lists/linux-acpi/msg54723.html
>> But that hasn't come to a conclusion ...
>> Unfortunately 3.2 - 3.19-rc4 is a bit of a largish bisect window, so that's
>> unfeasible :-)
>> I compiled in apci debug support and tried:
>> echo "0x00080000" > /sys/module/acpi/parameters/debug_layer
>> echo "0xffffffff" > /sys/module/acpi/parameters/debug_level
>> But i don't get any extra output in dmesg ?
>> Do you have any ideas for a debug patch or better values to figure out what is going on ?
>> --
>> Sander
> Hmm is it normal that it registers in this way (twice) ?
> [ 5.817980] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
> [ 5.837907] ACPI: Power Button [PWRB]
> [ 5.847540] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
> [ 5.866915] ACPI: Power Button [PWRF]
> --
> Sander
Hi Rafael / Len,
Got some more time to test:
- It's indeed giving one event for both registered power buttons (which in reality
are just one hardware button) printing acpid's "%e" revealed that:
1421672289-161192235 | button/power PBTN 00000080 00000000
1421672289-279647745 | button/power LNXPWRBN:00 00000080 00000004
So i tested on another box (amd instead of intel), and that also registers 2
power buttons:
# dmesg | grep -i button
[ 13.435060] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
[ 13.435294] ACPI: Power Button [PWRB]
[ 13.435495] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[ 13.435683] ACPI: Power Button [PWRF]
So the question is .. should both register and should scripts adjust to pick up just one of them ?
Or can, as a more general solution, just one be ignored when registering ?
--
Sander
next prev parent reply other threads:[~2015-01-19 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 16:35 if power button pressed 1x it creates the same ACPI event twice Sander Eikelenboom
2015-01-13 16:47 ` Sander Eikelenboom
2015-01-19 13:09 ` Sander Eikelenboom [this message]
2015-01-19 13:21 ` Sander Eikelenboom
2015-02-10 22:46 ` ACPI " Sander Eikelenboom
2015-02-11 0:37 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=577867575.20150119140934@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox