From owner-freebsd-current@freebsd.org  Tue Jan 17 17:38:04 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A56DCB44C4
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue, 17 Jan 2017 17:38:04 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2666F1C92;
 Tue, 17 Jan 2017 17:38:04 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from hps2016.home.selasky.org (unknown [62.141.129.119])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id 61C6F1FE025;
 Tue, 17 Jan 2017 18:37:45 +0100 (CET)
Subject: Re: Strange issue after early AP startup
To: John Baldwin <jhb@freebsd.org>
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>
Cc: FreeBSD Current <freebsd-current@freebsd.org>,
 Konstantin Belousov <kib@freebsd.org>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <b4c47ee8-a545-b1b7-b25c-73d9fd9e9a12@selasky.org>
Date: Tue, 17 Jan 2017 18:37:27 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <2215603.KuBd8pM5Pm@ralph.baldwin.cx>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2017 17:38:04 -0000

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