Unable to enter password to decrypt filesystem on boot after upgrading kernel to 4.4.0-51

[Chris Schadl]

Disk is encrypted using full disk encryption. I could enter my password to decrypt the disk when booting in 4.4.0-47, but after upgrading to 4.4.0-51, I'm prompted for the password, but I can't type anything.

I think the last time this happened there was some change with the USB HID modules or something (I'm using a USB keyboard). Has there been any changes to the USB modules or configuration between kernel 4.4.0-47 and 4.4.0-51?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-51-generic 4.4.0-51.72
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: chris 2447 F.... pulseaudio
 /dev/snd/controlC1: chris 2447 F.... pulseaudio
 /dev/snd/controlC0: chris 2447 F.... pulseaudio
CurrentDesktop: Unity
Date: Sat Dec 3 11:39:50 2016
HibernationDevice: RESUME=UUID=8a9bf6f5-bb32-459a-8f5b-fc7f95451c26
InstallationDate: Installed on 2014-07-04 (883 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet nosplash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-47-generic N/A
 linux-backports-modules-4.4.0-47-generic N/A
 linux-firmware 1.157.5
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/20/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2001
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH P67
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHP67:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.36

[Chris Schadl (cschadl)]

Tried it with mainline kernel 4.4.37-040437, looks like it's fixed there.

[penalvch (penalvch)]

Chris Schadl, the next step is to fully reverse commit bisect from kernel 4.4.30 to 4.4.36 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

It is most helpful that after the fix commit (not kernel version) has been identified, you then mark this report Status Confirmed.

Thank you for your help.