From owner-freebsd-current@freebsd.org  Mon Jan 16 15:52:26 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 B33B0CB2AAE
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 16 Jan 2017 15:52:26 +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 70B291E8F;
 Mon, 16 Jan 2017 15:52:26 +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 B78BF1FE025;
 Mon, 16 Jan 2017 16:52:01 +0100 (CET)
From: Hans Petter Selasky <hps@selasky.org>
Subject: Strange issue after early AP startup
To: FreeBSD Current <freebsd-current@freebsd.org>,
 John Baldwin <jhb@freebsd.org>, Konstantin Belousov <kib@FreeBSD.org>
Message-ID: <b9c53237-4b1a-a140-f692-bf5837060b18@selasky.org>
Date: Mon, 16 Jan 2017 16:51:42 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; 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: Mon, 16 Jan 2017 15:52:26 -0000

Hi,

When booting I observe an additional 30-second delay after this print:

> Timecounters tick every 1.000 msec

~30 second delay and boot continues like normal.

Checking "vmstat -i" reveals that some timers have been running loose.

> cpu0:timer                         44300        442
> cpu1:timer                         40561        404
> cpu3:timer                      48462822     483058
> cpu2:timer                      48477898     483209

Trying to add delays and/or prints around the Timecounters printout 
makes the issue go away. Any ideas for debugging?

Looks like a startup race to me.

--HPS