From: Thomas Green <TGreen2@Sorenson.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: RE: third time
Date: Wed, 22 Jun 2022 21:08:23 +0000 [thread overview]
Message-ID: <BN7PR04MB526737063784913B34568C009FB29@BN7PR04MB5267.namprd04.prod.outlook.com> (raw)
In-Reply-To: <CABBYNZLaPxBMvVXWx+yqQz-SyxptdMfEZ5TPQVP7q4otpcbErg@mail.gmail.com>
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?
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 correctly. The issue is when we call the Adapter1.RemoveDevice method for this device. Some times the device is removed completely, and everything works fine. Some times it fails and bluetoothd becomes unusable. Even when I shutdown 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 before the salient part of the Bluetooth log. The only thing that will make bluetoothd function correctly is to shut it down, remove all of the similar GATT 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 that 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 are missing some fixes like:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=5ebc2b5a3e48dbe67a2d315979b096a1b4d1eb99
>
> Tom Green
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2022-06-22 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 20:23 third time Thomas Green
2022-06-21 20:40 ` Luiz Augusto von Dentz
2022-06-22 21:08 ` Thomas Green [this message]
2022-06-22 21:31 ` Luiz Augusto von Dentz
2022-06-22 21:43 ` Thomas Green
2022-06-23 20:00 ` Thomas Green
2022-06-24 7:01 ` Paul Menzel
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=BN7PR04MB526737063784913B34568C009FB29@BN7PR04MB5267.namprd04.prod.outlook.com \
--to=tgreen2@sorenson.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).