lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 19 Jan 2015 14:09:34 +0100
From:	Sander Eikelenboom <linux@...elenboom.it>
To:	Sander Eikelenboom <linux@...elenboom.it>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Len Brown <lenb@...nel.org>
CC:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: if power button pressed 1x it creates the same ACPI event twice

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ