Strange issue after early AP startup

[Hans Petter Selasky]

On 01/18/17 02:18, John Baldwin wrote:
> You might still want to adjust 'nextevent' to schedule the next interrupt
> to be sooner than 'timerperiod' though.  You could just set 'nextevent' to
> 'now' in that case instead of 'next'.

Right, I'll give that a spin. Would have to be "now + 1" instead of 
"now", due to check before et_start() ?

--HPS