[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
** Tags added: cscc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
This bug was fixed in the package linux-snapdragon - 4.15.0-1053.57 --- linux-snapdragon (4.15.0-1053.57) bionic; urgency=medium [ Ubuntu: 4.15.0-50.54 ] * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130 - Documentation/l1tf: Fix small spelling typo - x86/cpu: Sanitize FAM6_ATOM naming - kvm: x86: Report STIBP on GET_SUPPORTED_CPUID - locking/atomics, asm-generic: Move some macros from to a new file - tools include: Adopt linux/bits.h - x86/msr-index: Cleanup bit defines - x86/speculation: Consolidate CPU whitelists - x86/speculation/mds: Add basic bug infrastructure for MDS - x86/speculation/mds: Add BUG_MSBDS_ONLY - x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests - x86/speculation/mds: Add mds_clear_cpu_buffers() - x86/speculation/mds: Clear CPU buffers on exit to user - x86/kvm/vmx: Add MDS protection when L1D Flush is not active - x86/speculation/mds: Conditionally clear CPU buffers on idle entry - x86/speculation/mds: Add mitigation control for MDS - x86/speculation/mds: Add sysfs reporting for MDS - x86/speculation/mds: Add mitigation mode VMWERV - Documentation: Move L1TF to separate directory - Documentation: Add MDS vulnerability documentation - x86/speculation/mds: Add mds=full,nosmt cmdline option - x86/speculation: Move arch_smt_update() call to after mitigation decisions - x86/speculation/mds: Add SMT warning message - x86/speculation/mds: Fix comment - x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off - x86/speculation/mds: Add 'mitigations=' support for MDS * CVE-2017-5715 // CVE-2017-5753 - s390/speculation: Support 'mitigations=' cmdline option * CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639 - powerpc/speculation: Support 'mitigations=' cmdline option * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 // CVE-2018-3646 - cpu/speculation: Add 'mitigations=' cmdline option - x86/speculation: Support 'mitigations=' cmdline option * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log [ Ubuntu: 4.15.0-49.53 ] * linux: 4.15.0-49.53 -proposed tracker (LP: #1826358) * bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868) - [Packaging] arm64: Drop snapdragon from kernel-versions linux-snapdragon (4.15.0-1052.56) bionic; urgency=medium * linux-snapdragon: 4.15.0-1052.56 -proposed tracker (LP: #1826335) * bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868) - packaging: fix debian control vars for snapdragon * Packaging resync (LP: #1786013) - [Packaging] update update.conf [ Ubuntu: 4.15.0-49.52 ] * linux: 4.15.0-49.52 -proposed tracker (LP: #1826358) * Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3) (LP: #1822870) - powerpc/64s: Add support for ori barrier_nospec patching - powerpc/64s: Patch barrier_nospec in modules - powerpc/64s: Enable barrier_nospec based on firmware settings - powerpc: Use barrier_nospec in copy_from_user() - powerpc/64: Use barrier_nospec in syscall entry - powerpc/64s: Enhance the information in cpu_show_spectre_v1() - powerpc/64: Disable the speculation barrier from the command line - powerpc/64: Make stf barrier PPC_BOOK3S_64 specific. - powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC - powerpc/64: Call setup_barrier_nospec() from setup_arch() - powerpc/64: Make meltdown reporting Book3S 64 specific - powerpc/lib/code-patching: refactor patch_instruction() - powerpc/lib/feature-fixups: use raw_patch_instruction() - powerpc/asm: Add a patch_site macro & helpers for patching instructions - powerpc/64s: Add new security feature flags for count cache flush - powerpc/64s: Add support for software count cache flush - powerpc/pseries: Query hypervisor for count cache flush settings - powerpc/powernv: Query firmware for count cache flush settings - powerpc/fsl: Add nospectre_v2 command line argument - KVM: PPC: Book3S: Add count cache flush parameters to kvmppc_get_cpu_char() - [Config] Add CONFIG_PPC_BARRIER_NOSPEC * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log * autopkgtests run too often, too much and don't skip enough (LP: #1823056) - [Debian] Set +x on rebuild testcase. - [Debian] Skip rebuild test, for regression-suite deps. - [Debian] Make ubuntu-regression-suite skippable on unbootable kernels. - [Debian] make rebuild use skippable error codes when skipping. - [Debian] Only run regression-suite, if requested to. * bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868) - [Packaging] remove arm64 snapdragon from getabis - [Config] config changes for snapdragon split - packaging: arm64: disable building the snapdragon flavour * CVE-2017-5753
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
This bug was fixed in the package linux - 4.18.0-16.17 --- linux (4.18.0-16.17) cosmic; urgency=medium * linux: 4.18.0-16.17 -proposed tracker (LP: #1814749) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2018-16880 - vhost: fix OOB in get_rx_bufs() * RTL8822BE WiFi Disabled in Kernel 4.18.0-12 (LP: #1806472) - SAUCE: staging: rtlwifi: allow RTLWIFI_DEBUG_ST to be disabled - [Config] CONFIG_RTLWIFI_DEBUG_ST=n - SAUCE: Add r8822be to signature inclusion list * kernel oops in bcache module (LP: #1793901) - SAUCE: bcache: never writeback a discard operation * CVE-2018-18397 - userfaultfd: use ENOENT instead of EFAULT if the atomic copy user fails - userfaultfd: shmem: allocate anonymous memory for MAP_PRIVATE shmem - userfaultfd: shmem/hugetlbfs: only allow to register VM_MAYWRITE vmas - userfaultfd: shmem: add i_size checks - userfaultfd: shmem: UFFDIO_COPY: set the page dirty if VM_WRITE is not set * Ignore "incomplete report" from Elan touchpanels (LP: #1813733) - HID: i2c-hid: Ignore input report if there's no data present on Elan touchpanels * Vsock connect fails with ENODEV for large CID (LP: #1813934) - vhost/vsock: fix vhost vsock cid hashing inconsistent * Fix non-working pinctrl-intel (LP: #1811777) - pinctrl: intel: Do pin translation in other GPIO operations as well * ip6_gre: fix tunnel list corruption for x-netns (LP: #1812875) - ip6_gre: fix tunnel list corruption for x-netns * Backported commit breaks audio (fixed upstream) (LP: #1811566) - ASoC: intel: cht_bsw_max98090_ti: Add quirk for boards using pmc_plt_clk_0 - ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Clapper - ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty * kvm_stat : missing python dependency (LP: #1798776) - tools/kvm_stat: switch to python3 * [SRU] Fix Xorg crash with nomodeset when BIOS enable 64-bit fb addr (LP: #1812797) - vgaarb: Add support for 64-bit frame buffer address - vgaarb: Keep adding VGA device in queue * Fix non-working QCA Rome Bluetooth after S3 (LP: #1812812) - USB: Add new USB LPM helpers - USB: Consolidate LPM checks to avoid enabling LPM twice * [SRU] IO's are issued with incorrect Scatter Gather Buffer (LP: #1795453) - scsi: megaraid_sas: Use 63-bit DMA addressing * x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a (LP: #1813532) - x86/mm: Do not warn about PCI BIOS W+X mappings * CVE-2019-6133 - fork: record start_time late * Fix not working Goodix touchpad (LP: #1811929) - HID: i2c-hid: Disable runtime PM on Goodix touchpad * bluetooth controller not detected with 4.15 kernel (LP: #1810797) - SAUCE: btqcomsmd: introduce BT_QCOMSMD_HACK - [Config] arm64: snapdragon: BT_QCOMSMD_HACK=y * X1 Extreme: only one of the two SSDs is loaded (LP: #1811755) - nvme-core: rework a NQN copying operation - nvme: pad fake subsys NQN vid and ssvid with zeros - nvme: introduce NVME_QUIRK_IGNORE_DEV_SUBNQN * Crash on "ip link add foo type ipip" (LP: #1811803) - SAUCE: fan: Fix NULL pointer dereference -- Stefan Bader Thu, 07 Feb 2019 23:23:02 +0100 ** Changed in: linux (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16880 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
This bug was fixed in the package linux - 4.15.0-46.49 --- linux (4.15.0-46.49) bionic; urgency=medium * linux: 4.15.0-46.49 -proposed tracker (LP: #1814726) * mprotect fails on ext4 with dax (LP: #1799237) - x86/speculation/l1tf: Exempt zeroed PTEs from inversion * kernel BUG at /build/linux-vxxS7y/linux-4.15.0/mm/slub.c:296! (LP: #1812086) - iscsi target: fix session creation failure handling - scsi: iscsi: target: Set conn->sess to NULL when iscsi_login_set_conn_values fails - scsi: iscsi: target: Fix conn_ops double free * user_copy in user from ubuntu_kernel_selftests failed on KVM kernel (LP: #1812198) - selftests: user: return Kselftest Skip code for skipped tests - selftests: kselftest: change KSFT_SKIP=4 instead of KSFT_PASS - selftests: kselftest: Remove outdated comment * RTL8822BE WiFi Disabled in Kernel 4.18.0-12 (LP: #1806472) - SAUCE: staging: rtlwifi: allow RTLWIFI_DEBUG_ST to be disabled - [Config] CONFIG_RTLWIFI_DEBUG_ST=n - SAUCE: Add r8822be to signature inclusion list * kernel oops in bcache module (LP: #1793901) - SAUCE: bcache: never writeback a discard operation * CVE-2018-18397 - userfaultfd: use ENOENT instead of EFAULT if the atomic copy user fails - userfaultfd: shmem: allocate anonymous memory for MAP_PRIVATE shmem - userfaultfd: shmem/hugetlbfs: only allow to register VM_MAYWRITE vmas - userfaultfd: shmem: add i_size checks - userfaultfd: shmem: UFFDIO_COPY: set the page dirty if VM_WRITE is not set * Ignore "incomplete report" from Elan touchpanels (LP: #1813733) - HID: i2c-hid: Ignore input report if there's no data present on Elan touchpanels * Vsock connect fails with ENODEV for large CID (LP: #1813934) - vhost/vsock: fix vhost vsock cid hashing inconsistent * SRU: Fix thinkpad 11e 3rd boot hang (LP: #1804604) - ACPI / LPSS: Force LPSS quirks on boot * Bionic update: upstream stable patchset 2019-01-17 (LP: #1812229) - scsi: sd_zbc: Fix variable type and bogus comment - KVM/Eventfd: Avoid crash when assign and deassign specific eventfd in parallel. - x86/apm: Don't access __preempt_count with zeroed fs - x86/events/intel/ds: Fix bts_interrupt_threshold alignment - x86/MCE: Remove min interval polling limitation - fat: fix memory allocation failure handling of match_strdup() - ALSA: hda/realtek - Add Panasonic CF-SZ6 headset jack quirk - ARCv2: [plat-hsdk]: Save accl reg pair by default - ARC: Fix CONFIG_SWAP - ARC: configs: Remove CONFIG_INITRAMFS_SOURCE from defconfigs - ARC: mm: allow mprotect to make stack mappings executable - mm: memcg: fix use after free in mem_cgroup_iter() - mm/huge_memory.c: fix data loss when splitting a file pmd - cpufreq: intel_pstate: Register when ACPI PCCH is present - vfio/pci: Fix potential Spectre v1 - stop_machine: Disable preemption when waking two stopper threads - drm/i915: Fix hotplug irq ack on i965/g4x - drm/nouveau: Use drm_connector_list_iter_* for iterating connectors - drm/nouveau: Avoid looping through fake MST connectors - gen_stats: Fix netlink stats dumping in the presence of padding - ipv4: Return EINVAL when ping_group_range sysctl doesn't map to user ns - ipv6: fix useless rol32 call on hash - ipv6: ila: select CONFIG_DST_CACHE - lib/rhashtable: consider param->min_size when setting initial table size - net: diag: Don't double-free TCP_NEW_SYN_RECV sockets in tcp_abort - net: Don't copy pfmemalloc flag in __copy_skb_header() - skbuff: Unconditionally copy pfmemalloc in __skb_clone() - net/ipv4: Set oif in fib_compute_spec_dst - net: phy: fix flag masking in __set_phy_supported - ptp: fix missing break in switch - qmi_wwan: add support for Quectel EG91 - tg3: Add higher cpu clock for 5762. - hv_netvsc: Fix napi reschedule while receive completion is busy - net/mlx4_en: Don't reuse RX page when XDP is set - net: systemport: Fix CRC forwarding check for SYSTEMPORT Lite - ipv6: make DAD fail with enhanced DAD when nonce length differs - net: usb: asix: replace mii_nway_restart in resume path - alpha: fix osf_wait4() breakage - cxl_getfile(): fix double-iput() on alloc_file() failures - powerpc/powernv: Fix save/restore of SPRG3 on entry/exit from stop (idle) - xhci: Fix perceived dead host due to runtime suspend race with event handler - KVM: irqfd: fix race between EPOLLHUP and irq_bypass_register_consumer - x86/kvmclock: set pvti_cpu0_va after enabling kvmclock - ALSA: hda/realtek - Yet another Clevo P950 quirk entry - drm/amdgpu: Reserve VM root shared fence slot for command submission (v3) - rhashtable: add restart routine in rhashtable_free_and_destroy() - sch_fq_codel: zero q->flows_cnt when fq_codel_init fails - sctp: introduce sctp_dst_mtu - sctp: fix the issue that pathmtu may be
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
This passes for me on 4.15.0-46.49 - (rev 82) kernel snap that is currently in candidate ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
I think we're waiting on a snap of this for testing. We already tested and confirmed it worked on a snap that ppisati built (see comment #6 and comment #8). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
This bug was fixed in the package linux - 4.19.0-12.13
---
linux (4.19.0-12.13) disco; urgency=medium
* linux: 4.19.0-12.13 -proposed tracker (LP: #1813664)
* kernel oops in bcache module (LP: #1793901)
- SAUCE: bcache: never writeback a discard operation
* Disco update: 4.19.18 upstream stable release (LP: #1813611)
- ipv6: Consider sk_bound_dev_if when binding a socket to a v4 mapped
address
- mlxsw: spectrum: Disable lag port TX before removing it
- mlxsw: spectrum_switchdev: Set PVID correctly during VLAN deletion
- net: dsa: mv88x6xxx: mv88e6390 errata
- net, skbuff: do not prefer skb allocation fails early
- qmi_wwan: add MTU default to qmap network interface
- ipv6: Take rcu_read_lock in __inet6_bind for mapped addresses
- net: clear skb->tstamp in bridge forwarding path
- netfilter: ipset: Allow matching on destination MAC address for mac and
ipmac sets
- gpio: pl061: Move irq_chip definition inside struct pl061
- drm/amd/display: Guard against null stream_state in set_crc_source
- drm/amdkfd: fix interrupt spin lock
- ixgbe: allow IPsec Tx offload in VEPA mode
- platform/x86: asus-wmi: Tell the EC the OS will handle the display off
hotkey
- e1000e: allow non-monotonic SYSTIM readings
- usb: typec: tcpm: Do not disconnect link for self powered devices
- selftests/bpf: enable (uncomment) all tests in test_libbpf.sh
- of: overlay: add missing of_node_put() after add new node to changeset
- writeback: don't decrement wb->refcnt if !wb->bdi
- serial: set suppress_bind_attrs flag only if builtin
- bpf: Allow narrow loads with offset > 0
- ALSA: oxfw: add support for APOGEE duet FireWire
- x86/mce: Fix -Wmissing-prototypes warnings
- MIPS: SiByte: Enable swiotlb for SWARM, LittleSur and BigSur
- crypto: ecc - regularize scalar for scalar multiplication
- arm64: perf: set suppress_bind_attrs flag to true
- drm/atomic-helper: Complete fake_commit->flip_done potentially earlier
- clk: meson: meson8b: fix incorrect divider mapping in cpu_scale_table
- samples: bpf: fix: error handling regarding kprobe_events
- usb: gadget: udc: renesas_usb3: add a safety connection way for
forced_b_device
- fpga: altera-cvp: fix probing for multiple FPGAs on the bus
- selinux: always allow mounting submounts
- ASoC: pcm3168a: Don't disable pcm3168a when CONFIG_PM defined
- scsi: qedi: Check for session online before getting iSCSI TLV data.
- drm/amdgpu: Reorder uvd ring init before uvd resume
- rxe: IB_WR_REG_MR does not capture MR's iova field
- efi/libstub: Disable some warnings for x86{,_64}
- jffs2: Fix use of uninitialized delayed_work, lockdep breakage
- clk: imx: make mux parent strings const
- pstore/ram: Do not treat empty buffers as valid
- media: uvcvideo: Refactor teardown of uvc on USB disconnect
- powerpc/xmon: Fix invocation inside lock region
- powerpc/pseries/cpuidle: Fix preempt warning
- media: firewire: Fix app_info parameter type in avc_ca{,_app}_info
- ASoC: use dma_ops of parent device for acp_audio_dma
- media: venus: core: Set dma maximum segment size
- staging: erofs: fix use-after-free of on-stack `z_erofs_vle_unzip_io'
- net: call sk_dst_reset when set SO_DONTROUTE
- scsi: target: use consistent left-aligned ASCII INQUIRY data
- scsi: target/core: Make sure that target_wait_for_sess_cmds() waits long
enough
- selftests: do not macro-expand failed assertion expressions
- arm64: kasan: Increase stack size for KASAN_EXTRA
- clk: imx6q: reset exclusive gates on init
- arm64: Fix minor issues with the dcache_by_line_op macro
- bpf: relax verifier restriction on BPF_MOV | BPF_ALU
- kconfig: fix file name and line number of warn_ignored_character()
- kconfig: fix memory leak when EOF is encountered in quotation
- mmc: atmel-mci: do not assume idle after atmci_request_end
- btrfs: volumes: Make sure there is no overlap of dev extents at mount time
- btrfs: alloc_chunk: fix more DUP stripe size handling
- btrfs: fix use-after-free due to race between replace start and cancel
- btrfs: improve error handling of btrfs_add_link
- tty/serial: do not free trasnmit buffer page under port lock
- perf intel-pt: Fix error with config term "pt=0"
- perf tests ARM: Disable breakpoint tests 32-bit
- perf svghelper: Fix unchecked usage of strncpy()
- perf parse-events: Fix unchecked usage of strncpy()
- perf vendor events intel: Fix Load_Miss_Real_Latency on SKL/SKX
- netfilter: ipt_CLUSTERIP: check MAC address when duplicate config is set
- netfilter: ipt_CLUSTERIP: remove wrong WARN_ON_ONCE in netns exit routine
- netfilter: ipt_CLUSTERIP: fix deadlock in netns exit routine
- x86/topology: Use total_cpus for max logical packages calculation
- dm crypt: use u64 instead of sector_t
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-snapdragon (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Committed ** Changed in: linux-snapdragon (Ubuntu Cosmic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
I built an image with this kernel snap added to extra-snaps, and it seems to find it now: ubuntu@localhost:~$ sudo bluetoothctl [NEW] Controller 00:00:00:00:5A:AD BlueZ 5.47 [default] Agent registered -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-snapdragon (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-snapdragon (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
@Paolo Is it possible to push this to edge or some other track? I'm having trouble sideloading a kernel snap with --dangerous. I get the following error: ubuntu@localhost:~$ sudo snap install ./dragonboard-kernel_4.15.0-43.46_lp1810797_arm64.snap --dangerous error: cannot perform the following tasks: - Mount snap "dragonboard-kernel" (unset) (cannot replace signed kernel snap with an unasserted one) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
And here is a kernel snap for testing: http://people.canonical.com/~ppisati/lp1810797/dragonboard- kernel_4.15.0-43.46~lp1810797_arm64.snap hcitool has a problem accessing hci0 on Ubuntu core (at least, in my tests), use bluetoothctl instead: p-pisati@localhost:~$ sudo bluetoothctl [NEW] Controller 00:00:00:00:5A:AD localhost.localdomain [default] Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# power on [CHG] Controller 00:00:00:00:5A:AD Class: 0x0010 Changing power on succeeded [CHG] Controller 00:00:00:00:5A:AD Powered: yes [bluetooth]# scan on Discovery started [CHG] Controller 00:00:00:00:5A:AD Discovering: yes ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
** Description changed:
Impact:
Upon boot, no hci device is available to userspace, thus bluetooth
communication is not possible.
Defect analysis:
The root of the problem lies in these two patches:
$ git log --online drivers/bluetooth/btqcomsmd.c
...
766154b Bluetooth: btqcomsmd: retrieve BD address from DT property
6e51811 Bluetooth: btqcomsmd: Add support for BD address setup
...
Qualcomm engineer found that btqcomsmd had no BD address burned in (nor
via ROM, neither internally) and it was always coming up with the same
address, probably derived from manufacturer ID and / or chip ID.
To fix this, they pushed the burden of generating a unique per-board BD
address to the Qualcomm bootloader and make it pass down via DTB to the
live kernel - and if no address was present in the DTB, the hci was left
unconfigured.
Fix:
So *technically* speaking, the kernel is correct in this case, it's our
dragonboard image (e.g. Ubuntu Core) that doesn't extract the generated
BD address from the Qualcomm bootloader and pass it down to the kernel.
On the other hand, having Bluetooth working out of the box (even with a
dummy address), is a nice feature to have, so i slightly modified
Qualcomm's code introduced in the two above patches, and made the lack
- of DB address in DTB non fatal:
-
- if DTB_has_BD_address()
- read_BD_addr_and_apply_it()
- else
- default_back_to_dummy_addr()
- end if
+ of DB address in DTB non fatal.
And surrounded the modification in #ifdef...#endif brackets to keep it
local.
How to test:
By default, on a patched kernel, the hci device will have a default
address:
ubuntu@dragon410c:~$ hcitool dev
Devices:
- hci000:00:00:00:5A:AD
+ hci000:00:00:00:5A:AD
the address " 00:00:00:00:5A:AD" might vary per board, but will be
consistent after every reboot.
- The other option is to specify a custom address via dtb, e.g. using uboot to
manipulate the dtb - we assume the dtb ws loaded in memory at ${fdt_addr}:
-
+ The other option is to specify a custom address via dtb, e.g. using
+ uboot to manipulate the dtb - we assume the dtb ws loaded in memory at
+ ${fdt_addr}:
+
dragonboard410c => fdt addr ${fdt_addr}
dragonboard410c => fdt print /soc/wcnss/smd-edge/wcnss/bt/
bt {
- compatible = "qcom,wcnss-bt";
+ compatible = "qcom,wcnss-bt";
};
dragonboard410c => fdt resize
dragonboard410c => fdt set /soc/wcnss/smd-edge/wcnss/bt/ local-bd-
address [ 55 44 33 22 11 00 ]
- dragonboard410c => fdt print /soc/wcnss/smd-edge/wcnss/bt/
+ dragonboard410c => fdt print /soc/wcnss/smd-edge/wcnss/bt/
bt {
- local-bd-address = [55 44 33 22 11 00];
- compatible = "qcom,wcnss-bt";
+ local-bd-address = [55 44 33 22 11 00];
+ compatible = "qcom,wcnss-bt";
};
then proceed with the rest of the boot process and check hci:
$ hcitool dev
Devices:
- hci000:11:22:33:44:55
+ hci000:11:22:33:44:55
In both cases, blueooth work afterward, and can be used to communicate
with other devices:
ubuntu@dragon410c:~$ hcitool scan
Scanning ...
- C0:BD:54:12:4E:D1 My dummy device
-
+ C0:BD:54:12:4E:D1 My dummy device
Regression potential:
None, the fix is surronded with #ifdef...#endif thus it doesn't exist
outside of it.
--
-
Using the core18 image from
http://cdimage.ubuntu.com/ubuntu-core/18/stable/current/
Kernel snap: 4.15.0-39.42 (72)
rfkill shows there is an hci0 device:
$ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
But bluetoothctl does not detect any controller:
$ sudo bluetoothctl
08:58 Agent registered
08:58 [bluetooth]# list
[...no output...]
If you revert to the 4.4 kernel [4.4.0-1106.111 (76)] it works:
$ sudo bluetoothctl
[NEW] Controller 00:00:00:00:5A:AD BlueZ 5.47 [default]
Agent registered
[bluetooth]# list
Controller 00:00:00:00:5A:AD BlueZ 5.47 [default]
[bluetooth]# show
Controller 00:00:00:00:5A:AD
Name: BlueZ 5.47
Alias: BlueZ 5.47
Class: 0x
Powered: no
Discoverable: no
Pairable: yes
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb)
UUID: PnP Information (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
UUID: Vendor specific
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
** Patch added: "0002-UBUNTU-Config-arm64-snapdragon-BT_QCOMSMD_HACK-y.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+attachment/5229696/+files/0002-UBUNTU-Config-arm64-snapdragon-BT_QCOMSMD_HACK-y.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-snapdragon (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
** Patch added: "0002-UBUNTU-Config-arm64-snapdragon-BT_QCOMSMD_HACK-y.patch" https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1810797/+attachment/5229615/+files/0002-UBUNTU-Config-arm64-snapdragon-BT_QCOMSMD_HACK-y.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
** Patch added: "0001-UBUNTU-SAUCE-btqcomsmd-introduce-BT_QCOMSMD_HACK.patch" https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1810797/+attachment/5229614/+files/0001-UBUNTU-SAUCE-btqcomsmd-introduce-BT_QCOMSMD_HACK.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810797 Title: bluetooth controller not detected with 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1810797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
** Description changed:
+ Impact:
+
+ Upon boot, no hci device is available to userspace, thus bluetooth
+ communication is not possible.
+
+ Defect analysis:
+
+ The root of the problem lies in these two patches:
+
+ $ git log --online drivers/bluetooth/btqcomsmd.c
+
+ ...
+ 766154b Bluetooth: btqcomsmd: retrieve BD address from DT property
+ 6e51811 Bluetooth: btqcomsmd: Add support for BD address setup
+ ...
+
+ Qualcomm engineer found that btqcomsmd had no BD address burned in (nor
+ via ROM, neither internally) and it was always coming up with the same
+ address, probably derived from manufacturer ID and / or chip ID.
+
+ To fix this, they pushed the burden of generating a unique per-board BD
+ address to the Qualcomm bootloader and make it pass down via DTB to the
+ live kernel - and if no address was present in the DTB, the hci was left
+ unconfigured.
+
+ Fix:
+
+ So *technically* speaking, the kernel is correct in this case, it's our
+ dragonboard image (e.g. Ubuntu Core) that doesn't extract the generated
+ BD address from the Qualcomm bootloader and pass it down to the kernel.
+
+ On the other hand, having Bluetooth working out of the box (even with a
+ dummy address), is a nice feature to have, so i slightly modified
+ Qualcomm's code introduced in the two above patches, and made the lack
+ of DB address in DTB non fatal:
+
+ if DTB_has_BD_address()
+ read_BD_addr_and_apply_it()
+ else
+ default_back_to_dummy_addr()
+ end if
+
+ And surrounded the modification in #ifdef...#endif brackets to keep it
+ local.
+
+ How to test:
+
+ By default, on a patched kernel, the hci device will have a default
+ address:
+
+ ubuntu@dragon410c:~$ hcitool dev
+ Devices:
+ hci000:00:00:00:5A:AD
+
+ the address " 00:00:00:00:5A:AD" might vary per board, but will be
+ consistent after every reboot.
+
+ The other option is to specify a custom address via dtb, e.g. using uboot to
manipulate the dtb - we assume the dtb ws loaded in memory at ${fdt_addr}:
+
+ dragonboard410c => fdt addr ${fdt_addr}
+
+ dragonboard410c => fdt print /soc/wcnss/smd-edge/wcnss/bt/
+ bt {
+ compatible = "qcom,wcnss-bt";
+ };
+
+ dragonboard410c => fdt resize
+
+ dragonboard410c => fdt set /soc/wcnss/smd-edge/wcnss/bt/ local-bd-
+ address [ 55 44 33 22 11 00 ]
+
+ dragonboard410c => fdt print /soc/wcnss/smd-edge/wcnss/bt/
+ bt {
+ local-bd-address = [55 44 33 22 11 00];
+ compatible = "qcom,wcnss-bt";
+ };
+
+ then proceed with the rest of the boot process and check hci:
+
+ $ hcitool dev
+ Devices:
+ hci000:11:22:33:44:55
+
+ In both cases, blueooth work afterward, and can be used to communicate
+ with other devices:
+
+ ubuntu@dragon410c:~$ hcitool scan
+ Scanning ...
+ C0:BD:54:12:4E:D1 My dummy device
+
+
+ Regression potential:
+
+ None, the fix is surronded with #ifdef...#endif thus it doesn't exist
+ outside of it.
+
+ --
+
+
Using the core18 image from
http://cdimage.ubuntu.com/ubuntu-core/18/stable/current/
Kernel snap: 4.15.0-39.42 (72)
rfkill shows there is an hci0 device:
$ rfkill list
0: hci0: Bluetooth
- Soft blocked: no
- Hard blocked: no
+ Soft blocked: no
+ Hard blocked: no
1: phy0: Wireless LAN
- Soft blocked: no
- Hard blocked: no
+ Soft blocked: no
+ Hard blocked: no
But bluetoothctl does not detect any controller:
$ sudo bluetoothctl
08:58 Agent registered
08:58 [bluetooth]# list
[...no output...]
If you revert to the 4.4 kernel [4.4.0-1106.111 (76)] it works:
$ sudo bluetoothctl
[NEW] Controller 00:00:00:00:5A:AD BlueZ 5.47 [default]
Agent registered
[bluetooth]# list
Controller 00:00:00:00:5A:AD BlueZ 5.47 [default]
[bluetooth]# show
Controller 00:00:00:00:5A:AD
- Name: BlueZ 5.47
- Alias: BlueZ 5.47
- Class: 0x
- Powered: no
- Discoverable: no
- Pairable: yes
- UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
- UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
- UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
- UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
- UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb)
- UUID: PnP Information (1200--1000-8000-00805f9b34fb)
- UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
- UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
- UUID: Vendor specific (5005--1000-8000-0002ee01)
- UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
- UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb)
- UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
- Modalias: usb:v1D6Bp0246d052F
- Discovering: no
+ Name:
