From owner-freebsd-stable Wed Jun 28 23:27:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (ppp-247.dialup.clari.net.au [203.57.253.247]) by hub.freebsd.org (Postfix) with ESMTP id 7A5C337BB23; Wed, 28 Jun 2000 23:27:28 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id XAA01381; Wed, 28 Jun 2000 23:33:54 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200006290633.XAA01381@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: freebsd-stable@freebsd.org Subject: Re: microuptime() going backwards In-reply-to: Your message of "Tue, 27 Jun 2000 20:21:18 PDT." <200006280321.UAA00490@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Jun 2000 23:33:53 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > System is an Athlon 700Mc, dmesg.boot available if required. > > > > > > Any idea what is causing this? > > > > Yup. Is this an Epox board? I think it's a bug in the APM code. It > > even bites if APM is disabled. Try completely removing APM from the > > kernel. > > I explained this to you at Usenix, actually. It has nothing to do with > APM, it has to do with the selection of clocks available with/without APM > compiled into the kernel - there is probably either a bug in the TSC > hardware on this CPU, or (more likely) a bug in the timecounter code > (since people see this on !APM systems already). s/TSC hardware/i8254 hardware/ (the TSC is disabled when APM is compiled in, and this forces the use of the i8254) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message