From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Alexandre Pereira Nunes <alexandre.nunes@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: After kernel update: connect/disconnect forever while attempting to auto-reconnect
Date: Sat, 18 May 2019 19:30:18 +0300 [thread overview]
Message-ID: <CABBYNZKbWAaO9dTnHcV7vCYodRQYEZT8=PBws+=_iip-7Njo2w@mail.gmail.com> (raw)
In-Reply-To: <CANxMttCqEYDZOwTriLqC-q39+JhEJ9KCOsPhRqkjZwE1h-64Gg@mail.gmail.com>
Hi Alexandre,
On Sat, May 18, 2019 at 7:13 PM Alexandre Pereira Nunes
<alexandre.nunes@gmail.com> wrote:
>
> I've attached two btmon sessions: one captured from the text mode and
> another with -w param.
>
> Both on 5.1.2 kernel.
The problem seems to be here:
< ACL Data TX: Handle 512 flags 0x00 dlen 16 #87 [hci0] 9.952984
L2CAP: Connection Response (0x03) ident 1 len 8
Destination CID: 0
Source CID: 65
Result: Connection refused - security block (0x0003)
Status: No further information available (0x0000)
Ruling out encryption since HID don't require it:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/profiles/input/server.c#n294
Are you seeing any of the following logs on the journal:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/profiles/input/server.c#n181
> Em sáb, 18 de mai de 2019 às 05:53, Carlos Pita
> <carlosjosepita@gmail.com> escreveu:
> >
> > Hi Luiz,
> >
> > I've attached the output for a single auto-reconnect/disconnect sequence.
> >
> > Notice this was using the 4.19.44 kernel, which is the LTS one in Arch
> > Linux. As I've pointed out above, the problem seems like a regression,
> > since it's happening both in older and latest kernels, but not
> > in-between them.
> >
> > Best regards
> > --
> > Carlos
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2019-05-18 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 5:59 After kernel update: connect/disconnect forever while attempting to auto-reconnect Carlos Pita
2019-05-17 21:39 ` 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 [this message]
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='CABBYNZKbWAaO9dTnHcV7vCYodRQYEZT8=PBws+=_iip-7Njo2w@mail.gmail.com' \
--to=luiz.dentz@gmail.com \
--cc=alexandre.nunes@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).