You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/07/12 17:28:00 UTC

[jira] [Commented] (MYNEWT-810) Controller scheduler halts incorrect state machine

    [ https://issues.apache.org/jira/browse/MYNEWT-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084345#comment-16084345 ] 

ASF subversion and git services commented on MYNEWT-810:
--------------------------------------------------------

Commit 76a1a16db57133fcb13341eff33eed785187f460 in mynewt-core's branch refs/heads/master from [~wes3]
[ https://gitbox.apache.org/repos/asf?p=mynewt-core.git;h=76a1a16 ]

nimble/controller: Fix scheduler advertising halt error

MYNEWT-810: This fixes the scheduler error where the controller
would send the wrong state machine to the advertising halt
function and an incorrect event would get sent to the LL for
processing.


> Controller scheduler halts incorrect state machine
> --------------------------------------------------
>
>                 Key: MYNEWT-810
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-810
>             Project: Mynewt
>          Issue Type: Bug
>      Security Level: Public(Viewable by anyone) 
>          Components: Nimble
>    Affects Versions: v1_0_0_rel
>            Reporter: William San Filippo
>            Assignee: William San Filippo
>             Fix For: v1_1_0_rel
>
>
> The scheduler incorrectly uses the schedule object argument when halting advertising if an advertising event is ongoing but a new scheduled event occurs (a connection, for example). This bug we causing a connection end event to get posted to the link layer task while the connection event was ongoing (messes up internal connection state machine timing).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)