Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <b4a13800dc869d85c9d5fba9c91483da954f286c.camel@ewol.com>
Subject: Re: mesh: call to Publish triggers apparent output loop in
 mesh/mesh-io-generic.c
From:   Steve Brown <sbrown@ewol.com>
To:     "Gix, Brian" <brian.gix@intel.com>,
        "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc:     "Stotland, Inga" <inga.stotland@intel.com>
Date:   Thu, 24 Dec 2020 04:23:21 -0500
In-Reply-To: <MW3PR11MB45394DC567668E8D0AD2081CE1DF0@MW3PR11MB4539.namprd11.prod.outlook.com>
References: <cf925daf120458a23798be054865d1e39068f7b5.camel@ewol.com>
         <MW3PR11MB45394DC567668E8D0AD2081CE1DF0@MW3PR11MB4539.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.38.1-1 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi Brian,

On Tue, 2020-12-22 at 18:43 +0000, Gix, Brian wrote:
> Hi Steve, I will investigate on my RPI4
> 
> -----Original Message-----
> From: Steve Brown <sbrown@ewol.com> 
> Sent: Tuesday, December 22, 2020 7:57 AM
> To: linux-bluetooth@vger.kernel.org
> Subject: mesh: call to Publish triggers apparent output loop in
> mesh/mesh-io-generic.c
> 
> Publish functions as expected, but results in continuous, very heavy
> HCI traffic (~every .7ms per btmon log). I don't think it's my
> application as the problem persists after the application disconnects
> from dbus and exits.
> 
> The calls to LE Set Adv Param all fail. Prior to the Publish call, LE
> Set Param calls succeed. The only difference I can see is the failing
> ones have an interval of 50ms and the ones that succeed have 100ms. A
> successful one is appended.
> 
> I'm at current Bluez head (65231892cd). The platform is a rpi4. 
> 
> Below is a pretty normal looking meshd log, a btmon dump and some
> more
> normal looking dbus traffic.
> 
> Steve

I think I found my problem. My retransmit count was set to zero.

If the publish retransmit count is 0, mesh-io-generic.c:tx_to() repeats
the message indefinitely. However, 4.2.2.6 of the mesh profile spec
V1.0 seems to state that 0 means no retransmissions.

Steve