From owner-freebsd-questions Tue Oct 23 11:51:31 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.ezwv.com (hermes.ezwv.com [208.163.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 0850B37B40F for ; Tue, 23 Oct 2001 11:51:21 -0700 (PDT) Received: from there (ip206102034072.dlup.ezwv.com [206.102.34.72]) by mail.ezwv.com (8.9.3/8.9.3) with SMTP id OAA02488 for ; Tue, 23 Oct 2001 14:51:18 -0400 Message-Id: <200110231851.OAA02488@mail.ezwv.com> Content-Type: text/plain; charset="iso-8859-1" From: Randy Pratt To: questions@FreeBSD.ORG Subject: microuptime and kern.timecounter.method Date: Tue, 23 Oct 2001 14:52:48 -0400 X-Mailer: KMail [version 1.3] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I resurrected my old 486DX2-66V for some lightweight server duties and installed 4.4-RELEASE. I would see the occasional message like: microuptime() went backwards (345.292246 -> 345.-695042607) The archives suggested recompiling the kernel to remove the apm option. That did not seem to do the trick. However, another post suggested: sysctl kern.timecounter.method=1 So far, things seem to be stable with no microuptime() messages (20 hrs). Now I'm searching for more information on what this accomplished and what other options are available for the kern.timecounter.method. The man page for sysctl didn't reference this variable. I'd appreciate any pointers to docs. Thanks, Randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message