Bluetooth keyboard only works for a few moments

Bug #1732029 reported by Andrew Vos
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

After a, seemingly random, amount of time my Bluetooth Keyboard stops working. If I look in the Bluetooth tray it seems to be connecting and disconnecting really quickly.

It's an apple magic keyboard. There are absolutely no problem on Ubuntu Gnome 17.04 which is running kernel 4.10.

Please note that in my dmesg log I have plugged the keyboard into USB after trying to get it to work a few times.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic]
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.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: andrewvos 1394 F.... pulseaudio
 /dev/snd/controlC1: andrewvos 1394 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 13 22:09:01 2017
InstallationDate: Installed on 2017-11-10 (3 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=b7992a74-c44e-44cc-be68-f658972e448f ro quiet splash vt.handoff=7
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
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2017
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KYSKLi70.86A.0050.2017.0831.1924
dmi.board.name: NUC6i7KYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H90766-406
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0050.2017.0831.1924:bd08/31/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

Revision history for this message
Andrew Vos (andrewvos) wrote :
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Andrew Vos (andrewvos) wrote :
Download full text (6.0 KiB)

I just tried with the kernel here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732034

14:07:22 ~ • uname -a
Linux andrewvos-desktop 4.14.0+ #1 SMP Wed Nov 15 00:02:10 EST 2017 x86_64 x86_64 x86_64 GNU/Linux

And I noticed this in the logs:

[ 25.147643] logitech-hidpp-device 0003:046D:101B.0007: HID++ 1.0 device connected. [260/2107]
[ 112.844354] usb 1-2: USB disconnect, device number 2
[ 139.643141] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 139.643156] Bluetooth: HIDP socket layer initialized
[ 139.674331] hid-generic 0005:004C:0267.0008: unknown main item tag 0x0
[ 139.674560] input: Magic Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/bluetooth/hci0/hci0:256/0005:004C:0267.0008/input/input15
[ 139.675296] hid-generic 0005:004C:0267.0008: input,hidraw0: BLUETOOTH HID v0.66 Keyboard [Magic Keyboard] on a0:c5:89:13:3e:3f
[ 157.100149] iwlwifi 0000:03:00.0: Queue 10 is active on fifo 1 and stuck for 10000 ms. SW [91, 113] HW [91, 113] FH TRB=0x0c010a06a
[ 157.100533] iwlwifi 0000:03:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 157.100780] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 157.100785] iwlwifi 0000:03:00.0: Status: 0x00000100, count: 6
[ 157.100789] iwlwifi 0000:03:00.0: Loaded firmware version: 31.532993.0
[ 157.100793] iwlwifi 0000:03:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN
[ 157.100797] iwlwifi 0000:03:00.0: 0x000002B0 | trm_hw_status0
[ 157.100801] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
[ 157.100804] iwlwifi 0000:03:00.0: 0x00010040 | branchlink2
[ 157.100807] iwlwifi 0000:03:00.0: 0x00028DA6 | interruptlink1
[ 157.100810] iwlwifi 0000:03:00.0: 0x00028DA6 | interruptlink2
[ 157.100813] iwlwifi 0000:03:00.0: 0x00000000 | data1
[ 157.100817] iwlwifi 0000:03:00.0: 0x00000080 | data2
[ 157.100820] iwlwifi 0000:03:00.0: 0x07830000 | data3
[ 157.100823] iwlwifi 0000:03:00.0: 0x52817D36 | beacon time
[ 157.100826] iwlwifi 0000:03:00.0: 0xBE4D62C8 | tsf low
[ 157.100830] iwlwifi 0000:03:00.0: 0x00000017 | tsf hi
[ 157.100833] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
[ 157.100837] iwlwifi 0000:03:00.0: 0x08F6A80D | time gp2
[ 157.100840] iwlwifi 0000:03:00.0: 0x00000001 | uCode revision type
[ 157.100843] iwlwifi 0000:03:00.0: 0x0000001F | uCode version major
[ 157.100847] iwlwifi 0000:03:00.0...

Read more...

Revision history for this message
Andrew Vos (andrewvos) wrote :

Using this kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/

There is a difference when I pair the device it asks me to type in the PIN, where with the previous kernel it just said "is this pin correct".

After a few seconds my keyboard stops working though.

Revision history for this message
Andrew Vos (andrewvos) wrote :

I can’t work out how to add the tag kernel-bug-exists-upstream?

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Andrew Vos (andrewvos)
tags: added: kernel-bug-exists-upstream
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
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.