[Kernel-packages] [Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize
Well, there are some refactoring for btbcm.c in latest mainline kernel, so might worth a try. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1483101 Title: Broadcom bluetooth modules sometimes fail to initialize Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This message can be found in dmesg: [ 15.080247] Bluetooth: hci0 command 0x1001 tx timeout Currently known affected modules: * 0a5c:216a * 0a5c:6410 * 0a5c:6412 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1483101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize
@wenchien: Ok, thank you for the info. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1483101 Title: Broadcom bluetooth modules sometimes fail to initialize Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This message can be found in dmesg: [ 15.080247] Bluetooth: hci0 command 0x1001 tx timeout Currently known affected modules: * 0a5c:216a * 0a5c:6410 * 0a5c:6412 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1483101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize
@jason108: This patch has been landed in upstream since 4.11, so, yes, we have it in bionic. >From the log in askubuntu, there's a line: "[ 31.964068] Bluetooth: hci0: BCM: Patch command 0a0a failed (-110)" This indicates that something goes wrong when the driver is sending firmware to the module. It is different from the bug we have here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1483101 Title: Broadcom bluetooth modules sometimes fail to initialize Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This message can be found in dmesg: [ 15.080247] Bluetooth: hci0 command 0x1001 tx timeout Currently known affected modules: * 0a5c:216a * 0a5c:6410 * 0a5c:6412 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1483101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize
The error message appears again in Ubuntu 18.04, kernel 4.15.0-22-generic, with module 0a5c:216c. I already posted this on https://askubuntu.com/questions/1043171/broadcom-bcm43242a0-bluetooth-adapter-not-detected-in-ubuntu-18-04 Is it possible that the fix got lost in a newer kernel version? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1483101 Title: Broadcom bluetooth modules sometimes fail to initialize Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This message can be found in dmesg: [ 15.080247] Bluetooth: hci0 command 0x1001 tx timeout Currently known affected modules: * 0a5c:216a * 0a5c:6410 * 0a5c:6412 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1483101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize
** Changed in: hwe-next Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1483101 Title: Broadcom bluetooth modules sometimes fail to initialize Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This message can be found in dmesg: [ 15.080247] Bluetooth: hci0 command 0x1001 tx timeout Currently known affected modules: * 0a5c:216a * 0a5c:6410 * 0a5c:6412 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1483101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize
** Tags removed: verification-needed-xenial verification-needed-yakkety ** Tags added: verification-done-xenial verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1483101 Title: Broadcom bluetooth modules sometimes fail to initialize Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This message can be found in dmesg: [ 15.080247] Bluetooth: hci0 command 0x1001 tx timeout Currently known affected modules: * 0a5c:216a * 0a5c:6410 * 0a5c:6412 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1483101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize
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- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. 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-xenial ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1483101 Title: Broadcom bluetooth modules sometimes fail to initialize Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This message can be found in dmesg: [ 15.080247] Bluetooth: hci0 command 0x1001 tx timeout Currently known affected modules: * 0a5c:216a * 0a5c:6410 * 0a5c:6412 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1483101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize
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- yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed- yakkety'. 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! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1483101 Title: Broadcom bluetooth modules sometimes fail to initialize Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This message can be found in dmesg: [ 15.080247] Bluetooth: hci0 command 0x1001 tx timeout Currently known affected modules: * 0a5c:216a * 0a5c:6410 * 0a5c:6412 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1483101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize
This bug was fixed in the package linux - 4.10.0-14.16 --- linux (4.10.0-14.16) zesty; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1673805 * msleep() bug causes Nuvoton I2C TPM device driver delays (LP: #1667567) - tpm: msleep() delays - replace with usleep_range() in i2c nuvoton driver - SAUCE: tpm: add sleep only for retry in i2c_nuvoton_write_status() * C++ demangling support missing from perf (LP: #1396654) - [Config] added binutils-dev to Build-deps * dm-queue-length module is not included in installer/initramfs (LP: #1673350) - [Config] d-i: Also add dm-queue-length to multipath modules * move aufs.ko from -extra to linux-image package (LP: #1673498) - [config] aufs.ko moved to linux-image package * Using an NVMe drive causes huge power drain (LP: #1664602) - nvme: Add a quirk mechanism that uses identify_ctrl - nvme: Enable autonomous power state transitions * Broadcom bluetooth modules sometimes fail to initialize (LP: #1483101) - Bluetooth: btbcm: Add a delay for module reset * Need support of Broadcom bluetooth device [413c:8143] (LP: #1166113) - Bluetooth: btusb: Add support for 413c:8143 * Zesty update to v4.10.3 stable release (LP: #1673118) - serial: 8250_pci: Add MKS Tenta SCOM-0800 and SCOM-0801 cards - KVM: s390: Disable dirty log retrieval for UCONTROL guests - KVM: VMX: use correct vmcs_read/write for guest segment selector/base - Bluetooth: Add another AR3012 04ca:3018 device - phy: qcom-ufs: Don't kfree devres resource - phy: qcom-ufs: Fix misplaced jump label - s390/qdio: clear DSCI prior to scanning multiple input queues - s390/dcssblk: fix device size calculation in dcssblk_direct_access() - s390/kdump: Use "LINUX" ELF note name instead of "CORE" - s390/chsc: Add exception handler for CHSC instruction - s390: TASK_SIZE for kernel threads - s390/topology: correct allocation of topology information - s390: make setup_randomness work - s390: use correct input data address for setup_randomness - net: mvpp2: fix DMA address calculation in mvpp2_txq_inc_put() - cxl: Prevent read/write to AFU config space while AFU not configured - cxl: fix nested locking hang during EEH hotplug - brcmfmac: fix incorrect event channel deduction - mnt: Tuck mounts under others instead of creating shadow/side mounts. - IB/ipoib: Fix deadlock between rmmod and set_mode - IB/IPoIB: Add destination address when re-queue packet - IB/mlx5: Fix out-of-bound access - IB/SRP: Avoid using IB_MR_TYPE_SG_GAPS - IB/srp: Avoid that duplicate responses trigger a kernel bug - IB/srp: Fix race conditions related to task management - Btrfs: fix data loss after truncate when using the no-holes feature - orangefs: Use RCU for destroy_inode - memory/atmel-ebi: Fix ns <-> cycles conversions - tracing: Fix return value check in trace_benchmark_reg() - ktest: Fix child exit code processing - ceph: remove req from unsafe list when unregistering it - target: Fix NULL dereference during LUN lookup + active I/O shutdown - drivers/pci/hotplug: Handle presence detection change properly - drivers/pci/hotplug: Fix initial state for empty slot - nlm: Ensure callback code also checks that the files match - pwm: pca9685: Fix period change with same duty cycle - xtensa: move parse_tag_fdt out of #ifdef CONFIG_BLK_DEV_INITRD - nfit, libnvdimm: fix interleave set cookie calculation - mac80211: flush delayed work when entering suspend - mac80211: don't reorder frames with SN smaller than SSN - mac80211: don't handle filtered frames within a BA session - mac80211: use driver-indicated transmitter STA only for data frames - drm/amdgpu: add more cases to DCE11 possible crtc mask setup - drm/amdgpu/pm: check for headless before calling compute_clocks - Revert "drm/amdgpu: update tile table for oland/hainan" - drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS - drm/radeon: handle vfct with multiple vbios images - drm/edid: Add EDID_QUIRK_FORCE_8BPC quirk for Rotel RSX-1058 - drm/ttm: Make sure BOs being swapped out are cacheable - drm/vmwgfx: Work around drm removal of control nodes - drm/imx: imx-tve: Do not set the regulator voltage - drm/atomic: fix an error code in mode_fixup() - drm/i915/gvt: Disable access to stolen memory as a guest - drm: Cancel drm_fb_helper_dirty_work on unload - drm: Cancel drm_fb_helper_resume_work on unload - drm/i915: Recreate internal objects with single page segments if dmar fails - drm/i915: Avoid spurious WARNs about the wrong pipe in the PPS code - drm/i915: Check for timeout completion when waiting for the rq to submitted - drm/i915: Pass timeout==0 on to i915_gem_object_wait_fence() - drm/i915: Fix not finding the VBT when it overlaps with OPREGION_ASLE_EXT - libceph:
[Kernel-packages] [Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize
** Also affects: linux (Ubuntu Zesty) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Changed in: linux (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Zesty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1483101 Title: Broadcom bluetooth modules sometimes fail to initialize Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: This message can be found in dmesg: [ 15.080247] Bluetooth: hci0 command 0x1001 tx timeout Currently known affected modules: * 0a5c:216a * 0a5c:6410 * 0a5c:6412 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1483101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize
same problem on Lenovo x1 carbon 1st gen 0a5c:21e6 9903.370351] usb 1-1.4: new full-speed USB device number 9 using ehci-pci [ 9903.467690] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [ 9903.467697] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 9903.467701] usb 1-1.4: Product: BCM20702A0 [ 9903.467705] usb 1-1.4: Manufacturer: Broadcom Corp [ 9903.467708] usb 1-1.4: SerialNumber: 7CE9D3E9491F [ 9903.475850] Bluetooth: hci0: BCM: chip id 63 [ 9903.491894] Bluetooth: hci0: BCM20702A [ 9903.492904] Bluetooth: hci0: BCM20702A1 (001.002.014) build [ 9906.994358] Bluetooth: hci0 command 0x1001 tx timeout [ 9914.990488] Bluetooth: hci0: BCM: Reading local version info failed (-110) [ 9916.994516] Bluetooth: hci0 command 0x0c03 tx timeout [ 9924.990576] Bluetooth: hci0: BCM: Reset failed (-110) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1483101 Title: Broadcom bluetooth modules sometimes fail to initialize Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Bug description: This message can be found in dmesg: [ 15.080247] Bluetooth: hci0 command 0x1001 tx timeout Currently known affected modules: * 0a5c:216a * 0a5c:6410 * 0a5c:6412 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1483101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize
I'm affected too. My module is 0a5c:216c Thanks in advance. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1483101 Title: Broadcom bluetooth modules sometimes fail to initialize Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Bug description: This message can be found in dmesg: [ 15.080247] Bluetooth: hci0 command 0x1001 tx timeout Currently known affected modules: * 0a5c:216a * 0a5c:6410 * 0a5c:6412 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1483101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize
** Changed in: hwe-next Status: New => In Progress ** Changed in: hwe-next Assignee: (unassigned) => Jesse Sung (wenchien) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1483101 Title: Broadcom bluetooth modules sometimes fail to initialize Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Bug description: This message can be found in dmesg: [ 15.080247] Bluetooth: hci0 command 0x1001 tx timeout Currently known affected modules: * 0a5c:216a * 0a5c:6410 * 0a5c:6412 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1483101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
