Linux-Bluetooth Archive on lore.kernel.org
 help / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 202515] New: Bluetooth LE Extended Connect returning Command Disallowed
Date: Wed, 06 Feb 2019 00:01:03 +0000
Message-ID: <bug-202515-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 202515
           Summary: Bluetooth LE Extended Connect returning Command
                    Disallowed
           Product: Drivers
           Version: 2.5
    Kernel Version: v4.19
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: master.homer@gmail.com
        Regression: No

Ever since Linux v4.19 I haven't been able to connect to my mouse via bluetooth
LE, using an Intel 9260 (supporting AC Wifi and Bluetooth 5) with a pci-e
adaptor.


Basically, the device doesn't pair at all - dmesg just says:
Bluetooth: hci0: request failed to create LE connection: status 0x0c.

I've been able to narrow this down to commit
4d94f95d30c8fbfe86068e9abed110974d697cf5, which introduced extended LE Connect
if supported by the card.

To get some more info, I ran hcidump, and the relevant output says:
< HCI Command: Unknown (0x08|0x0043) plen 26
> HCI Event: Command Status (0x0f) plen 4
    Unknown (0x08|0x0043) status 0x0c ncmd 1
    Error: Command Disallowed

On a working system (using v4.18), with the legacy connect command, the hcidump
says:
< HCI Command: LE Create Connection (0x08|0x000d) plen 25
    bdaddr DA:B8:DC:90:75:A7 type 1
    interval 96 window 96 initiator_filter 0
    own_bdaddr_type 0 min_interval 6 max_interval 9
    latency 100 supervision_to 600 min_ce 0 max_ce 0
> HCI Event: Command Status (0x0f) plen 4
    LE Create Connection (0x08|0x000d) status 0x00 ncmd 2

I also grabbed the Local commands supported, which says:
< HCI Command: Read Local Supported Commands (0x04|0x0002) plen 0
> HCI Event: Command Complete (0x0e) plen 68
    Read Local Supported Commands (0x04|0x0002) ncmd 1
    status 0x00
    Commands: fffffb03ccffefffff3ffc9ff30fe8fe3ff78fff1c00040061f7ffff7fb80000
              feffffffffdfff07

As far as I can see, the kernel checks byte 37 of the local supported commands
output, to see if it should enable the Extended connect command or not.

I couldn't find any reports at all about this, and I couldn't really find much
info on the extended connect command at all. Is there any way of disabling
this? Or would it be at all possible to use the legacy connect command when the
extended command fails?

Do let me know if you need any more information.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply index

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06  0:01 bugzilla-daemon [this message]
2019-02-06  8:27 ` [Bug 202515] " bugzilla-daemon
2019-02-06  8:27 ` bugzilla-daemon
2019-02-06  9:07 ` bugzilla-daemon
2019-02-06  9:42 ` bugzilla-daemon
2019-02-06 11:11 ` bugzilla-daemon
2019-02-06 11:11 ` bugzilla-daemon
2019-02-06 11:19 ` bugzilla-daemon
2019-02-06 11:58 ` bugzilla-daemon
2019-02-06 12:18 ` bugzilla-daemon
2019-02-06 19:36 ` bugzilla-daemon
2019-02-07 12:59 ` bugzilla-daemon
2019-02-07 22:55 ` bugzilla-daemon
2019-02-07 23:05 ` bugzilla-daemon
2019-02-07 23:48 ` bugzilla-daemon
2019-02-08 16:16 ` bugzilla-daemon
2019-02-08 17:35 ` bugzilla-daemon
2019-02-08 21:39 ` bugzilla-daemon

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-202515-62941@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Bluetooth Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-bluetooth/0 linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ https://lore.kernel.org/linux-bluetooth \
		linux-bluetooth@vger.kernel.org linux-bluetooth@archiver.kernel.org
	public-inbox-index linux-bluetooth


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-bluetooth


AGPL code for this site: git clone https://public-inbox.org/ public-inbox