From owner-freebsd-current@freebsd.org  Tue Oct 17 00:12:56 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 00FEFE49584
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue, 17 Oct 2017 00:12:56 +0000 (UTC)
 (envelope-from bsd-lists@bsdforge.com)
Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com
 [24.113.41.81])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 78801734BE
 for <freebsd-current@freebsd.org>; Tue, 17 Oct 2017 00:12:54 +0000 (UTC)
 (envelope-from bsd-lists@bsdforge.com)
Received: from ultimatedns.net (localhost [127.0.0.1])
 by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v9H0DMlE036597
 for <freebsd-current@freebsd.org>; Mon, 16 Oct 2017 17:13:28 -0700 (PDT)
 (envelope-from bsd-lists@bsdforge.com)
To: "FreeBSD CURRENT" <freebsd-current@freebsd.org>
From: "Chris H" <bsd-lists@bsdforge.com>
Subject: Is there an RTC prejudice?
Date: Mon, 16 Oct 2017 17:13:28 -0700
Content-Type: text/plain; charset=UTF-8; format=fixed
MIME-Version: 1.0
Message-id: <0f019102c38d089d28510c75f3450349@ultimatedns.net>
Content-Transfer-Encoding: 8bit
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 Oct 2017 00:12:56 -0000

While I haven't [yet] experienced this problem. A bug[1] just came in
on the amd64 list that is over a *year old*, and there are several
individuals involved. As well as several [freebsd] versions. So I
thought I'd raise the issue here. In case someone(tm) thinks they
know what's wrong/ what to do.

1: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207677

--Chris