From owner-freebsd-bugs Wed Nov 14 2:50: 5 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4FA9737B405 for ; Wed, 14 Nov 2001 02:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id fAEAo1601837; Wed, 14 Nov 2001 02:50:01 -0800 (PST) (envelope-from gnats) Date: Wed, 14 Nov 2001 02:50:01 -0800 (PST) Message-Id: <200111141050.fAEAo1601837@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Malone Subject: Re: kern/31971: microuptime() went backwards when apm is already disabled in the kernel on intel CPU Reply-To: David Malone Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/31971; it has been noted by GNATS. From: David Malone To: Ming Zhang Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/31971: microuptime() went backwards when apm is already disabled in the kernel on intel CPU Date: Wed, 14 Nov 2001 10:41:55 +0000 On Tue, Nov 13, 2001 at 11:02:45PM -0800, Ming Zhang wrote: > >Description: > microuptime() went backwards (1569221.6122007 -> 1569220.755141) > > it happens every other 3-4 days. > > Machine is a PIII-650Mhz on ASUS CUV 4X > APM is already disabled from kernel (never was configured) > > Never seen this before upgrading to 4.4 Can you try running "sysctl kern.timecounter" and see what it outputs. You could try setting kern.timecounter.method to 1 or experimenting with kern.timecounter.hardware (which can probably be set to i8254 or TSC on your hardware). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message