From owner-freebsd-questions Mon Oct 8 0:36: 3 2001 Delivered-To: freebsd-questions@freebsd.org Received: from kuku.excite.com (kuku-rwcmta.excite.com [198.3.99.63]) by hub.freebsd.org (Postfix) with ESMTP id 8837037B401 for ; Mon, 8 Oct 2001 00:35:59 -0700 (PDT) Received: from patti.excite.com ([199.172.148.159]) by kuku.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20011008073559.TFJE25815.kuku.excite.com@patti.excite.com> for ; Mon, 8 Oct 2001 00:35:59 -0700 Message-ID: <4738661.1002526559234.JavaMail.imail@patti.excite.com> Date: Mon, 8 Oct 2001 00:35:59 -0700 (PDT) From: Matt Sykes To: freebsd-questions@freebsd.org Subject: kernel SMP timer bug persists Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Excite Inbox X-Sender-Ip: 66.3.230.250 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG kernel: 4.4-STABLE motherboard: P2L97-DS (dual PII 300MHZ) top and ps give 0.00% cpu usage for all processes. cvsupping didn't help. LINT config file says # Notes on APM # The flags takes the following meaning for apm0: # 0x0020 Statclock is broken. # If apm is omitted, some systems require sysctl -w kern.timecounter.method=1 # for correct timekeeping. but all combinations of setting apm on/off and setting timecounter.method on/off do not correct the problem (I reboot into single-user for sysctl then reboot again to be sure). Been talked about in google some, but no resolution from what I've seen. There is a patch mentioned, but I am hoping for something less ad hoc; why wouldn't the patch appear from cvsup? Please CC my email if you reply. Thanks. _______________________________________________________ Send a cool gift with your E-Card http://www.bluemountain.com/giftcenter/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message