Re: Strange issue after early AP startup

On 01/17/17 16:50, John Baldwin wrote:
> (One odd thing is that even in your case the first call to handleevents(),
> the 'now => state->nextcallout' check in handleevents() should be true
> which resets both nextcall and nextcallopt and invokes callout_process().)

Hi,

I suspect the cpu_new_callout() function is changing this condition 
after a callout_reset() call, before handleevents() gets a chance to run.

I'll give your patch a spin right away and let you know how it goes.

--HPS