Date: Tue, 17 Jan 2017 18:46:40 +0100 From: Hans Petter Selasky <hps@selasky.org> To: John Baldwin <jhb@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, Konstantin Belousov <kib@freebsd.org> Subject: Re: Strange issue after early AP startup Message-ID: <17c85624-9a8b-183b-7e3b-0169b0c53a39@selasky.org> In-Reply-To: <2215603.KuBd8pM5Pm@ralph.baldwin.cx> References: <b9c53237-4b1a-a140-f692-bf5837060b18@selasky.org> <3466870.vFI8cjabAc@ralph.baldwin.cx> <264c5dd8-d82d-3326-7de5-96b0bb96ac01@selasky.org> <2215603.KuBd8pM5Pm@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/17/17 16:50, John Baldwin wrote: > Index: kern_clocksource.c > =================================================================== > --- kern_clocksource.c (revision 312301) > +++ kern_clocksource.c (working copy) > @@ -503,7 +503,12 @@ configtimer(int start) > state->nextevent = SBT_MAX; > else > #endif > + if (next < state->nextcall) > state->nextevent = next; > + else if (state->nextcall < now) > + state->nextevent = now; > + else > + state->nextevent = state->nextcall; > if (periodic) > state->nexttick = next; > else > @@ -511,8 +516,6 @@ configtimer(int start) > state->nexthard = next; > state->nextstat = next; > state->nextprof = next; > - state->nextcall = next; > - state->nextcallopt = next; > hardclock_sync(cpu); > } > busy = 0; This patch makes it worse. Now I don't even reach the login prompt. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17c85624-9a8b-183b-7e3b-0169b0c53a39>