[Bug 199111] New: BCM4324B5: bt connection to paired devices is only established when discovery/scan is enabled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=199111

            Bug ID: 199111
           Summary: BCM4324B5: bt connection to paired devices is only
                    established when discovery/scan is enabled
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.16-rc4
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@xxxxxxxxxxxxxxx
          Reporter: sassmann@xxxxxxxxxx
        Regression: No

Created attachment 274717
  --> https://bugzilla.kernel.org/attachment.cgi?id=274717&action=edit
dmesg-4.16-rc4.txt

The chip only connects to paired devices when discovery/scanning is enabled.
Otherwise connection is never established.

Device Info:
[   17.617214] Bluetooth: hci0: BCM: chip id 90
[   17.620448] Bluetooth: hci0: BCM: features 0x0f
[   17.626236] Bluetooth: hci0: BCM4324B5

root@tpt10:~ > bluetoothctl --version
bluetoothctl: 5.48
root@tpt10:~ > hciconfig -a
hci0:   Type: Primary  Bus: UART
        BD Address: EC:0E:C4:1D:BB:5A  ACL MTU: 1021:8  SCO MTU: 64:1
        UP RUNNING PSCAN ISCAN INQUIRY
        RX bytes:3798 acl:0 sco:0 events:332 errors:0
        TX bytes:35719 acl:0 sco:0 commands:309 errors:0
        Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH SNIFF
        Link mode: SLAVE ACCEPT
        Name: 'localhost.localdomain'
        Class: 0x0c0110
        Service Classes: Rendering, Capturing
        Device Class: Computer, Handheld
        HCI Version: 4.0 (0x6)  Revision: 0x3492
        LMP Version: 4.0 (0x6)  Subversion: 0x4606
        Manufacturer: Broadcom Corporation (15)

[bluetooth]# show
Controller EC:0E:C4:1D:BB:5A (public)
        Name: localhost.localdomain
        Alias: localhost.localdomain
        Class: 0x000c0110
        Powered: yes
        Discoverable: yes
        Pairable: yes
        UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0530
        Discovering: yes
[Universal Mobile Keyboard]# info C0:33:5E:75:86:AB
Device C0:33:5E:75:86:AB (public)
        Name: Universal Mobile Keyboard
        Alias: Universal Mobile Keyboard
        Class: 0x00000540
        Icon: input-keyboard
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Service Discovery Serve.. (00001000-0000-1000-8000-00805f9b34fb)
        UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v045Ep0802d0099


The following warning is printed on boot:
[   17.231279] ======================================================
[   17.234231] WARNING: possible circular locking dependency detected
[   17.237170] 4.16.0-0.rc4.git3.1.fc27.x86_64 #1 Not tainted
[   17.240115] ------------------------------------------------------
[   17.243049] kworker/u8:1/74 is trying to acquire lock:
[   17.245962]  (bcm_device_lock){+.+.}, at: [<00000000acdc9be0>]
bcm_recv+0x68/0xe0 [hci_uart]
[   17.248943]·
               but task is already holding lock:
[   17.254812]  (&buf->lock){+.+.}, at: [<0000000057d725d1>]
flush_to_ldisc+0x20/0xa0
[   17.257845]·
               which lock already depends on the new lock.
Attaching full dmesg.

-- 
You are receiving this mail because:
You are the assignee for the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux