linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael N. Moran" <mike@mnmoran.org>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Mesh: Continuous Transaction Acknowledgment
Date: Mon, 27 Jul 2020 18:41:02 -0400	[thread overview]
Message-ID: <20d1abee-8400-19a9-6f15-d3011a8a3d0a@mnmoran.org> (raw)

I'm using a clone of bluez master on a Fedora 32 system.

I was using the Fedora 32 bluez-5.54 and bluez-mesh-5.54-1 
packages, but there are some issues when using mesh-test 
where opcodes are using the wrong byte-order that has been 
fixed in master.

Otherwise, mesh was working OK and I was able to provision 
and configure my device using mesh-cfgclient.

However, running the master branch code I am having a 
problem where provisioning does not complete and in the end, 
a Transaction Acknowledgment for my Random PDU is sent 
endlessly. The bluetooth-meshd does not seem to be sending a 
LE Set Advertise Enable to DISABLE advertising.

I assume that bluetooth-meshd has a timer that that fires 
that should disable the advertisement after some period of 
time (150ms), but the code is a bit opaque to my eyes.

I have a btmon trace the shows the problem if needed.

Also, the btmon trace shows that there are two LE Set 
Advertise Enable (DISABLE) HCI commands in a row just before 
the LE Set Advertising Data is issued for the offending 
Transaction Acknowledgment.

Thoughts?

-- 
Michael N. Moran           (h) 770 704 9751
218 Wilshire Terrace       (c) 678 521 5460
White, GA, USA 30184       http://mnmoran.org


                 reply	other threads:[~2020-07-27 22:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20d1abee-8400-19a9-6f15-d3011a8a3d0a@mnmoran.org \
    --to=mike@mnmoran.org \
    --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).