can't use keyboard after resume from suspend

Bug #1650319 reported by Gianfranco Costamagna
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Many times (around ~60% of them), resuming my laptop from suspend results in a not-working keyboard.

Solution/Workaround is: close lid, let it suspend again, and try to resume until keyboard gets working again.

Another solution is: plug an usb keyboard, and run something like "modprobe usbhid" or "modprobe hid", and this unblocks also the laptop keyboard.

Probably this is a bug in the kernel, but I have not enough knowledge to understand where it is located (maybe we can add some systemd hooks in /lib/systemd to catch such events and reload the kernel modules?)

G.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu12
ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
Uname: Linux 4.4.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Dec 15 16:15:08 2016
InstallationDate: Installed on 2016-05-11 (217 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Acer Aspire V3-772G
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-51-generic root=UUID=96a472a8-14aa-43e2-8953-a112b2ef6b9c ro quiet splash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/11/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.13
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA70_HW
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.13:bd10/11/2013:svnAcer:pnAspireV3-772G:pvrV1.13:rvnAcer:rnVA70_HW:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire V3-772G
dmi.product.version: V1.13
dmi.sys.vendor: Acer

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :
Revision history for this message
J (jonathan-vola) wrote :

I seem to have fixed this by adding `atkbd.reset` to my boot parameters.

You can add them to `GRUB_CMDLINE_LINUX` and `GRUB_CMDLINE_LINUX_DEFAULT` in `/etc/default/grub` then `sudo update-grub` for them to apply on every boot.

Dan Streetman (ddstreet)
Changed in systemd (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.