From owner-freebsd-current Fri Sep 8 13:45: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 919B437B43E; Fri, 8 Sep 2000 13:45:01 -0700 (PDT) Received: from rac1.wam.umd.edu (IDENT:root@rac1.wam.umd.edu [128.8.10.141]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id QAA07014; Fri, 8 Sep 2000 16:44:37 -0400 (EDT) Received: from rac1.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id QAA25295; Fri, 8 Sep 2000 16:44:37 -0400 (EDT) Received: from localhost (culverk@localhost) by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id QAA25288; Fri, 8 Sep 2000 16:44:37 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Fri, 8 Sep 2000 16:44:37 -0400 (EDT) From: Kenneth Wayne Culver To: Poul-Henning Kamp Cc: Mike Smith , Greg Lehey , John Baldwin , Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards In-Reply-To: <82049.968442173@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could all this be in any way related to the statclock not working on certain systems (like my Dell Inspiron)?? Also, could the "rtc" device as listed in systat -vm not being there (I'm assuming this is the statclock) be causing scheduling anomalies? I ask because I am trying to get gaim (multi-threaded, and using gtk which is threaded as well) to work on my laptop. It works on my desktop (-CURRENT), and on my friend's desktop (-STABLE) but not on my laptop (-STABLE). Just wondering... Thanks. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Fri, 8 Sep 2000, Poul-Henning Kamp wrote: > In message <200009080543.WAA01815@mass.osd.bsdi.com>, Mike Smith writes: > >> > Sep 7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980 -> 10412, -694583121)y > >> > > >> > this is bad.. right ? :-) > >> > >> Well, at any rate it looks very funny. If this is a laptop, try > >> building a kernel without apm and see if that helps. > > > >It only helps "hide" the problem. There's either *extremely* bogus data > >coming in, or an arithmetic or sequencing error that's allowing a corrupt > >timecounter to be seen. > > > >It might help to see the negative number as hex... > > I have collected all the emails I've received and I have identified > at least two different causes: > > There is a bogus i8254 implementation on certain Athlon Mobos, this > is a non-brainer since they should not use the i8254 but the TSC. > > There are negative numbers coming in from both the i8254 and in a > few cases from the TSC. NTIMECOUNTER may be too low for certain > systems, I'm still waiting for some feedback on that. > > Either way, I have a patch which I need to burn in in my lab, but > right now I have a hard time getting my SMP box to even print out > "Copyright..." when it boots :-( > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD coreteam member | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message