Date: Tue, 27 Jun 2000 20:21:18 -0700 From: Mike Smith <msmith@freebsd.org> To: Greg Lehey <grog@lemis.com> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: microuptime() going backwards Message-ID: <200006280321.UAA00490@mass.osd.bsdi.com> In-Reply-To: Your message of "Tue, 27 Jun 2000 12:03:49 %2B1000." <20000627120348.B5328@sydney.worldwide.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> [Format recovered--see http://www.lemis.com/email/email-format.html] > > On Monday, 26 June 2000 at 22:56:29 +0200, Wilko Bulte wrote: > > I just got tons and tons of > > > > Jun 26 22:06:33 freebie /kernel: microuptime() went backwards (18951.226366 -> 1 8951,199762) > > Jun 26 22:06:34 freebie /kernel: microuptime() went backwards (18951.226366 -> 1 8951,210275) > > > > (approx 10Mb worth of them). This was during a mpeg video playing operation. > > > > FreeBSD freebie.wbnet 4.0-STABLE FreeBSD 4.0-STABLE #2: Sat Jun 24 16:52:41 CEST 2000 root@freebie.wbnet:/usr/src/sys/compile/FREEBIE i386 > > > > 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). -- \\ 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006280321.UAA00490>