From owner-freebsd-questions Tue Feb 20 10:37:33 2001 Delivered-To: freebsd-questions@freebsd.org Received: from bender.physast.uga.edu (bender.physast.uga.edu [128.192.19.61]) by hub.freebsd.org (Postfix) with ESMTP id E3A3937B401 for ; Tue, 20 Feb 2001 10:37:30 -0800 (PST) (envelope-from andy@bender.physast.uga.edu) Received: (from andy@localhost) by bender.physast.uga.edu (8.9.1/8.9.1) id NAA32692 for freebsd-questions@FreeBSD.ORG; Tue, 20 Feb 2001 13:37:28 -0500 Date: Tue, 20 Feb 2001 13:37:28 -0500 From: Andreas Schweitzer To: freebsd-questions@FreeBSD.ORG Subject: microuptime backwards (again) and galopping time Message-ID: <20010220133728.A25902@bender.physast.uga.edu> Reply-To: Andreas Schweitzer Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm another lucky individual who finds microuptime : went backwards on the console. Plus : the time is galopping ! it was increasing its idea of the time by about 1 minute per real second ... And the microuptime console messages were just flying over the screen. The system is an Athlon with 4.2BETA. This started under very heavy load including vinum. Before we had vinum, the machine was under heavy load, too and we did not have any problems for half a year. After the load dropped, the flying time was slowly approaching normal. After I power cycled the machine, everything is normal again (let's wait for the next heavy load). I power cycled it because I feared some hardware problem with the oscillator. I know : the solution is disable APM. But what about the galopping time ? Thanks Andreas -- Department of Physics & Astronomy and Center for Simulational Physics University of Georgia Phone ++1 (706) 542 5043 Athens, GA 30602-2451 Fax ++1 (706) 542 2492 USA http://dilbert.physast.uga.edu/~andy/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message