From owner-freebsd-stable@FreeBSD.ORG Mon Oct 8 10:42:12 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9A208106566C for ; Mon, 8 Oct 2012 10:42:12 +0000 (UTC) (envelope-from apeiron@isuckatdomains.net) Received: from isuckatdomains.net (unknown [IPv6:2600:3c01:e000:4::1]) by mx1.freebsd.org (Postfix) with ESMTP id 803D08FC0A for ; Mon, 8 Oct 2012 10:42:12 +0000 (UTC) Received: from isuckatdomains.isuckatdomains.net (isuckatdomains.net [IPv6:2600:3c01:e000:4::1]) by isuckatdomains.net (Postfix) with ESMTPSA id 6BBC44588B for ; Mon, 8 Oct 2012 06:42:12 -0400 (EDT) Date: Mon, 8 Oct 2012 06:42:11 -0400 From: Chris Nehren To: freebsd-stable@freebsd.org Message-ID: <20121008104211.GG28769@isuckatdomains.isuckatdomains.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20121008040239.GE1967@funkthat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7DO5AaGCk89r4vaK" Content-Disposition: inline In-Reply-To: <20121008040239.GE1967@funkthat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: time keeps on slipping... slipping... 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: Mon, 08 Oct 2012 10:42:12 -0000 --7DO5AaGCk89r4vaK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 07, 2012 at 21:02:39 -0700 , John-Mark Gurney wrote: > I recently put together a new machine w/ a SuperMicro H8SCM and an > AMD Opteron 4228 HE... I've having an issue where the clock on the > machine skips around... The wierd part is that it's very sudden when > it happens... ntp sometimes brings it back, but it can't when the clock > gets too far ahread (1000 seconds), ntp dies... >=20 > In order to catch it happening, I ran a sleep 60 loop fetching time > from another server that keeps time correctly via: > while sleep 60; do echo -n h2:; nc h2 13; date; ntpdate h2.funkthat.com; = done >=20 > here are some snippits: > h2:Sun Oct 7 17:12:54 2012^M > Sun Oct 7 17:12:54 PDT 2012 > 7 Oct 17:12:54 ntpdate[31036]: the NTP socket is in use, exiting > h2:Sun Oct 7 17:13:48 2012^M > Sun Oct 7 17:20:21 PDT 2012 > 7 Oct 17:20:21 ntpdate[31045]: the NTP socket is in use, exiting >=20 > but then ntp brings it back in sync: > h2:Sun Oct 7 17:28:49 2012^M > Sun Oct 7 17:35:21 PDT 2012 > 7 Oct 17:35:21 ntpdate[31164]: the NTP socket is in use, exiting > h2:Sun Oct 7 17:29:49 2012^M > Sun Oct 7 17:29:49 PDT 2012 > 7 Oct 17:29:49 ntpdate[31170]: the NTP socket is in use, exiting >=20 > I have switched my timecounter to HPET to see if things are different... >=20 > Any clues? Looks like faulty hardware to me. You shouldn't need to work that hard to keep the clock in sync. Can you boot a livecd of e.g. Linux or OpenIndiana and reproduce the issue? --=20 Thanks and best regards, Chris Nehren --7DO5AaGCk89r4vaK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJQcq4CAAoJEB3ywRGrHAnQciAQAJjwGxUuxRWR46bAU6issx/f imuC1z6gaPUt5FqNZU+bb7gsmCH7d+tR3zUbkbF3M4ME87iTq6+dG4RONQVtiTdG Q3Rq42/afj8rqlFOkROi+8WQnvBPztM2bFMtE8GTU3K4IEcq2QdzzdaFiqZeUu3X 0jaSbB9eHWM1tgEQ+9JG6Mp7wRlFCfjoPYNTO7pMzgTNJNq+vLejOeOrOiiKJY5B PNXNfjdziHlikEKSifZvShl0q9dDjeJpt/7UipF+AjOUJtbrhJZxYOXjnvHtJLTD AaDivb85NEJizcP59386bwA8iWG74qZBjTrSTSAij10bipSZK9nHKRH5Z8WUaNQj 0ZRxYxQvOgi7EbBTFKRuX6dz1xJ1S4byXo1zYI2Xv++b1+Ns3rRT7UrvXVYSNTiO DU/8pT/gj1dNcLMKP8+6ho56jWlmD+S6nd9OdxejnEKm9xz40ASNR8K5vVyVAeSn UIIWQj5F7YRECYAS4CsrXmXJRtECxttI6EsBsmTn5t1WjWbqpjkRQQCS/HUfeznP VauvMgrMp1QLMdbBFOrCxxsGn+9jaZdtDORDAabG3loAu7nTyTBP9Lz5CZxLeL1/ lCfr3SSwz0s1E0FrlsA+Nx1jw86+iBMh+6WdNT3xcmnO/vuPZRQg+yDeVwFsvoni gMWdwVlkmX2oTmPR3IPp =SNei -----END PGP SIGNATURE----- --7DO5AaGCk89r4vaK--