From owner-freebsd-current Wed Dec 15 7:44:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D7DC314A1B for ; Wed, 15 Dec 1999 07:44:39 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id QAA10387; Wed, 15 Dec 1999 16:44:19 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Khetan Gajjar Cc: current@FreeBSD.ORG Subject: Re: microuptime problem/error ? In-reply-to: Your message of "Wed, 15 Dec 1999 17:09:15 +0200." Date: Wed, 15 Dec 1999 16:44:19 +0100 Message-ID: <10385.945272659@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please send me the output of the following: xntpdc -c loopinfo xntpdc -c kerninfo xntpdc -c peer Poul-Henning In message , Khetan Gajjar writes: >Hi. > >I've started seeing "microuptime() went backwards" errors, followed >by calcru errors. I think it's related to phk's commit of >kern_resource.c (1.53) and kern_synch.c (1.84). > >What I don't understand is how is this possible if I'm using >xntpd to keep time, and my machine is reporting itself as a >stratum 3 server ? I have included three examples of the >microuptime and calcru error, and the output of ntptrace. > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message