From owner-freebsd-stable Sun Jun 10 16:51:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 5DA5737B401 for ; Sun, 10 Jun 2001 16:51:35 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f5B01k202445; Sun, 10 Jun 2001 17:01:53 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106110001.f5B01k202445@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Pete French Cc: stable@FreeBSD.ORG Subject: Re: Very odd clock problem In-reply-to: Your message of "Sat, 09 Jun 2001 14:30:55 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Jun 2001 17:01:46 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > One of our FreeBSD machine is starting to loose time very badly. Odd as it > is running ntp from 5 different servers. Its also not a small loss, the > clock jumps backwards to the year 1933 ! Anybody got any ideas or seen > anything similar ? Er, the system clock is not capable of representing the year 1933 (in any valid fashion). This sounds like either memory corruption or an in-kernel sniper bug of some sort. You don't help the diagnosis any by saying "losing time" and then complaining about a "jump". The two are very different things, and you need to be much more specific about what is actually happening. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message