Re: Strange issue after early AP startup

From: Hans Petter Selasky <hps_at_selasky.org>
Date: Tue, 17 Jan 2017 18:46:40 +0100
On 01/17/17 16:50, John Baldwin wrote:
> Index: kern_clocksource.c
> ===================================================================
> --- kern_clocksource.c	(revision 312301)
> +++ kern_clocksource.c	(working copy)
> _at__at_ -503,7 +503,12 _at__at_ 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
> _at__at_ -511,8 +516,6 _at__at_ 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
Received on Tue Jan 17 2017 - 16:47:23 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:09 UTC