[Group.of.nepali.translators] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
** Changed in: bluez (Ubuntu) Status: In Progress => Won't Fix ** No longer affects: bluez (Ubuntu Xenial) ** No longer affects: bluez (Ubuntu Zesty) ** No longer affects: bluez (Ubuntu Artful) ** No longer affects: bluez (Ubuntu) -- 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 linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released 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/linux/+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
[Group.of.nepali.translators] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
This bug was fixed in the package linux - 4.13.0-25.29 --- linux (4.13.0-25.29) artful; urgency=low * linux: 4.13.0-25.29 -proposed tracker (LP: #1741955) * CVE-2017-5754 - Revert "UBUNTU: [Config] updateconfigs to enable PTI" - [Config] Enable PTI with UNWINDER_FRAME_POINTER linux (4.13.0-24.28) artful; urgency=low * linux: 4.13.0-24.28 -proposed tracker (LP: #1741745) * CVE-2017-5754 - x86/cpu, x86/pti: Do not enable PTI on AMD processors linux (4.13.0-23.27) artful; urgency=low * linux: 4.13.0-23.27 -proposed tracker (LP: #1741556) [ Kleber Sacilotto de Souza ] * CVE-2017-5754 - x86/mm: Add the 'nopcid' boot option to turn off PCID - x86/mm: Enable CR4.PCIDE on supported systems - x86/mm: Document how CR4.PCIDE restore works - x86/entry/64: Refactor IRQ stacks and make them NMI-safe - x86/entry/64: Initialize the top of the IRQ stack before switching stacks - x86/entry/64: Add unwind hint annotations - xen/x86: Remove SME feature in PV guests - x86/xen/64: Rearrange the SYSCALL entries - irq: Make the irqentry text section unconditional - x86/xen/64: Fix the reported SS and CS in SYSCALL - x86/paravirt/xen: Remove xen_patch() - x86/traps: Simplify pagefault tracing logic - x86/idt: Unify gate_struct handling for 32/64-bit kernels - x86/asm: Replace access to desc_struct:a/b fields - x86/xen: Get rid of paravirt op adjust_exception_frame - x86/paravirt: Remove no longer used paravirt functions - x86/entry: Fix idtentry unwind hint - x86/mm/64: Initialize CR4.PCIDE early - objtool: Add ORC unwind table generation - objtool, x86: Add facility for asm code to provide unwind hints - x86/unwind: Add the ORC unwinder - x86/kconfig: Consolidate unwinders into multiple choice selection - objtool: Upgrade libelf-devel warning to error for CONFIG_ORC_UNWINDER - x86/ldt/64: Refresh DS and ES when modify_ldt changes an entry - x86/mm: Give each mm TLB flush generation a unique ID - x86/mm: Track the TLB's tlb_gen and update the flushing algorithm - x86/mm: Rework lazy TLB mode and TLB freshness tracking - x86/mm: Implement PCID based optimization: try to preserve old TLB entries using PCID - x86/mm: Factor out CR3-building code - x86/mm/64: Stop using CR3.PCID == 0 in ASID-aware code - x86/mm: Flush more aggressively in lazy TLB mode - Revert "x86/mm: Stop calling leave_mm() in idle code" - kprobes/x86: Set up frame pointer in kprobe trampoline - x86/tracing: Introduce a static key for exception tracing - x86/boot: Add early cmdline parsing for options with arguments - mm, x86/mm: Fix performance regression in get_user_pages_fast() - x86/asm: Remove unnecessary \n\t in front of CC_SET() from asm templates - objtool: Don't report end of section error after an empty unwind hint - x86/head: Remove confusing comment - x86/head: Remove unused 'bad_address' code - x86/head: Fix head ELF function annotations - x86/boot: Annotate verify_cpu() as a callable function - x86/xen: Fix xen head ELF annotations - x86/xen: Add unwind hint annotations - x86/head: Add unwind hint annotations - ACPI / APEI: adjust a local variable type in ghes_ioremap_pfn_irq() - x86/unwinder: Make CONFIG_UNWINDER_ORC=y the default in the 64-bit defconfig - x86/fpu/debug: Remove unused 'x86_fpu_state' and 'x86_fpu_deactivate_state' tracepoints - x86/unwind: Rename unwinder config options to 'CONFIG_UNWINDER_*' - x86/unwind: Make CONFIG_UNWINDER_ORC=y the default in kconfig for 64-bit - bitops: Add clear/set_bit32() to linux/bitops.h - x86/cpuid: Add generic table for CPUID dependencies - x86/fpu: Parse clearcpuid= as early XSAVE argument - x86/fpu: Make XSAVE check the base CPUID features before enabling - x86/fpu: Remove the explicit clearing of XSAVE dependent features - x86/platform/UV: Convert timers to use timer_setup() - objtool: Print top level commands on incorrect usage - x86/cpuid: Prevent out of bound access in do_clear_cpu_cap() - x86/entry: Use SYSCALL_DEFINE() macros for sys_modify_ldt() - mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y - x86/kasan: Use the same shadow offset for 4- and 5-level paging - x86/xen: Provide pre-built page tables only for CONFIG_XEN_PV=y and CONFIG_XEN_PVH=y - x86/xen: Drop 5-level paging support code from the XEN_PV code - ACPI / APEI: remove the unused dead-code for SEA/NMI notification type - x86/asm: Don't use the confusing '.ifeq' directive - x86/build: Beautify build log of syscall headers - x86/mm/64: Rename the register_page_bootmem_memmap() 'size' parameter to 'nr_pages' - x86/cpufeatures: Enable new SSE/AVX/AVX512 CPU features - x86/mm: Relocate page fault error codes to traps.h - x86/boot: Relocate definition of the initia
[Group.of.nepali.translators] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
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 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
[Group.of.nepali.translators] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
This bug was fixed in the package linux - 4.13.0-19.22
---
linux (4.13.0-19.22) artful; urgency=low
* linux: 4.13.0-19.22 -proposed tracker (LP: #1736118)
* CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()
linux (4.13.0-18.21) artful; urgency=low
* linux: 4.13.0-18.21 -proposed tracker (LP: #1733530)
* NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type
* CPU call trace on AMD Raven Ridge after S3 (LP: #1732894)
- x86/mce/AMD: Allow any CPU to initialize the smca_banks array
* 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
* enable CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH easily confuse users
(LP: #1732627)
- [Config] CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH=n
* Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610
* Allow drivers to use Relaxed Ordering on capable root ports (LP: #1721365)
- Revert commit 1a8b6d76dc5b ("net:add one common config...")
- net: ixgbe: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag
* support GICv3 ITS save/restore & migration (LP: #1710019)
- KVM: arm/arm64: vgic-its: Fix return value for device table restore
* Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi
* Artful update to 4.13.13 stable release (LP: #1732726)
- netfilter: nat: Revert "netfilter: nat: convert nat bysrc hash to
rhashtable"
- netfilter: nft_set_hash: disable fast_ops for 2-len keys
- workqueue: Fix NULL pointer dereference
- crypto: ccm - preserve the IV buffer
- crypto: x86/sha1-mb - fix panic due to unaligned access
- crypto: x86/sha256-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ACPI / PM: Blacklist Low Power S0 Idle _DSM for Dell XPS13 9360
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: timer: Limit max instances per timer
- ALSA: usb-audio: support new Amanero Combo384 firmware version
- ALSA: hda - fix headset mic problem for Dell machines with alc274
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: Fix CM region target definitions
- MIPS: BMIPS: Fix missing cbr address
- MIPS: AR7: Defer registration of GPIO
- MIPS: AR7: Ensure that serial ports are properly set up
- KVM: PPC: Book3S HV: Fix exclusion between HPT resizing and other HPT
updates
- Input: elan_i2c - add ELAN060C to the ACPI table
- rbd: use GFP_NOIO for parent stat and data requests
- drm/vmwgfx: Fix Ubuntu 17.10 Wayland black screen issue
- Revert "x86: CPU: Fix up "cpu MHz" in /proc/cpuinfo"
- can: sun4i: handle overrun in RX FIFO
- can: peak: Add support for new PCIe/M2 CAN FD interfaces
- can: ifi: Fix transmitter delay calculation
- can: c_can: don't indicate triple sampling support for D_CAN
- x86/debug: Handle warnings before the notifier chain, to fix KGDB crash
- x86/smpboot: Make optimization of delay calibration work correctly
- x86/oprofile/ppro: Do not use __this_cpu*() in preemptible context
- Linux 4.13.13
* ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh
install (LP: #1727544)
- Input: elan_i2c - add ELAN060C to the ACPI table
* Power8 Nest PMU Instrumentation support (LP: #1481347)
- powerpc/powernv: Add IMC OPAL APIs
- powerpc/powernv: Detect and create IMC device
- powerpc/perf: Add nest IMC PMU support
- powerpc/perf: Add core IMC PMU support
- powerpc/perf: Add thread IMC PMU support
- powerpc/perf: Fix double unlock in imc_common_cpuhp_mem_free()
- powerpc/perf/imc: Fix nest events on muti socket system
- powerpc/powernv: Fix build error in opal-imc.c when NUMA=n
- powerpc/perf: Fix usage of nest_imc_refc
- powerpc/perf: Fix for core/nest imc call trace on cpuhotplug
- powerpc/perf: Add ___GFP_NOWARN flag to alloc_pages_node()
- powerpc/perf: Fix IMC initialization crash
* Artful update to 4.13.12 stable release (LP: #1731971)
- ALSA: timer: Add missing mutex lock for compat ioctls
- ALSA: seq: Fix nested rwsem annotation for lockdep splat
- cifs: check MaxPathNameComponentLength != 0 before using it
- KEYS: return full count in keyring_read() if buffer is too small
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- KEYS: fix out-of-bounds read during ASN.1 parsing
- ASoC: adau17x1: Workaround for noise bug in ADC
- virtio_blk: Fix an SG_IO regression
- arm64: ensure __dump_instr() checks addr_limit
[Group.of.nepali.translators] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Artful) Status: New => Fix Committed ** Changed in: linux (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Zesty) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Committed -- 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: Incomplete Status in bluez source package in Xenial: New Status in linux source package in Xenial: Fix Committed Status in bluez source package in Zesty: New Status in linux source package in Zesty: Fix Committed Status in bluez source package in Artful: New Status in linux source package in Artful: Fix Committed 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
[Group.of.nepali.translators] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Xenial) Importance: Undecided Status: New -- 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: Incomplete Status in bluez source package in Xenial: New Status in linux source package in Xenial: New 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
