From: Carlos Pita <carlosjosepita@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: After kernel update: connect/disconnect forever while attempting to auto-reconnect
Date: Fri, 17 May 2019 02:59:05 -0300 [thread overview]
Message-ID: <CAELgYhdqAxTGA98RsUEOSEA5WfhxGaVn7C_DegAfU13sHx817A@mail.gmail.com> (raw)
Hi,
after upgrading to kernel 5.1.1 (and also 5.1.2) my bluetooth speakers
are unable to auto-reconnect. I can connect them without problems, but
once I turn them off and on again an unending sequence of connections
and disconnections begins:
---- manual connection ok ---------
[bluetooth]# connect E0:D1:E6:07:62:E1
Attempting to connect to E0:D1:E6:07:62:E1
[CHG] Device E0:D1:E6:07:62:E1 Connected: yes
Connection successful
[CHG] Device E0:D1:E6:07:62:E1 ServicesResolved: yes
---- turned off speakers and on again ----
[CHG] Device E0:D1:E6:07:62:E1 ServicesResolved: no
[CHG] Device E0:D1:E6:07:62:E1 Connected: no
[CHG] Device E0:D1:E6:07:62:E1 Connected: yes
[CHG] Device E0:D1:E6:07:62:E1 Connected: no
[CHG] Device E0:D1:E6:07:62:E1 Connected: yes
[CHG] Device E0:D1:E6:07:62:E1 Connected: no
[CHG] Device E0:D1:E6:07:62:E1 Connected: yes
[CHG] Device E0:D1:E6:07:62:E1 Connected: no
[CHG] Device E0:D1:E6:07:62:E1 Connected: yes
[CHG] Device E0:D1:E6:07:62:E1 Connected: no
I've tested this with a number of kernels:
linux-lts 4.19.43: doesn't work
linux 5.0.13: works
linux 5.1: works
linux 5.1.1: doesn't work
linux 5.1.2: doesn't work
All the above tests were done against bluez 5.50. I've also tested
bluez git master against linux 5.1.2 to no avail.
During failed attempts to auto-reconnect, the debug log shows:
May 17 02:25:27 carlos bluetoothd[8178]:
src/adapter.c:connected_callback() hci0 device E0:D1:E6:07:62:E1
connected eir_len 5
May 17 02:25:27 carlos bluetoothd[8178]:
src/adapter.c:dev_disconnected() Device E0:D1:E6:07:62:E1
disconnected, reason 3
May 17 02:25:27 carlos bluetoothd[8178]:
src/adapter.c:adapter_remove_connection()
May 17 02:25:27 carlos bluetoothd[8178]:
plugins/policy.c:disconnect_cb() reason 3
May 17 02:25:27 carlos bluetoothd[8178]:
src/adapter.c:bonding_attempt_complete() hci0 bdaddr E0:D1:E6:07:62:E1
type 0 status 0xe
May 17 02:25:27 carlos bluetoothd[8178]:
src/device.c:device_bonding_complete() bonding (nil) status 0x0e
May 17 02:25:27 carlos bluetoothd[8178]:
src/device.c:device_bonding_failed() status 14
Some other info that may be relevant:
> uname -a
Linux carlos 5.1.1-arch1-1-ARCH #1 SMP PREEMPT Sat May 11 13:02:48 UTC
2019 x86_64 GNU/Linux
> yay -Qi pulseaudio
Version : 12.2-2
If you need something else to track down this issue, please let me
know. I've also reported this to pulseaudio tracker:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/674.
Best regards
--
Carlos
next reply other threads:[~2019-05-17 5:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 5:59 Carlos Pita [this message]
2019-05-17 21:39 ` After kernel update: connect/disconnect forever while attempting to auto-reconnect Alexandre Pereira Nunes
2019-05-18 5:33 ` Luiz Augusto von Dentz
2019-05-18 8:53 ` Carlos Pita
2019-05-18 14:08 ` Alexandre Pereira Nunes
2019-05-18 16:30 ` Luiz Augusto von Dentz
2019-05-18 18:08 ` Johan Hedberg
2019-05-19 8:39 ` Luiz Augusto von Dentz
2019-05-18 17:05 ` Johan Hedberg
2019-05-18 17:09 ` Johan Hedberg
Reply instructions:
You may reply publicly 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=CAELgYhdqAxTGA98RsUEOSEA5WfhxGaVn7C_DegAfU13sHx817A@mail.gmail.com \
--to=carlosjosepita@gmail.com \
--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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).