This bug was fixed in the package linux - 4.10.0-42.46
---------------
linux (4.10.0-42.46) zesty; urgency=low
* linux: 4.10.0-42.46 -proposed tracker (LP: #1736152)
* CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()
* CVE-2017-16939
- ipsec: Fix aborted xfrm policy dump crash
linux (4.10.0-41.45) zesty; urgency=low
* linux: 4.10.0-41.45 -proposed tracker (LP: #1733524)
* tar -x sometimes fails on overlayfs (LP: #1728489)
- ovl: check if all layers are on the same fs
- ovl: persistent inode number for directories
* CVE-2017-12146
- driver core: platform: fix race condition with driver_override
* NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type
* Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el
* Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections
* Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610
* Invalid btree pointer causes the kernel NULL pointer dereference
(LP: #1729256)
- xfs: reinit btree pointer on attr tree inactivation walk
* Samba mount/umount in docker container triggers kernel Oops (LP: #1729637)
- ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
- ipv6: fix NULL dereference in ip6_route_dev_notify()
* Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi
* Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940 (LP: #1719697)
- Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"
-- Stefan Bader <stefan.ba...@canonical.com> Mon, 04 Dec 2017 15:04:01
+0100
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1731467
Title:
Cannot pair BLE remote devices when using combo BT SoC
Status in bluez package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
Triaged
Status in bluez source package in Xenial:
New
Status in linux source package in Xenial:
Fix Released
Status in bluez source package in Zesty:
New
Status in linux source package in Zesty:
Fix Released
Status in bluez source package in Artful:
New
Status in linux source package in Artful:
Fix Released
Bug description:
It has been observed that sometimes it is not possible to pair with
BLE remote devices when the host system is using combo (WiFi + BT)
chip.
The root cause of the disconnection has been identified as coming from
the internal to bluez timeout. If bluez does not hear any reply from for
two seconds the link is automagically disconnected. The reason fro the
silence is not however a failure of the remote device but quite often a
delay in the WiFi/BT combo driver that causes the packages not to reach
the bluez stack.
[Impact]
Not possible to pair BLE remote devices such as sensors and such with
Ubuntu when the host system uses BT+WiFi combo SoC. The connection
attempt is disturbed with a timeout.
[Fix]
It has been fixed by increasing the timeout value from 2 seconds to
4 seconds. It is enough for the events to reach the stack (measured
that it takes between 3 and 3.5 seconds).
[Testcase]
Tested with the device that failed to connect to Ubuntu Core gateway.
It fails w/o the patch, it connects just fine with the patch applied.
[Regression Potential]
Very small. The increased timeout is taken into consideration only for
new and scan report triggered connections. It will not make any already
working device to fail to pair.
[Other Info]
The bug has been discussed and fixed here:
https://marc.info/?l=linux-bluetooth&m=150824844606937&w=2
[Patch]
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571
The patch has been accepted by the upstream and will be a part of the next
kernel release. Currently in the bluetooth-next tree.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
