From owner-cvs-src@FreeBSD.ORG Fri Feb 4 22:12:24 2005 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F39DB16A4CE for ; Fri, 4 Feb 2005 22:12:23 +0000 (GMT) Received: from mail23.sea5.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58C5143D54 for ; Fri, 4 Feb 2005 22:12:23 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 30523 invoked from network); 4 Feb 2005 22:12:23 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 4 Feb 2005 22:12:22 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j14MCGNJ065270; Fri, 4 Feb 2005 17:12:17 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: David Malone Date: Fri, 4 Feb 2005 14:53:56 -0500 User-Agent: KMail/1.6.2 References: <200502031906.j13J63fl055269@repoman.freebsd.org> <20050204101033.GA35920@walton.maths.tcd.ie> In-Reply-To: <20050204101033.GA35920@walton.maths.tcd.ie> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200502041453.56421.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/isa clock.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Feb 2005 22:12:24 -0000 On Friday 04 February 2005 05:10 am, David Malone wrote: > On Thu, Feb 03, 2005 at 07:06:03PM +0000, John Baldwin wrote: > > Log: > > Anytime we write to the RTC's status B register to possibly enable > > interrupts, read from the interrupt status register to clear any > > pending interrupts. Otherwise in some rare cases the RTC would never > > fire any interrupts as it constantly thinks it has an interrupt pending. > > Do you think there's any link between this and the occasional > problems people have reported over the years where the RTC stops > firing and they stop getting CPU usage stats? I'm not sure. The part of this patch that was in PR 17800 didn't fix another PR I didn't list on boxes where the clock does go away. According to that PR running 'date' to set the date and time turns the interrupt back on though. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org