Strange issue after early AP startup

[Hans Petter Selasky]

On 01/17/17 22:28, Hans Petter Selasky wrote:
> +                       state->nextcall = SBT_MAX;
> +                       state->nextcallopt = now + 1;

BTW: What locks are protecting the update of these fields? Can they be 
written simultaneously by configtimer() and cpu_new_callout()?

--HPS