linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@kernel.org>
To: ibm-acpi-devel@lists.sourceforge.net
Cc: LKML <linux-kernel@vger.kernel.org>,
	Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
	Matthew Garrett <mjg@redhat.com>,
	platform-driver-x86@vger.kernel.org
Subject: [PROBLEM] thinkpad_acpi: unhandled HKEY event 0x6040
Date: Fri, 17 Aug 2012 13:57:49 +0300	[thread overview]
Message-ID: <CAOJsxLEb+J=p8Kd782VWPm0ft3D9ujOnV0x_Av+fjWp6QiTHQQ@mail.gmail.com> (raw)

Hello,

I'm seeing this when I dock a Thinkpad X220 laptop:

[ 3129.616279] thinkpad_acpi: unknown possible thermal alarm or
keyboard event received
[ 3129.616297] thinkpad_acpi: unhandled HKEY event 0x6040
[ 3129.616298] thinkpad_acpi: please report the conditions when this
event happened to ibm-acpi-devel@lists.sourceforge.net
[ 3129.616949] thinkpad_acpi: undocked from hotplug port replicator
[ 3129.617065] ACPI: \_SB_.GDCK - undocking
[ 3144.184916] ACPI: \_SB_.GDCK - docking
[ 3144.185204] ACPI: Unable to dock!

and the monitor doesn't come up.

I'm currently running a stock Fedora kernel:

[penberg@tux ~]$ uname -a
Linux tux 3.3.8-1.fc16.x86_64 #1 SMP Mon Jun 4 20:49:02 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux

but looking at drivers/platform/x86/thinkpad_acpi.c in Linus' tree, the event
is not handled there either:

        TP_HKEY_EV_UNK_6040             = 0x6040, /* Related to AC change?
                                                     some sort of APM hint,
                                                     W520 */

Help!

                        Pekka

             reply	other threads:[~2012-08-17 10:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 10:57 Pekka Enberg [this message]
2012-08-17 14:17 ` [PROBLEM] thinkpad_acpi: unhandled HKEY event 0x6040 Henrique de Moraes Holschuh
2012-08-17 14:34   ` Borislav Petkov

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='CAOJsxLEb+J=p8Kd782VWPm0ft3D9ujOnV0x_Av+fjWp6QiTHQQ@mail.gmail.com' \
    --to=penberg@kernel.org \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=ibm-acpi@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).