Bug 209923 - atkbd serio0: Failed to enable/deactivate keyboard on isa0060/serio0
Summary: atkbd serio0: Failed to enable/deactivate keyboard on isa0060/serio0
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_input-devices
URL:
Keywords:
Depends on:
Blocks: 178231
  Show dependency tree
 
Reported: 2020-10-29 02:30 UTC by Zhang Rui
Modified: 2024-03-30 06:42 UTC (History)
1 user (show)

See Also:
Kernel Version: 5.9.0
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Zhang Rui 2020-10-29 02:30:26 UTC
We've seen this error message during suspend/resume stress test

atkbd serio0: Failed to deactivate keyboard on isa0060/serio0
and
atkbd serio0: Failed to enable keyboard on isa0060/serio0

This happens on many of the platforms we have tested, and most of them are 100% reproducible for every suspend/resume iterations.

It seems that this does not bring any other impact rather than this error message. 
May I know what problem this is?
Comment 1 Berend De Schouwer 2024-03-30 06:42:00 UTC
I am seeing this on a machine (Asus Vivobook) that then wakes up when you hit the keyboard.

It's a problem because you can hit the keyboard while the lid is closed, by squeezing the laptop lightly.  This can (and does) happen in a laptop bag.  That then causes the laptop to wake up from suspend in the bag.

I *assume* this message and the fact that the keyboard remains active with the lid closed are related.

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