This bug was fixed in the package linux - 3.2.0-80.116

---------------
linux (3.2.0-80.116) precise; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #1435392

  [ Andy Whitcroft ]

  * [Packaging] generate live watchdog blacklists
    - LP: #1432837

  [ Upstream Kernel Changes ]

  * Drivers: hv: vmbus: incorrect device name is printed when child device
    is unregistered
    - LP: #1417313
  * x86, mm/ASLR: Fix stack randomization on 64-bit systems
    - LP: #1423757
    - CVE-2015-1593
  * net: llc: use correct size for sysctl timeout entries
    - LP: #1425271
    - CVE-2015-2041
  * net: rds: use correct size for max unacked packets and bytes
    - LP: #1425274
    - CVE-2015-2042
  * PCI: quirks: Fix backport of quirk_io()
    - LP: #1434639
  * MIPS: IRQ: Fix disable_irq on CPU IRQs
    - LP: #1434639
  * ASoC: atmel_ssc_dai: fix start event for I2S mode
    - LP: #1434639
  * ALSA: ak411x: Fix stall in work callback
    - LP: #1434639
  * lib/checksum.c: fix carry in csum_tcpudp_nofold
    - LP: #1434639
  * lib/checksum.c: fix build for generic csum_tcpudp_nofold
    - LP: #1434639
  * caif: remove wrong dev_net_set() call
    - LP: #1434639
  * MIPS: Fix kernel lockup or crash after CPU offline/online
    - LP: #1434639
  * gpio: sysfs: fix memory leak in gpiod_export_link
    - LP: #1434639
  * gpio: sysfs: fix memory leak in gpiod_sysfs_set_active_low
    - LP: #1434639
  * net: sctp: fix passing wrong parameter header to param_type2af in
    sctp_process_param
    - LP: #1434639
  * mm: pagewalk: call pte_hole() for VM_PFNMAP during walk_page_range
    - LP: #1434639
  * nilfs2: fix deadlock of segment constructor over I_SYNC flag
    - LP: #1434639
  * staging: comedi: cb_pcidas64: fix incorrect AI range code handling
    - LP: #1434639
  * media/rc: Send sync space information on the lirc device
    - LP: #1434639
  * sched/rt: Reduce rq lock contention by eliminating locking of
    non-feasible target
    - LP: #1434639
  * time: adjtimex: Validate the ADJ_FREQUENCY values
    - LP: #1434639
  * ntp: Fixup adjtimex freq validation on 32-bit systems
    - LP: #1434639
  * ipv6: fib: fix fib dump restart
    - LP: #1434639
  * ipv6: fib: fix fib dump restart
    - LP: #1434639
  * Bluetooth: ath3k: workaround the compatibility issue with xHCI
    controller
    - LP: #1400215, #1434639
  * Linux 3.2.68
    - LP: #1434639
  * KVM: nVMX: Fix content of MSR_IA32_VMX_ENTRY/EXIT_CTLS
    - LP: #1431473
 -- Brad Figg <brad.f...@canonical.com>   Mon, 23 Mar 2015 08:41:45 -0700

** Changed in: linux (Ubuntu Precise)
       Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-1593

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-2041

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-2042

** Changed in: linux (Ubuntu Precise)
       Status: Fix Committed => 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/1400215

Title:
  Atheros BT devices(ath3k) fail to work on USB3.0 buses

Status in HWE Next Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released

Bug description:
  Atheros BT devices(ath3k) fail to work on USB3.0 buses, but work well
  on USB 2.0

    1. BT devices will disappear from USB3.0 buses.
    2. BT devices can be found on USB3.0 buses, but can not be found by 
hciconfig.
    3. There are FW loading error messages in dmesg with USB3.0.

  $ dmesg | grep Blu
  [ 13.996701] Bluetooth: Core ver 2.19
  [ 13.996716] Bluetooth: HCI device and connection manager initialized
  [ 13.996722] Bluetooth: HCI socket layer initialized
  [ 13.996723] Bluetooth: L2CAP socket layer initialized
  [ 13.996729] Bluetooth: SCO socket layer initialized
  [ 15.763696] Bluetooth: RFCOMM TTY layer initialized
  [ 15.763705] Bluetooth: RFCOMM socket layer initialized
  [ 15.763709] Bluetooth: RFCOMM ver 1.11
  [ 15.772693] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [ 15.772696] Bluetooth: BNEP filters: protocol multicast
  [ 15.772703] Bluetooth: BNEP socket layer initialized
  [ 17.378235] Bluetooth: Error in firmware loading err = -110,len = 448, size 
= 1496
  [ 17.378242] Bluetooth: Loading sysconfig file failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1400215/+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

Reply via email to