Strange issue after early AP startup
Jia-Shiun Li
jiashiun at gmail.com
Thu Jan 19 10:35:25 UTC 2017
On Thu, Jan 19, 2017 at 4:23 PM, Hans Petter Selasky <hps at selasky.org>
wrote:
>
> I can add prints/asserts to show that what happens is that
> "state->nextcallopt > now" while "state->nextcall <= now". This situtation
> is allowed to persist due to the way getnextcpuevent() is currently
> implemented.
>
> Can the people CC'ed give the attached patch a spin and report back?
>
>
As far as c2d system time is concerned, it works correctly for me w/
r312210.
-Jia-Shiun.
More information about the freebsd-current
mailing list