linux-kernel - Re: Problem with a notebook keyboard after plug into dock station

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] [day] [month] [year] [list]

Message-ID: <CAHp75VdgFTv7TzqDVDbdcv4RT-CZim7XLB1XTg2NWBxNFEuzgQ@mail.gmail.com>
Date:   Wed, 10 Jan 2018 20:39:21 +0200
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     kapica@....cvut.cz
Cc:     Platform Driver <platform-driver-x86@...r.kernel.org>,
        Darren Hart <dvhart@...radead.org>,
        Andy Shevchenko <andy@...radead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Problem with a notebook keyboard after plug into dock station

On Thu, Nov 30, 2017 at 1:09 PM, Aleš Kapica <kapica@....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