From owner-freebsd-questions@FreeBSD.ORG Tue Mar 4 09:37:38 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3C5CA322 for ; Tue, 4 Mar 2014 09:37:38 +0000 (UTC) Received: from eu1sys200aog114.obsmtp.com (eu1sys200aog114.obsmtp.com [207.126.144.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DAE98A00 for ; Tue, 4 Mar 2014 09:37:36 +0000 (UTC) Received: from mail-wg0-f51.google.com ([74.125.82.51]) (using TLSv1) by eu1sys200aob114.postini.com ([207.126.147.11]) with SMTP ID DSNKUxWe3uNfARioEizMFIzkimuz7YtRqMyT@postini.com; Tue, 04 Mar 2014 09:37:36 UTC Received: by mail-wg0-f51.google.com with SMTP id a1so4566582wgh.34 for ; Tue, 04 Mar 2014 01:37:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:message-id:to:subject:cc :reply-to:in-reply-to; bh=R3jaiSWJM1rEe0xVf7q9jZDwe8hdlJ+n6SJ2aNB5TJc=; b=fabqublLP5zSn3pyHrF96dI6WDfsBoDvkv1N2NFeAEj6sOdvOIRGYCWjoHefub5tYw BxeoTVEGpWS2BnrKjWD6IsQu9IOFOivGzyEsSehyH1l2oxjcwto3gjilOB1x2GPaVAZh O5BZ1dH9SE8DABHhssdiwOxFiG0ulNG/KbH+ebRVeCCXJoCyh2+pvMOY9mwvFykpWnkI kPU8iflhDJEqEDzSDfPorZjM333gsmEaK+Sm9p/1+f1fcYp5zesyztb4W+ydAYBcN/mx 8Jh1RZQUtMMEKBxL04STG2hidxJmTu+SjqghpwUHP2UfQl9SgrPqNowJuGIUWRt7ELo+ VSuA== X-Gm-Message-State: ALoCoQnA5bNTrUvZGM7YfBfQXfM1Fj9ozMZm8rEu+NLvxqJqJ4XPx67VvvDvAikvskUvuZ58g+g5lR2xG+qotuZlujnT6a4hW6A9RztJ7H2dRF13mf8xqBprNYnGC1DTrQ62oA7JApAabSp+qxCQjCZtBwpXp5nORrlNKWJPS9xwBbqfnYqu48zWv7CX3lGxuLL6eTqCijje X-Received: by 10.194.109.68 with SMTP id hq4mr25962977wjb.12.1393925854730; Tue, 04 Mar 2014 01:37:34 -0800 (PST) X-Received: by 10.194.109.68 with SMTP id hq4mr25962968wjb.12.1393925854646; Tue, 04 Mar 2014 01:37:34 -0800 (PST) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id xt1sm49440521wjb.17.2014.03.04.01.37.32 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Mar 2014 01:37:33 -0800 (PST) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id s249bVIe042312 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 4 Mar 2014 09:37:31 GMT (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id s249bV9V042311; Tue, 4 Mar 2014 09:37:31 GMT (envelope-from mexas) Date: Tue, 04 Mar 2014 01:37:33 -0800 (PST) From: Anton Shterenlikht Message-Id: <201403040937.s249bV9V042311@mech-cluster241.men.bris.ac.uk> To: erichsfreebsdlist@alogt.com, mexas@bris.ac.uk Subject: Re: ntp frequent time resets - battery dead? In-Reply-To: <20140304171522.2934a2b8@X220.alogt.com> Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: mexas@bris.ac.uk List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Mar 2014 09:37:38 -0000 >From erichsfreebsdlist@alogt.com Tue Mar 4 09:29:39 2014 > >Hi, > >On Tue, 04 Mar 2014 01:07:25 -0800 (PST) >Anton Shterenlikht wrote: > >> >> I see in /var/log/messages: >> >> Mar 4 00:16:40 mech-anton240 ntpd[764]: time reset +0.291030 s >> Mar 4 00:38:02 mech-anton240 ntpd[764]: time reset +0.344745 s >> Mar 4 00:57:37 mech-anton240 ntpd[764]: time reset +0.338739 s >> Mar 4 01:19:45 mech-anton240 ntpd[764]: time reset +0.355020 s >> Mar 4 01:41:34 mech-anton240 ntpd[764]: time reset +0.365177 s >> Mar 4 01:58:41 mech-anton240 ntpd[764]: time reset +0.306982 s >> >> and so on. >> >> The correction seems large to me. >> Does this indicate that the battery is dead? > >do you reboot between? If not, it is not the battery but the quartz >used by the clock. no, no reboots at all. Please elaborate. I don't really understand you. >> >> This is on a Sun Blade 1500 silver desktop, >> about 10 years old. > >This also can happen on new hardware. But it would be real rare. Did >you check for dirt in the PCB? will do Anton