Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <BN7PR04MB52674E1CAADA5B0550C3F6959FB39@BN7PR04MB5267.namprd04.prod.outlook.com>
 <CABBYNZLaPxBMvVXWx+yqQz-SyxptdMfEZ5TPQVP7q4otpcbErg@mail.gmail.com> <BN7PR04MB526737063784913B34568C009FB29@BN7PR04MB5267.namprd04.prod.outlook.com>
In-Reply-To: <BN7PR04MB526737063784913B34568C009FB29@BN7PR04MB5267.namprd04.prod.outlook.com>
From:   Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date:   Wed, 22 Jun 2022 14:31:59 -0700
Message-ID: <CABBYNZ+Ak=U1UUmYvWwfGOMMQNBAFKpbNm_ZoUTcGvCw7EYxpQ@mail.gmail.com>
Subject: Re: third time
To:     Thomas Green <TGreen2@sorenson.com>
Cc:     "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Hi Thomas,

On Wed, Jun 22, 2022 at 2:22 PM Thomas Green <TGreen2@sorenson.com> wrote:
>
> Luiz,
>
> Thank you for your reply.  In my first two attempts I pasted into it the =
log file created by running:
>
> bluetoothd --experimental -debug -n
>
> The version of bluez is 5.50.  I looked at the patch you suggested and it=
's already included in this version of src/device.c
>
> Are there any further patches I should look at?  Would you like a copy of=
 my log again?

Ouch, that is quite an old version, have you considered using something new=
er?

> Tom
>
> -----Original Message-----
> From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
> Sent: Tuesday, June 21, 2022 2:40 PM
> To: Thomas Green <TGreen2@Sorenson.com>
> Cc: linux-bluetooth@vger.kernel.org
> Subject: Re: third time
>
> [EXTERNAL]
>
> Hi Thomas,
>
> On Tue, Jun 21, 2022 at 1:29 PM Thomas Green <TGreen2@sorenson.com> wrote=
:
> >
> > I've twice before written about this issue I'm having, but never heard =
anything back.  It regards a GATT device that connects and operates correct=
ly.  The issue is when we call the Adapter1.RemoveDevice method for this de=
vice.  Some times the device is removed completely, and everything works fi=
ne.  Some times it fails and bluetoothd becomes unusable.  Even when I shut=
down and restart bluetoothd it doesn't operate correctly when restarting.  =
The difference is that when it works, at the end of the removal process, it=
 reconnects the device, tries to recreate the device, then removes it.  All=
 internally.  When things fail, those steps don't happen.  I've posted befo=
re the salient part of the Bluetooth log.  The only thing that will make bl=
uetoothd function correctly is to shut it down, remove all of the similar G=
ATT devices, then restart bluetoothd.
> >
> > I have yet to hear if anyone has -any- idea regarding this, not even to=
 tell me it's not something that needs to be looked at.  It is something th=
at renders bluetoothd unusable, so I would think that it is something that =
might be interesting to look into.
> >
> > If anyone has any ideas where to look, or what might be going on, I'd
> > love to hear from you
>
> Do you have any logs? Also what version is this happening, perhaps you ar=
e missing some fixes like:
>
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=3D5ebc2b5a3=
e48dbe67a2d315979b096a1b4d1eb99
>
> >
> > Tom Green
>
>
>
> --
> Luiz Augusto von Dentz


--=20
Luiz Augusto von Dentz