From owner-freebsd-current Fri Dec 10 22:44:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 5D1CA14BF5 for ; Fri, 10 Dec 1999 22:44:55 -0800 (PST) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id BAA00372 for ; Sat, 11 Dec 1999 01:44:53 -0500 (EST) (envelope-from culverk@culverk.student.umd.edu) Date: Sat, 11 Dec 1999 01:44:53 -0500 (EST) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: timecounter 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 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