From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: kapica@fel.cvut.cz
Cc: Platform Driver <platform-driver-x86@vger.kernel.org>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problem with a notebook keyboard after plug into dock station
Date: Wed, 10 Jan 2018 20:39:21 +0200 [thread overview]
Message-ID: <CAHp75VdgFTv7TzqDVDbdcv4RT-CZim7XLB1XTg2NWBxNFEuzgQ@mail.gmail.com> (raw)
In-Reply-To: <op.zaijxpd8dqmfw5@localhost>
On Thu, Nov 30, 2017 at 1:09 PM, Aleš Kapica <kapica@fel.cvut.cz> wrote:
> After the last dist upgrade my system (I use Debian unstable amd64), was
> encountered a problem, that begined from the kernel 4.13 and probably
> concerns the wmi module. Kernel version 4.12 and lower is ok.
>
> I have a HP ProBook 6475b notebook. When I plug-in it in the 'HP 230W
> Advanced Docking Station', the keyboard will stop working in the X server
> environment.
>
> Accepted only a code keys from external USB keyboard. But on the text
> console works the notebook keyboard seamlessly too.
>
> acpi_listen:
> …
> 95F24279-4D7B-43 00000080 00000000
> video/tabletmode TBLT 0000008A 00000001
> ac_adapter ACPI0003:00 00000080 00000001
> …
>
> When unplug notebook from dock station, it work again normal.
>
> I don't know if is the bug or feature, but it is very uncomfortable because
> external keyboard occupied place on my table.
>
> If it should be feature, please advise mee how to turn it off.
Big sorry for missed answer.
Is it possible to you to
1) check if latest vanilla still has the issue;
2) do git bisect to find a culprit commit?
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2018-01-10 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 11:09 Problem with a notebook keyboard after plug into dock station Aleš Kapica
2018-01-10 18:39 ` Andy Shevchenko [this message]
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=CAHp75VdgFTv7TzqDVDbdcv4RT-CZim7XLB1XTg2NWBxNFEuzgQ@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=kapica@fel.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--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).