From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: "Mantas Mikulėnas" <grawity@gmail.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Len Brown" <lenb@kernel.org>,
"Robert Moore" <robert.moore@intel.com>,
"Lv Zheng" <lv.zheng@intel.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] Media keys cause "ACPI: \_SB_.ATKD: Unsupported event" on ASUS laptop
Date: Thu, 24 Apr 2014 06:21:52 +0100 [thread overview]
Message-ID: <20140424052151.GA9449@sucs.org> (raw)
In-Reply-To: <liocsk$le0$1@ger.gmane.org>
On Thu, Apr 17, 2014 at 02:11:15PM +0300, Mantas Mikulėnas wrote:
> After commit 1a699476e258 [two months ago], Linux has stopped
> recognizing the media & function keys on my laptop's keyboard (the
> laptop is ASUS K52JT.206).
>
> When I press any of the Fn keys (Play/Pause, Stop, Prev, Next, Vol+,
> Vol-, Mute, WiFi, Brightness +/-...), I get the following messages in dmesg:
>
> | ACPI: \_SB_.ATKD: Unsupported event type 0x45
> | ACPI: \_SB_.ATKD: Unsupported event type 0x43
> | ACPI: \_SB_.ATKD: Unsupported event type 0x40
> | etc.
I'm seeing the same problem with an EeePC 900's volume and brightness
keys:
[ 90.098518] ACPI: \_SB_.ATKD: Unsupported event type 0x14
[ 90.785202] ACPI: \_SB_.ATKD: Unsupported event type 0x15
[ 457.062072] ACPI: \_SB_.ATKD: Unsupported event type 0x2e
[ 457.926754] ACPI: \_SB_.ATKD: Unsupported event type 0x2d
[ 458.418740] ACPI: \_SB_.ATKD: Unsupported event type 0x2c
[ 458.821482] ACPI: \_SB_.ATKD: Unsupported event type 0x2b
[ 459.240896] ACPI: \_SB_.ATKD: Unsupported event type 0x2a
> In the past (v3.14 and earlier), those used to be reported as ACPI and
> input events. From `acpi_listen` on a good kernel:
>
> | hotkey ATK0100:00 00000045 00000000
> | cd/play CDPLAY 00000080 00000000 K
> |
> | hotkey ATK0100:00 00000031 0000000d
> | button/volumedown VOLDN 00000080 00000000 K
> |
> | hotkey ATK0100:00 00000016 00000000
> |
> | hotkey ATK0100:00 00000025 00000001
>
> Bisect output:
>
> 1a699476e25814343766342672c655fb135224cc is the first bad commit
> commit 1a699476e25814343766342672c655fb135224cc
> Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Date: Thu Feb 6 13:58:13 2014 +0100
>
> ACPI / hotplug / PCI: Hotplug notifications from acpi_bus_notify()
>
> Since acpi_bus_notify() is executed on all notifications for all
> devices anyway, make it execute acpi_device_hotplug() for all
> hotplug events instead of installing notify handlers pointing to
> the same function for all hotplug devices.
> [...]
>
> * Linux 3.14.0-rc1-00023-g1a699476e258 (bad)
> * Linux 3.14.0-rc1-00022-g5e6f236c2631 (good)
>
> (I'm not quite sure why they show up as 3.14-rc1 if they're after 3.14?)
>
> The kernel config is close to that of stock Arch Linux, except with
> entirely irrelevant devices disabled (PATA, SCSI, tuner, etc.)
Adding email addresses recommended by get_maintainer.pl to see if that
helps this to get noticed...
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2014-04-24 5:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 11:11 Media keys cause "ACPI: \_SB_.ATKD: Unsupported event" on ASUS laptop Mantas Mikulėnas
2014-04-24 5:21 ` Sitsofe Wheeler [this message]
2014-04-24 10:51 ` [REGRESSION] " Rafael J. Wysocki
2014-04-24 13:31 ` Mantas Mikulėnas
2014-04-24 13:31 ` Mantas Mikulėnas
2014-04-24 17:06 ` Rafael J. Wysocki
2014-04-24 17:06 ` 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=20140424052151.GA9449@sucs.org \
--to=sitsofe@yahoo.com \
--cc=grawity@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.