From owner-freebsd-stable@FreeBSD.ORG Fri Aug 13 23:06:47 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 35C381065693; Fri, 13 Aug 2010 23:06:47 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Fri, 13 Aug 2010 19:06:15 -0400 User-Agent: KMail/1.6.2 References: <20100813070333.CD62B5C43@hal10000.halplant.com> <20100813223645.GA53484@icarus.home.lan> <4C65CC1F.6010903@halplant.com> In-Reply-To: <4C65CC1F.6010903@halplant.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201008131906.38496.jkim@FreeBSD.org> Cc: Subject: Re: ts_to_ct flood on 8.1-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Aug 2010 23:06:47 -0000 On Friday 13 August 2010 06:50 pm, Andrew J. Caines wrote: > Jeremy, > > Thanks for the quick response. > > > The source/responsible code for the printing is in function > > clock_ts_to_ct() in: src/sys/kern/subr_clock.c > > I took a look at the code in an attempt to divine the reason for > the frequent messages, without success. > > Any idea why I see so many? I'm not aware of any special timing > related configuration. I do run ntpd, of course. In examples I've > found, others seem to get just the one ts_to_ct message. > > > 52 #define ct_debug bootverbose Are your systems booting > > verbosely? > > By default, yes. I'd like to keep it that way without having to > hack the source. Is there another option? If you are really annoyed by the messages, you may increase 'machdep.rtc_save_period' sysctl value to something larger. Default is 1,800 seconds or 30 minutes. Also, you can completely disable it by setting it to zero or 'machdep.disable_rtc_set' to non-zero value but I would not recommend it. Still, it doesn't explain why you are seeing the message more often, however. :-( Jung-uk Kim