Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Jun 2000 23:33:53 -0700
From:      Mike Smith <msmith@freebsd.org>
To:        Mike Smith <msmith@freebsd.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: microuptime() going backwards 
Message-ID:  <200006290633.XAA01381@mass.osd.bsdi.com>
In-Reply-To: Your message of "Tue, 27 Jun 2000 20:21:18 PDT." <200006280321.UAA00490@mass.osd.bsdi.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006290633.XAA01381>