From owner-freebsd-questions@FreeBSD.ORG Sun May 18 16:50:50 2003 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 0D47337B401 for ; Sun, 18 May 2003 16:50:50 -0700 (PDT) Received: from postit.adam.com.au (postit.adam.com.au [203.2.124.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0626743F3F for ; Sun, 18 May 2003 16:50:49 -0700 (PDT) (envelope-from bastill@adam.com.au) Received: from lightning.adam.com.au (lightning.adam.com.au [203.2.124.20]) by postit.adam.com.au (8.12.9/8.12.9) with SMTP id h4INqh26091297 for ; Mon, 19 May 2003 09:22:44 +0930 (CST) Received: (qmail 77325 invoked from network); 18 May 2003 23:50:45 -0000 Received: from 202-6-151-210.ip.adam.com.au (HELO BAPhD.gihon.org.au) (202.6.151.210) by eden.adam.com.au with SMTP; 18 May 2003 23:50:45 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Brian Astill To: Shantanu Mahajan , freebsd-questions@freebsd.org Date: Mon, 19 May 2003 09:21:37 +0930 User-Agent: KMail/1.4.3 References: <20030518213036.GA1513@dhumketu.homeunix.net> In-Reply-To: <20030518213036.GA1513@dhumketu.homeunix.net> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200305190921.37403.bastill@adam.com.au> Subject: Re: mircouptime()??? 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: Sun, 18 May 2003 23:50:50 -0000 On Mon, 19 May 2003 07:00 am, Shantanu Mahajan wrote: > Hi! > =09I got the following msg. > > microuptime() went backwards (14208.429157 -> 13513.043743) > > =09what does it mean? should i have to worry? Of course you do! The phenomenon isn't "dangerous", but the lines=20 giving the error message given repeatedly and endlessly in your log=20 will fill up /var PDQ! In addition, strange things can happen to your=20 operation of apps due to memory access problems. The usual cause is a VIA chipset incompatibility. The usual cure is to=20 recompile your kernel with all reference to apm _removed_ (it isn't=20 enough to rely on the default "disabled" status). --=20 Regards, Brian