Ubuntu 16.04: unresponsive keyboard (15 sec) after grub

[Federico Leoni]

I've upgraded my notebook with an SSD. All works fine and I can reach the login in less than 10 seconds. Problem is I can't use the internal keyboard (perfectly working on grub) for at least 10-15 seconds, then it starts to working just fine. The touchpad and capacitive buttons are working without issues.

Luckily I have a second HDD on my machine and I've made some tests with the old mechanical drive, with this unit I can input my password on LightDM without any delay.

The issue is not (only) related to Xorg or LightDM, because starting in recovery mode shown the same issue with both disks: if I use an external keyboard (a Logitech k400r in my case) I have no issue at all on both login and recovery mode.
Seems kdb needs some time to be up and running.

Here's a video showing a full cycle of boots:

https://youtu.be/yseDPvqWNw4

And here a video of the recovery mode:

https://youtu.be/vbsD9tb-Dn8

Fresh install of Ubuntu 16.04 LTS without any other packages.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Jun 25 12:01:50 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics Controller (primary) [103c:30cd]
   Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics Controller (secondary) [103c:30cd]
InstallationDate: Installed on 2016-06-25 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=56bb4994-c2b0-4ada-9f3d-493898e2ad39 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/07/2008
dmi.bios.vendor: Phoenix
dmi.bios.version: F.2B
dmi.board.name: 30CD
dmi.board.vendor: Wistron
dmi.board.version: 80.52
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvrF.2B:bd05/07/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2B:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv2700 Notebook PC
dmi.product.version: F.2B
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Jun 25 12:00:23 2016
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 19778
 vendor SEC
xserver.version: 2:1.18.3-1ubuntu2

[Federico Leoni (effelle-gmail)]

Tested the same SSD with Ubuntu 14.04, same issue.
I gave a spin with Windows 7 just to be sure is not an hardware related issue: the keyboard works fine.

[Federico Leoni (effelle-gmail)]

Since I fear ubuntu is unable to detect correctly my keyboard at startup after passing grub (why?), I'm trying to solve with xinput after X init.
Here's my xinput list:

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ AlpsPS/2 ALPS GlidePoint id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Sleep Button id=8 [slave keyboard (3)]
    ↳ HP Webcam id=9 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
    ↳ HP WMI hotkeys id=12 [slave keyboard (3)]

My keyboard is on id 10.
Using the option 'greeter-setup-script' I've added a script on my lightdm configuration:

#!/bin/sh
xinput --list > /home/effe/list.txt
xinput float 10
sleep 1
xinput reattach 10 3

The script is working, but the issue persists: the keyboard doesn't work for 10-15 seconds after the greeter and I need to wait.

[Federico Leoni (effelle-gmail)]

I've tried to boot with a keylogger loaded on rc.local and as an option on lightdm to see if the keys are captured but I got no input from the moment I leave GRUB and the kernel start to load until the infamous 15 seconds after LighDM is loaded.

Since the issue seems to be strongly related to i8042, I've tested some kernel options:

i8042.direct - Put keyboard port into non-translated mode
i8042.dumbkbd - Pretend that controller can only read data from keyboard and cannot control its state (Don't attempt to blink the leds)
i8042.noaux - Don't check for auxiliary (== mouse) port
i8042.noloop - Disable the AUX Loopback command while probing for the AUX port
i8042.nomux - Don't check presence of an active multiplexing controller
i8042.nopnp - Don't use ACPIPnP / PnPBIOS to discover KBD/AUX controllers
i8042.reset - Reset the controller during init and cleanup

Again without any tangible results.

I've extracted from dmesg all the information from i8042 (with 'i8042.debug' option on GRUB).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.