Strange issue after early AP startup

Hans Petter Selasky hps at selasky.org
Tue Jan 17 17:47:23 UTC 2017


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


More information about the freebsd-current mailing list