From owner-freebsd-current Fri Dec 10 23:59: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id DE48614D04 for ; Fri, 10 Dec 1999 23:59:00 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA12509; Sat, 11 Dec 1999 08:58:53 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kenneth Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: timecounter In-reply-to: Your message of "Sat, 11 Dec 1999 01:44:53 EST." Date: Sat, 11 Dec 1999 08:58:53 +0100 Message-ID: <12507.944899133@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The rtc is not a timecounter, and I doubt the the problem is related to timecounters at all. The RTC is always detected, because we know it is there, but it may be that you don't get any interrupts from it, I don't know why that might be. Poul-Henning In message , Ke nneth Culver writes: >I am not sure the timecounters are being detected properly on my home >computer. A while back (around August) -CURRENT's kernel detected 2 >timecounters, and using systat -vm, I could see clk generating 100 >interrupts (I'm assuming per second) and rtc0 generating about 128 per >second. Around the time we changed over to gcc-2.95.2, I noticed that rtc0 >is no longer detected, and only one timecounter is detected at boot. The >bad effect of this is that the system doesn't accurately show the cpu >usage. Any suggestions on how to fix this, or pointers to where the >cpu_initclocks() function would be nice :-) Thanks > > >================================================================= >| Kenneth Culver | FreeBSD: The best OS around. | >| Unix Systems Administrator | ICQ #: 24767726 | >| and student at The | AIM: AgRSkaterq | >| The University of Maryland, | Website: (Under Construction) | >| College Park. | http://www.wam.umd.edu/~culverk/| >================================================================= > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message