** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1950825/+attachment/5540505/+files/ProcModules.txt

-- 
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/1950825

Title:
  Unable to pair Dell XPS 13 7390 Intel bluetooth btusb with some
  headset / speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do have a Dell XPS 13 7390 laptop running Ubuntu 20.04:
  Linux martin-XPS-13-7390 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 
20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  with Intel bluetooth card. dmesg recognizes it as:
  usb 1-7: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01
  usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
  It uses the btusb driver:
  usbcore: registered new interface driver btusb

  The driver / chip has problems to connect / pair with some headsets / 
speakers. Namely the Sony SRS-XB12 Mini speaker and the Teufel True Airy 
Wireless headset.
  Pairing other speaker devices with the XPS works fine and the Sony and Teufel 
itself pair fine with other linux laptops / android smartphones. I'd like to 
concentrate on the Teufel, as I have logged the pairing conversation.
  It looks like this on btmon:

  @ MGMT Command: Pair Device (0x0019) plen 8            {0x0001} [hci0] 
8.822002
          BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
          Capability: KeyboardDisplay (0x04)
  < HCI Command: Create Connection (0x01|0x0005) plen 13      #22 [hci0] 
8.822041
          Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
          Packet type: 0xcc18
            DM1 may be used
            DH1 may be used
            DM3 may be used
            DH3 may be used
            DM5 may be used
            DH5 may be used
          Page scan repetition mode: R2 (0x02)
          Page scan mode: Mandatory (0x00)
          Clock offset: 0x0000
          Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4                   #23 [hci0] 
8.822352
        Create Connection (0x01|0x0005) ncmd 1
          Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11               #28 [hci0] 
39.891457
          Status: LMP Response Timeout / LL Response Timeout (0x22)
          Handle: 65535
          Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
          Link type: ACL (0x01)
          Encryption: Disabled (0x00)
  @ MGMT Event: Connect Failed (0x000d) plen 8          {0x0002} [hci0] 
39.891549
          BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
          Status: Timeout (0x08)
  @ MGMT Event: Connect Failed (0x000d) plen 8          {0x0001} [hci0] 
39.891549
          BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
          Status: Timeout (0x08)
  @ MGMT Event: Command Complete (0x0001) plen 10       {0x0001} [hci0] 
39.891575
        Pair Device (0x0019) plen 7
          Status: Timeout (0x08)
          BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)

  So it pretty much looks like the laptop sends a connection request,
  but never sees a reply from the Teufel headset.

  Same conversation for a Surface Pro 3 laptop (with some broadcom
  bluetooth chip if I remember correctly, also using btusb driver) also
  running Ubuntu 20.04:

  @ MGMT Command: Pair Device (0x0019) plen 8            {0x0001} [hci0] 
4.925811
          BR/EDR Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
          Capability: DisplayYesNo (0x01)
  < HCI Command: Create Connection (0x01|0x0005) plen 13      #50 [hci0] 
4.925831
          Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
          Packet type: 0xcc18
            DM1 may be used
            DH1 may be used
            DM3 may be used
            DH3 may be used
            DM5 may be used
            DH5 may be used
          Page scan repetition mode: R2 (0x02)
          Page scan mode: Mandatory (0x00)
          Clock offset: 0x0000
          Role switch: Allow slave (0x01)
  > HCI Event: Command Status (0x0f) plen 4                   #51 [hci0] 
4.928927
        Create Connection (0x01|0x0005) ncmd 1
          Status: Success (0x00)
  > HCI Event: Connect Complete (0x03) plen 11                #54 [hci0] 
5.077961
          Status: Success (0x00)
          Handle: 1
          Address: 00:00:B0:05:65:67 (RND-RAD NETWORK DEVICES)
          Link type: ACL (0x01)
          Encryption: Disabled (0x00)
  < HCI Command: Read Remote Supporte.. (0x01|0x001b) plen 2  #55 [hci0] 
5.078179
          Handle: 1
  > HCI Event: Command Status (0x0f) plen 4                   #56 [hci0] 
5.078928
        Read Remote Supported Features (0x01|0x001b) ncmd 1
          Status: Success (0x00)
  [...]

  What could cause the Intel 8087 / 0029 bluetooth chip / driver not
  being able to connect to the Teufel speakers?

  There is also another report with a similar problem here: 
https://askubuntu.com/questions/1020584/apple-keyboard-a1016-pairing-fails
  How to further debug this problem?
  Is it necessary to buy some bt sniffer hardware to get to the bottom of this? 
I would invest in a cheapo 10€ CC2531 clone sniffer (like this 
https://www.amazon.com/-/en/dp/B081WRGL31) but I am not sure if they are 
sufficient to capture the pairing process.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  martin     4168 F.... pulseaudio
   /dev/snd/pcmC0D3p:   martin     4168 F...m pulseaudio
   /dev/snd/pcmC0D0c:   martin     4168 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-21 (722 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 7390
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic 
root=UUID=9fb13a1c-ce7e-451e-b7ee-f1710b84eccf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-40-generic N/A
   linux-backports-modules-5.11.0-40-generic  N/A
   linux-firmware                             1.187.17
  Tags:  focal
  Uname: Linux 5.11.0-40-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-27 (411 days ago)
  UserGroups: adm cdrom dialout dip kvm lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd10/22/2020:br1.7:svnDellInc.:pnXPS137390:pvr:sku0962:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950825/+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