From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 06:39:34 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4CF137B401 for ; Fri, 27 Jun 2003 06:39:34 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 372E643F75 for ; Fri, 27 Jun 2003 06:39:34 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h5RDd7KJ072623; Fri, 27 Jun 2003 09:39:07 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h5RDd6kO072620; Fri, 27 Jun 2003 09:39:07 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 27 Jun 2003 09:39:06 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Stijn Hoop In-Reply-To: <20030627115208.GC90536@pcwin002.win.tue.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: stable@freebsd.org Subject: Re: alternate system clock has died X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2003 13:39:35 -0000 On Fri, 27 Jun 2003, Stijn Hoop wrote: > I'm getting the message in the subject when I run systat -vm on a > lightly loaded server. Top shows interesting CPU usage %: > > CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% > idle > > Some Googling tells me that a fix for this went in around 1998 in > sys/i386/isa/clock.c, see > > http://www.geocrawler.com/archives/3/159/1998/7/0/777198/ > > (fix verified to be present in RELENG_4_8 which is what the machine is > running). > > Since I'm the only one with this problem I'm assuming some hardware > clock has died, but now I'm trying to find out which one exactly. Could > this have to do with the battery-backed CMOS clock? If so how can I know > for sure that that isn't working right? > > More information available on request. Many vendors have hardware diagnostic CD's available on their web sites that test various aspects of the system, such as the accuracy of the clock, the proper functioning of timers, etc. You might want to give one a spin. Also, if you have any identical (or very similar hardware) that does or does not exhibit the problem, that would be interesting also. Speaking of systat -vmstat, in the interrupts column, what is the interrupt count for the rtc and clk lines? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories