* Re: intel_vbtn dead keyboard bug on Acer Aspire E5-511G
2020-10-06 10:16 ` intel_vbtn dead keyboard bug on Acer Aspire E5-511G Andy Shevchenko
@ 2020-10-06 13:16 ` Hans de Goede
0 siblings, 0 replies; 2+ messages in thread
From: Hans de Goede @ 2020-10-06 13:16 UTC (permalink / raw)
To: Andy Shevchenko, Игорь, Mark Gross
Cc: platform-driver-x86
Hi Igor,
On 10/6/20 12:16 PM, Andy Shevchenko wrote:
> +Cc: mailing list and maintainers
>
> On Mon, Oct 05, 2020 at 05:59:40PM +0300, Игорь wrote:
>> Good time of day!
>> Sorry for bothering you, I found a strange bug in "intel_vbtn" kernel
>> module which makes the keyboard non-responding.
>> Reproducible 100% starting from kernel 5.4.0-45 and till 5.8.0-20.
>> Everything works fine on 5.4.0-42 or on Windows 10
>>
>> As a workaround I blacklisted the intel_vbtn module and everything works
>> fine. Seems like it somehow relative to tablet mode detection patch.
>>
>> I did research and found out that this bug is affecting Acer Aspire E5-511G
>> laptops and some HP model(s).
>> Here it is: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017
>>
>> Looking forward to hearing something from you.
>> Thanks for your attention!
Thank you for your bug report.
This should be fixed by this upstream commit, which landed in Linus' tree a couple of hours ago:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/platform/x86?id=8169bd3e6e193497cab781acddcff8fde5d0c416
Igor, if you do:
cat /sys/class/dmi/id/chassis_type
On your laptop, and the output is NOT "31" or "32" then this
fix should work for you.
If the output actually is "31" or "32 (which I do not expect),
then please let me know, because then we need a different fix.
I've also added this comment to the launchpad bug.
Regards,
Hans
^ permalink raw reply [flat|nested] 2+ messages in thread