Keyboard plugged in to monitor USB hub does not work at password prompt

[Dan Watkins]

I have my external keyboard plugged in to my monitor's USB hub. Unless I unplug and replug the USB cable that connects the monitor hub to my machine, I can't use my keyboard on boot.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: cryptsetup 2:1.7.3-4ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Mon Oct 16 11:45:42 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-09-04 (1138 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: cryptsetup
UpgradeStatus: Upgraded to artful on 2016-12-05 (315 days ago)
cmdline: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw vt.handoff=7
crypttab:
 sda3_crypt UUID=dc873bc3-22f0-491d-9f5b-50d322f31987 none luks,discard
 #cryptswap1 UUID=f44f685a-f520-4e81-b35a-0b9cba44a8a9 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
---
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: daniel 9156 F.... pulseaudio
 /dev/snd/controlC0: daniel 9010 F.... volumeicon
                      daniel 9156 F.... pulseaudio
DistroRelease: Ubuntu 17.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-09-04 (1145 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: LENOVO 20ANCTO1WW
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic N/A
 linux-firmware 1.169
Tags: artful
Uname: Linux 4.13.0-16-generic x86_64
UpgradeStatus: Upgraded to artful on 2016-12-05 (321 days ago)
UserGroups: adm audio cdrom dip disk docker fuse libvirt libvirtd lpadmin lxd plugdev sambashare sbuild sudo
_MarkForUpload: True
dmi.bios.date: 05/21/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GLET70WW (2.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ANCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T440p
dmi.product.name: 20ANCTO1WW
dmi.product.version: ThinkPad T440p
dmi.sys.vendor: LENOVO

[Dan Watkins (oddbloke)]

(This _probably_ isn't cryptsetup specific, but I wasn't really sure where else to file it.)

[Steve Langasek (vorlon)]

This sounds like it would be a kernel issue.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1723994

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Dan Watkins (oddbloke)]

apport information

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 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'.

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.14-rc6

[Dan Watkins (oddbloke)]

I've been seeing this issue for a while, but only just got around to filing it. I'll test with the upstream kernel once I'm back at my desk.

[Dan Watkins (oddbloke)]

This does reproduce with the mainline kernel.

(Possibly worth noting that if I unplug/replug in the grub menu, the keyboard works there _and_ once I get to the disk decryption step.)

[Kai-Heng Feng (kaihengfeng)]

Does this happen on older kernel or earlier Ubuntu releases?

[Dan Watkins (oddbloke)]

On Tue, Oct 24, 2017 at 03:43:38AM -0000, Kai-Heng Feng wrote:
> Does this happen on older kernel or earlier Ubuntu releases?

This has been happening for the last six months, but I didn't have this
setup before then.

[Kai-Heng Feng (kaihengfeng)]

What's the output of `lsusb -t` with and without the monitor USB hub?

[Dan Watkins (oddbloke)]

On Thu, Oct 26, 2017 at 07:38:58AM -0000, Kai-Heng Feng wrote:
> What's the output of `lsusb -t` with and without the monitor USB hub?

Without:

/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
    |__ Port 6: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 6: Dev 5, If 2, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 6: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 7: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 11: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 11: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
    |__ Port 12: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 12: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M

With:

/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
    |__ Port 1: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 1: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        |__ Port 1: Dev 9, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 6: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 6: Dev 5, If 2, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 6: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 7: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 11: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 11: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
    |__ Port 12: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 12: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M

Which gives a diff of:

 /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
+ |__ Port 1: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M
+ |__ Port 1: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
+ |__ Port 1: Dev 9, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
     |__ Port 6: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M

[Kai-Heng Feng (kaihengfeng)]

They should work, at least at initramfs stage. You can use the keyboard to decrypt rootfs proves that.

I am not sure why they stopped working in rootfs though.

Does your lsusb in #11 captured when the keyboards didn't work?

[ 2.862043] input: Microsoft Natural® Ergonomic Keyboard 4000 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1.1/3-1.1:1.0/0003:045E:00DB.0004/input/input8
[ 2.862074] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-3/input2
[ 2.908170] clocksource: Switched to clocksource tsc
[ 2.920192] microsoft 0003:045E:00DB.0004: input,hidraw1: USB HID v1.11 Keyboard [Microsoft Natural® Ergonomic Keyboard 4000] on usb-0000:00:14.0-1.1/input0
[ 2.920395] input: Microsoft Natural® Ergonomic Keyboard 4000 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1.1/3-1.1:1.1/0003:045E:00DB.0005/input/input9
[ 2.980170] microsoft 0003:045E:00DB.0005: input,hidraw2: USB HID v1.11 Device [Microsoft Natural® Ergonomic Keyboard 4000] on usb-0000:00:14.0-1.1/input1
[ 2.996137] input: Logitech K360 as /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0003/0003:046D:4004.0006/input/input10
[ 2.996278] logitech-hidpp-device 0003:046D:4004.0006: input,hidraw3: USB HID v1.11 Keyboard [Logitech K360] on usb-0000:00:14.0-3:1
[ 2.998053] input: Logitech M570 as /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0003/0003:046D:1028.0007/input/input11
[ 2.998289] logitech-hidpp-device 0003:046D:1028.0007: input,hidraw4: USB HID v1.11 Mouse [Logitech M570] on usb-0000:00:14.0-3:2

[Dan Watkins (oddbloke)]

On Thu, Oct 26, 2017 at 03:09:12PM -0000, Kai-Heng Feng wrote:
> They should work, at least at initramfs stage. You can use the keyboard
> to decrypt rootfs proves that.

I can use the keyboard to decrypt the rootfs if it's plugged in after
boot. If it's plugged in before boot, it doesn't work.

(It also continues to work on _reboot_; it's just on a power cycle that
it doesn't.)

> Does your lsusb in #11 captured when the keyboards didn't work?

I'm not sure I understand the question; could you clarify?

[Kai-Heng Feng (kaihengfeng)]

> On 26 Oct 2017, at 11:20 PM, Dan Watkins <email address hidden> wrote:
>
> On Thu, Oct 26, 2017 at 03:09:12PM -0000, Kai-Heng Feng wrote:
>> They should work, at least at initramfs stage. You can use the keyboard
>> to decrypt rootfs proves that.
>
> I can use the keyboard to decrypt the rootfs if it's plugged in after
> boot. If it's plugged in before boot, it doesn't work.
>
> (It also continues to work on _reboot_; it's just on a power cycle that
> it doesn't.)
>
>> Does your lsusb in #11 captured when the keyboards didn't work?
>
> I'm not sure I understand the question; could you clarify?

I’d like to see the dmesg when the issue happens, because the dmesg here says both keyboards were detected (and should work).

So I guess the dmesg here was collected when you reboot instead of cold boot.

>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1723994
>
> Title:
> Keyboard plugged in to monitor USB hub does not work at password
> prompt
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> I have my external keyboard plugged in to my monitor's USB hub.
> Unless I unplug and replug the USB cable that connects the monitor hub
> to my machine, I can't use my keyboard on boot.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: cryptsetup 2:1.7.3-4ubuntu1
> ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
> Uname: Linux 4.13.0-16-generic x86_64
> ApportVersion: 2.20.7-0ubuntu3
> Architecture: amd64
> Date: Mon Oct 16 11:45:42 2017
> EcryptfsInUse: Yes
> InstallationDate: Installed on 2014-09-04 (1138 days ago)
> InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
> SourcePackage: cryptsetup
> UpgradeStatus: Upgraded to artful on 2016-12-05 (315 days ago)
> cmdline: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw vt.handoff=7
> crypttab:
> sda3_crypt UUID=dc873bc3-22f0-491d-9f5b-50d322f31987 none luks,discard
> #cryptswap1 UUID=f44f685a-f520-4e81-b35a-0b9cba44a8a9 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
> ---
> ApportVersion: 2.20.7-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: daniel 9156 F.... pulseaudio
> /dev/snd/controlC0: daniel 9010 F.... volumeicon
> daniel 9156 F.... pulseaudio
> DistroRelease: Ubuntu 17.10
> EcryptfsInUse: Yes
> InstallationDate: Installed on 2014-09-04 (1145 days ago)
> InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
> MachineType: LENOVO 20ANCTO1WW
> Package: linux (not installed)
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw vt.handoff=7
> ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
> RelatedPackageVersions:
> linux-restricted-modules-4.13.0-16-generic N/A
> linux-backports-modules-4.13.0-16-generic N/A
> linux-firmware 1.169
> Tags: art...