From owner-freebsd-hackers@FreeBSD.ORG  Thu May  8 13:11:44 2003
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1619437B401
	for <freebsd-hackers@freebsd.org>;
	Thu,  8 May 2003 13:11:44 -0700 (PDT)
Received: from upright.CS.Princeton.EDU (upright.CS.Princeton.EDU
	[128.112.136.7])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0F48843F93
	for <freebsd-hackers@freebsd.org>;
	Thu,  8 May 2003 13:11:43 -0700 (PDT)
	(envelope-from lai@CS.Princeton.EDU)
Received: from opus (opus.CS.Princeton.EDU [128.112.169.45])
	h48KBSF22517verified NO);	Thu, 8 May 2003 16:11:29 -0400 (EDT)
Date: Thu, 8 May 2003 16:11:28 -0400 (EDT)
From: Junwen Lai <lai@CS.Princeton.EDU>
To: thib <thib@bitcode.org>
In-Reply-To: <20030508202337.79393d62.thib@bitcode.org>
Message-ID: <Pine.LNX.4.44.0305081610480.29779-100000@opus.CS.Princeton.EDU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-hackers@freebsd.org
Subject: Re: microuptime() went backwards.
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 May 2003 20:11:44 -0000

this happens when you change the system time, either by running "time" 
explicitly or using something like ntptime. Not a big deal, just ignore 
it.

> May  8 20:01:51 FeliX /kernel: microuptime() went backwards (39515.922679 -> 15.898650)
> 
> I had proplems with this same thing when I was running 4.5 but it stoped in 4.8-STABLE but now all of the sudden it came back
> I have looked throug the archives and found nothing wich can help me understand why this happend all of the sudden or how I can prevented from
> happing. I can asure that I made no changes to my system configuration nor installed any packages e.t.c. e.t.c. but all of the sudden I started getting this msg in /var/log/messages . 
> 
> Any feedback on what could be causing this and how to fix it or suggestions on where too look for more detailed info about this subject.
> 
> 
> P.S.
> 	If you find that this should not be send to -hackers excuse me for -hackers is the only list that I'm subscriped to and I hate to have thing's CC to me.
> 
> Regards,
> 	Thordur Ivar.
>