Bug 197903 - Keyboard/Touchpad sometimes unresponsive after boot on Lenovo Ideapad 100S
Summary: Keyboard/Touchpad sometimes unresponsive after boot on Lenovo Ideapad 100S
Status: NEW
Alias: None
Product: Other
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: other_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-17 09:42 UTC by klappnase
Modified: 2017-11-19 07:17 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.14.0
Tree: Mainline
Regression: No


Attachments
dmesg output (47.19 KB, text/plain)
2017-11-17 09:42 UTC, klappnase
Details
dmidecode info (11.92 KB, text/plain)
2017-11-17 09:43 UTC, klappnase
Details
DSDT info (517.99 KB, text/x-csrc)
2017-11-17 09:43 UTC, klappnase
Details

Description klappnase 2017-11-17 09:42:26 UTC
Created attachment 260693 [details]
dmesg output

Sometimes after booting the Lenovo Ideapad 100S (latest BIOS firmware version E2CN14WW) the keyboard and touchpad do not work. It seems that this problem was introduced with 4.13 and it is still present in 4.14.0. The bug has been initially reported at https://bugzilla.kernel.org/show_bug.cgi?id=113151 . There is a similar looking bug report (about totally different hardware though) at https://bugzilla.kernel.org/show_bug.cgi?id=197287 which may or may not be related.

I attached the output of dmesg (from a boot when keyboard and touchpad failed to work) and dmidecode and dsdt info. Please send me a note if you need further information.
Comment 1 klappnase 2017-11-17 09:43:29 UTC
Created attachment 260695 [details]
dmidecode info
Comment 2 klappnase 2017-11-17 09:43:55 UTC
Created attachment 260697 [details]
DSDT info
Comment 3 Jaakko 2017-11-19 07:17:31 UTC
I experience this same issue (as reported in 113151).

With 4.14.0 I am also seeing keyboard and touchpad failures during normal use. Boot was normal and everything worked as expected but during high load (and external mmcblk2 use) keyboard has now failed three times. The failure has happened after keydown and the keyup event never made it through. So that last pressed key was left on. I could then stop this repeating last key by plugging in external keyboard and typing something. And after the failure there was nothing new in dmesg.

I have never seen this happen with 4.13 but it's hard to say if I have had similar load conditions.

Note You need to log in before you can comment on or make changes to this bug.