Linux-Bluetooth Archive on lore.kernel.org
 help / color / Atom feed
* [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15
       [not found] <bug-203997-62941@https.bugzilla.kernel.org/>
@ 2019-06-27  0:22 ` bugzilla-daemon
  2019-06-27 13:35 ` bugzilla-daemon
                   ` (10 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-06-27  0:22 UTC (permalink / raw)
  To: linux-bluetooth

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

Ron Murray (rjmx@rjmx.net) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rjmx@rjmx.net

--- Comment #1 from Ron Murray (rjmx@rjmx.net) ---
Had same problem here with my Beats Wireless 810(?) headphones.
Reverting to kernel 5.1.14 fixed the problem.

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15
       [not found] <bug-203997-62941@https.bugzilla.kernel.org/>
  2019-06-27  0:22 ` [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15 bugzilla-daemon
@ 2019-06-27 13:35 ` bugzilla-daemon
  2019-06-28 13:05 ` bugzilla-daemon
                   ` (9 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-06-27 13:35 UTC (permalink / raw)
  To: linux-bluetooth

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

--- Comment #3 from Daniel Ponte (amigan@gmail.com) ---
Seeing similar with Logitech H800 headphones. Sometimes it stays connected.
Curiously enough, HFP profile sometimes works (using tanuk's pulseaudio-hfp
patch), but A2DP absolutely will not activate. The headphones will even
register with pulseaudio as a bare device but A2DP remains unavailable.

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15
       [not found] <bug-203997-62941@https.bugzilla.kernel.org/>
  2019-06-27  0:22 ` [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15 bugzilla-daemon
  2019-06-27 13:35 ` bugzilla-daemon
@ 2019-06-28 13:05 ` bugzilla-daemon
  2019-07-01  7:15 ` bugzilla-daemon
                   ` (8 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-06-28 13:05 UTC (permalink / raw)
  To: linux-bluetooth

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

Søren Holm (sgh@sgh.dk) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sgh@sgh.dk

--- Comment #4 from Søren Holm (sgh@sgh.dk) ---
(In reply to Daniel Ponte from comment #3)
> Seeing similar with Logitech H800 headphones. Sometimes it stays connected.
> Curiously enough, HFP profile sometimes works (using tanuk's pulseaudio-hfp
> patch), but A2DP absolutely will not activate. The headphones will even
> register with pulseaudio as a bare device but A2DP remains unavailable.

I have the exact same problem also with H800 headset.

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15
       [not found] <bug-203997-62941@https.bugzilla.kernel.org/>
                   ` (2 preceding siblings ...)
  2019-06-28 13:05 ` bugzilla-daemon
@ 2019-07-01  7:15 ` bugzilla-daemon
  2019-07-01 12:23 ` bugzilla-daemon
                   ` (7 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-07-01  7:15 UTC (permalink / raw)
  To: linux-bluetooth

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

--- Comment #8 from Matias Karhumaa (matias.karhumaa@gmail.com) ---
Ah, I think recent regression fix [1] caused another bug:

--snip--
static bool l2cap_check_enc_key_size(struct hci_conn *hcon)
{
        /* The minimum encryption key size needs to be enforced by the
         * host stack before establishing any L2CAP connections. The
         * specification in theory allows a minimum of 1, but to align
         * BR/EDR and LE transports, a minimum of 7 is chosen.
         *
         * This check might also be called for unencrypted connections
         * that have no key size requirements. Ensure that the link is
         * actually encrypted before enforcing a key size.
         */
        return (!test_bit(HCI_CONN_ENCRYPT, &hcon->flags) ||
                hcon->enc_key_size > HCI_MIN_ENC_KEY_SIZE);
}
--snip--

If Encryption key size is 7, L2CAP connection will fail. I think it should be
something like this:

In l2cap_core.c

static bool l2cap_check_enc_key_size(struct hci_conn *hcon)
{
        /* The minimum encryption key size needs to be enforced by the
         * host stack before establishing any L2CAP connections. The
         * specification in theory allows a minimum of 1, but to align
         * BR/EDR and LE transports, a minimum of 7 is chosen.
         *
         * This check might also be called for unencrypted connections
         * that have no key size requirements. Ensure that the link is
         * actually encrypted before enforcing a key size.
         */
        return (!test_bit(HCI_CONN_ENCRYPT, &hcon->flags) ||
                hcon->enc_key_size >= HCI_MIN_ENC_KEY_SIZE);
}
--snip--

Could you test the fix?

[1]:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/net/bluetooth?id=693cd8ce3f882524a5d06f7800dd8492411877b3

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15
       [not found] <bug-203997-62941@https.bugzilla.kernel.org/>
                   ` (3 preceding siblings ...)
  2019-07-01  7:15 ` bugzilla-daemon
@ 2019-07-01 12:23 ` bugzilla-daemon
  2019-07-07 11:33 ` bugzilla-daemon
                   ` (6 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-07-01 12:23 UTC (permalink / raw)
  To: linux-bluetooth

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

--- Comment #10 from Eivind Eide (xenofil@gmail.com) ---
Compiled 5.1.15 kernel with this patch and it indeed fixes the problem of
pairing with KLIPSCH KMC 1. Thanks!

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15
       [not found] <bug-203997-62941@https.bugzilla.kernel.org/>
                   ` (4 preceding siblings ...)
  2019-07-01 12:23 ` bugzilla-daemon
@ 2019-07-07 11:33 ` bugzilla-daemon
  2019-07-07 11:43 ` bugzilla-daemon
                   ` (5 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-07-07 11:33 UTC (permalink / raw)
  To: linux-bluetooth

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

--- Comment #13 from Matias Karhumaa (matias.karhumaa@gmail.com) ---
Eivind and Martin, thanks for testing!

Søren, could it be that for some reason now headset is able to create
connection? In your previous btmon trace we can see that headset was trying to
connect HFP but failed because your SDP records did not have record for HFP AG.
Then your machine tried to connect but failed because of the bug introduced in
5.1.15.

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15
       [not found] <bug-203997-62941@https.bugzilla.kernel.org/>
                   ` (5 preceding siblings ...)
  2019-07-07 11:33 ` bugzilla-daemon
@ 2019-07-07 11:43 ` bugzilla-daemon
  2019-09-02 11:44 ` bugzilla-daemon
                   ` (4 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-07-07 11:43 UTC (permalink / raw)
  To: linux-bluetooth

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

--- Comment #15 from Søren Holm (sgh@sgh.dk) ---
(In reply to Jan Steffens from comment #14)
> If you're running 5.1.16-arch1, please note that the patch has been
> backported into this release.

I do - then that is why. Sorry for the noise.

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15
       [not found] <bug-203997-62941@https.bugzilla.kernel.org/>
                   ` (6 preceding siblings ...)
  2019-07-07 11:43 ` bugzilla-daemon
@ 2019-09-02 11:44 ` bugzilla-daemon
  2019-09-02 11:49 ` bugzilla-daemon
                   ` (3 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-09-02 11:44 UTC (permalink / raw)
  To: linux-bluetooth

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

Pavel (pavel@noa-labs.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pavel@noa-labs.com

--- Comment #16 from Pavel (pavel@noa-labs.com) ---
Hello,

I'm afraid you are not out of the woods yet. I tried 5.2 and still can't pair a
lot of BT LE products based on MXCHIP chipset, including my mouse. My fear is
that they do use a key size of 1 by default 8-[]

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15
       [not found] <bug-203997-62941@https.bugzilla.kernel.org/>
                   ` (7 preceding siblings ...)
  2019-09-02 11:44 ` bugzilla-daemon
@ 2019-09-02 11:49 ` bugzilla-daemon
  2019-09-03 12:37 ` bugzilla-daemon
                   ` (2 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-09-02 11:49 UTC (permalink / raw)
  To: linux-bluetooth

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

--- Comment #17 from Pavel (pavel@noa-labs.com) ---
Created attachment 284765
  --> https://bugzilla.kernel.org/attachment.cgi?id=284765&action=edit
Traffic capture of a broken pairing

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15
       [not found] <bug-203997-62941@https.bugzilla.kernel.org/>
                   ` (8 preceding siblings ...)
  2019-09-02 11:49 ` bugzilla-daemon
@ 2019-09-03 12:37 ` bugzilla-daemon
  2019-09-03 12:45 ` bugzilla-daemon
  2019-09-08 12:19 ` bugzilla-daemon
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-09-03 12:37 UTC (permalink / raw)
  To: linux-bluetooth

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

--- Comment #19 from Pavel (pavel@noa-labs.com) ---
Matias, I'm afraid this also happening with all BT LE devices I have, including
ones not MXCHIP based like Microsoft mouses.

I'm very sure it is a BT related issues as when I switch to non-le 3.0 mode,
the mouse works fine. It started happening at some time during the 5.1 release
cycle.

I would better try to use a usb dongle for BT, trying to confirm if this is not
a modem (Qualcomm) issue.

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15
       [not found] <bug-203997-62941@https.bugzilla.kernel.org/>
                   ` (9 preceding siblings ...)
  2019-09-03 12:37 ` bugzilla-daemon
@ 2019-09-03 12:45 ` bugzilla-daemon
  2019-09-08 12:19 ` bugzilla-daemon
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-09-03 12:45 UTC (permalink / raw)
  To: linux-bluetooth

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

--- Comment #20 from Pavel (pavel@noa-labs.com) ---
Created attachment 284773
  --> https://bugzilla.kernel.org/attachment.cgi?id=284773&action=edit
Capture of a mouse connection which leads to no mouse movement

I attached one more capture.

I see that connection lights up in the blueman UI, and then times out when I
stop pressing the mouse buttons after 30 seconds. All without a sign of mouse
movement.

Were there any changes to BTLE during 5.1, 5.2 release cycle?

I think this worth a separate bug report.

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15
       [not found] <bug-203997-62941@https.bugzilla.kernel.org/>
                   ` (10 preceding siblings ...)
  2019-09-03 12:45 ` bugzilla-daemon
@ 2019-09-08 12:19 ` bugzilla-daemon
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-09-08 12:19 UTC (permalink / raw)
  To: linux-bluetooth

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

--- Comment #21 from Pavel (pavel@noa-labs.com) ---
Matias, I ordered an Intel ax200 wifi+bluetooth card for testing. It should
arrive in a week or so.

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, back to index

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-203997-62941@https.bugzilla.kernel.org/>
2019-06-27  0:22 ` [Bug 203997] [REGRESSION] Unable to connect BT audio device on 5.1.15 bugzilla-daemon
2019-06-27 13:35 ` bugzilla-daemon
2019-06-28 13:05 ` bugzilla-daemon
2019-07-01  7:15 ` bugzilla-daemon
2019-07-01 12:23 ` bugzilla-daemon
2019-07-07 11:33 ` bugzilla-daemon
2019-07-07 11:43 ` bugzilla-daemon
2019-09-02 11:44 ` bugzilla-daemon
2019-09-02 11:49 ` bugzilla-daemon
2019-09-03 12:37 ` bugzilla-daemon
2019-09-03 12:45 ` bugzilla-daemon
2019-09-08 12:19 ` bugzilla-daemon

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