From owner-freebsd-questions@FreeBSD.ORG Thu May 19 22:30:00 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E93B316A4CF for ; Thu, 19 May 2005 22:30:00 +0000 (GMT) Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0971143D1D for ; Thu, 19 May 2005 22:30:00 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from localhost.i.cz (ss.eunet.cz [193.85.228.13]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id j4JMTwiv077312 for ; Fri, 20 May 2005 00:29:58 +0200 (CEST) (envelope-from mime@traveller.cz) From: Michal Mertl To: freebsd-questions@freebsd.org In-Reply-To: <1115851048.875.2.camel@genius1.i.cz> References: <1115851048.875.2.camel@genius1.i.cz> Content-Type: text/plain Date: Fri, 20 May 2005 00:29:57 +0200 Message-Id: <1116541797.2958.19.camel@genius1.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: NTP issues with 5.4 (SOLVED) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2005 22:30:01 -0000 I wrote: > Hello, > > I run ntpd in daemon mode on several FreeBSD computers and synchronize > with 'ntpd -q' all others. > > I've just updated one machine to 5.4 (from 5.3) and noticed the daemon > was unhappy, often logging 'time reset' and resynchronizing with peers. > On other machines I also only recently (after the upgrade to 5.4) see > ntp problems - 'ntpd -q' gets stuck and time goes off. The machines were > all fine before. > > I searched the web and archives and found some more people complaining > about similar issues but I haven't found any good answer. At first I > thought it was happening only on SMP computers but it isn't the case. > The machines have all kinds of timecounters - ACPI-fast, ACPI-safe and > i8254. I'd like to let you all know that I don't think the problem is as widespread as I originally thought. After tens of restarts of ntpd processes I've never experienced any problem synchronizing. No more hung 'ntpd -q' processes either. I suspect the latter was a consequence of my server having problems synchronizing. Michal