From owner-freebsd-current@FreeBSD.ORG  Thu Feb 12 03:48:18 2015
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id F1FDBBE4
 for <freebsd-current@freebsd.org>; Thu, 12 Feb 2015 03:48:18 +0000 (UTC)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com
 [IPv6:2a00:1450:4010:c04::234])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 8E51DD3E
 for <freebsd-current@freebsd.org>; Thu, 12 Feb 2015 03:48:18 +0000 (UTC)
Received: by mail-lb0-f180.google.com with SMTP id z12so7160539lbi.11
 for <freebsd-current@freebsd.org>; Wed, 11 Feb 2015 19:48:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=u6iCEYb9+afKLSOW85dNPhtDV4pOpHfL7Q0a4O+eANE=;
 b=UNS5Z5dHDEY/JJ2i5tiqjirh3FToYcGrLwXOlIe6zuyoR6j2aQCHjVNG/vGZSEfwXQ
 N3aj2F3d7ibg9UB8pc1KjPx+zNLWsOX6gGMEFd11hzMAa3slE4yi5409mNMwkHyZvaU6
 bzHwCAC7cp2HltDGposdLJUo9Eujxfx5UALmxIja9VkR4uSTMTFZ70FaOy/a3/LNQ9Pf
 YcXeU2rk+s16/IMhKHbCS4+uVXgmlApyBuy94VkKrfBp0fkT+hbAxSLZZZ30S0cMAVyR
 H5+N7ycYSySQpDJK9gnCoT4UBUbkLCvVU+ytAMZE78r+iFBra24LWhMPV6m998POAqWa
 z6uA==
MIME-Version: 1.0
X-Received: by 10.152.18.133 with SMTP id w5mr1400911lad.51.1423712896505;
 Wed, 11 Feb 2015 19:48:16 -0800 (PST)
Received: by 10.114.78.131 with HTTP; Wed, 11 Feb 2015 19:48:16 -0800 (PST)
In-Reply-To: <986ce3d13a4789f4e64d24cd54f43869@ultimatedns.net>
References: <986ce3d13a4789f4e64d24cd54f43869@ultimatedns.net>
Date: Wed, 11 Feb 2015 22:48:16 -0500
Message-ID: <CAFMmRNxt2kZEhEye+HRqWknmOx7t4tVAE9XaZN+D3kzj7pnP4g@mail.gmail.com>
Subject: Re: Has the counter/tic been resolved?
From: Ryan Stone <rysto32@gmail.com>
To: Chris H <bsd-lists@bsdforge.com>
Content-Type: text/plain; charset=UTF-8
Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Feb 2015 03:48:19 -0000

Is this the issue that you're referring to?

https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054295.html

If so, it was fixed in r278229:
https://svnweb.freebsd.org/changeset/base/278229