Bug 24840

Summary: Bluetooth remote stops working as expected with kernel-desktop-4.14.119-1.mga6-1-1.mga6
Product: Mageia Reporter: Rolf Pedersen <rolfpedersen>
Component: RPM PackagesAssignee: Kernel and Drivers maintainers <kernel>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Normal CC: jan.ciger, marja11, tmb
Version: 6   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: kernel-4.14.119-1.mga6.src.rpm CVE:
Status comment:
Attachments: journalctl at time that issue occurs

Description Rolf Pedersen 2019-05-19 15:51:13 CEST 
Description of problem:
[rolf@z170i ~]$ rpm -qa | grep kernel
kernel-desktop-4.14.116-1.mga6-1-1.mga6
kernel-userspace-headers-4.14.119-1.mga6
kernel-desktop-4.14.119-1.mga6-1-1.mga6
kernel-desktop-devel-4.14.119-1.mga6-1-1.mga6
kernel-doc-4.14.119-1.mga6
kernel-desktop-latest-4.14.119-1.mga6
kernel-firmware-20170531-1.mga6
kernel-desktop-devel-4.14.116-1.mga6-1-1.mga6
kernel-firmware-nonfree-20180606-1.mga6.nonfree
kernel-desktop-devel-latest-4.14.119-1.mga6

This issue occurs on a Skylake mini-itx machine that I've got running Mageia 6 for some time with reliability.  The remote I use is a Sony BD remote.  Onboard bluetooth is disabled in UEFI and `lsusb` identifies the bluetooth usb dongle in use as:

Bus 001 Device 007: ID 0461:4d75 Primax Electronics, Ltd Rocketfish RF-FLBTAD Bluetooth Adapter

For some time, up to the previous kernel-desktop-4.14.116-1.mga6-1-1.mga6, once paired, the remote automatically pairs with a keypress, even after reboot, times out for battery saving as configured in /etc/bluetooth/input.conf, and re-pairs with the next keypress.  Not so with kernel-desktop-4.14.119-1.  I can pair it with the new kernel after some efforts with `bluetoothctl` and/or the Plasma applet but it does not re-pair with a button press after disconnect or reboot.  Simply booting to the previous kernel restores the desired/expected behavior.

I'll attach output of `sudo journalctl -f` while booted to the respective kernels, started just before a keypress on the sleeping remote and ending just after the keypress(es).  The first excerpt is with -116 and documents a successful pairing.  The second is with -119, where the keypress is detected, led on the dongle blinks two or three times, then stops (it continues blinking with a successful pairing on -116), and the keypress is repeated several times with no success.  The third is a subsequent boot to -116 to establish repeatability of the success with the previous kernel(s).  

Version-Release number of selected component (if applicable):
kernel-desktop-4.14.119-1.mga6-1-1.mga6

How reproducible:
As above

Steps to Reproduce:
As above

Thanks.
Comment 1 Rolf Pedersen 2019-05-19 15:52:47 CEST 
Created attachment 11003 [details]
journalctl at time that issue occurs
Comment 2 Jan Ciger 2019-05-19 22:28:29 CEST 
I think I can confirm this same bug with a bluetooth Logitech TravelMouse and a cheap wireless keyboard (both using Bluetooth Classic protocol). Both devices work fine when freshly paired however they will not reconnect after waking from sleep anymore - the bluetooth applet shows them constantly connecting and disconnecting. 

I am using a cheap CSR dongle (0a12:0001). 

The older stable kernel (4.14.116) didn't have these issues.

CC: (none) => jan.ciger

Marja Van Waes 2019-05-21 11:28:24 CEST

CC: (none) => marja11
Assignee: bugsquad => kernel

Comment 3 Thomas Backlund 2019-05-22 11:02:23 CEST 
Yeah, its a regression introduced in 4.14.118.

A suggested fix was posted on linux-bluetooth, so I'll add it and push a new kernel to mga6 updates_testing

CC: (none) => tmb

Comment 4 Thomas Backlund 2019-05-22 11:54:05 CEST 
Fix added in kernel-5.1.4-1.mga7 for Cauldron and in kernel-4.14.121-1.mga6 for Mageia 6.

Both currently building...
Comment 5 Rolf Pedersen 2019-05-22 17:02:30 CEST 
[rolf@z170i ~]$ uname -r
4.14.121-desktop-1.mga6

After I installed this kernel, making no other changes, the remote connects with a button press and respects the timeout I have configured, as before.  Tried a couple of boots and I expect this bug is fixed.  Thanks.

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Comment 6 Jan Ciger 2019-05-22 20:58:23 CEST 
Excellent, thank you!