From owner-freebsd-stable@FreeBSD.ORG Thu Jun 14 21:22:30 2007 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A11CD16A400 for ; Thu, 14 Jun 2007 21:22:30 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id 0D6D713C448 for ; Thu, 14 Jun 2007 21:22:29 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (pato.euesrg02.net [192.168.0.3]) by alf.dyndns.ws (8.13.1/8.13.1) with ESMTP id l5ELMLat007664; Thu, 14 Jun 2007 23:22:27 +0200 (CEST) (envelope-from victor@bsdes.net) Date: Thu, 14 Jun 2007 23:22:21 +0200 From: Victor Balada Diaz To: Peter Jeremy Message-ID: <20070614212220.GB4246@pato.euesrg02.net> References: <20070520162630.GA1481@pato.euesrg02.net> <20070520191123.GR1164@turion.vk2pj.dyndns.org> <20070520193808.GA857@pato.euesrg02.net> <20070521065532.GC1143@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20070521065532.GC1143@turion.vk2pj.dyndns.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (alf.dyndns.ws [217.126.240.244]); Thu, 14 Jun 2007 23:22:27 +0200 (CEST) Cc: stable@freebsd.org Subject: Re: RTC clock doesn't generate interrupts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2007 21:22:30 -0000 On Mon, May 21, 2007 at 04:55:32PM +1000, Peter Jeremy wrote: > On 2007-May-20 21:38:09 +0200, Victor Balada Diaz wrote: > >I tried the machdep.adjkerntz trick and didn't work very well. > >If i'm on 0 irqs per second after changing the value i get 1 > >irq per second. If i'm on 20 i get 21, and so on. > > The machdep.adjkerntz trick works by reading the status register - > which implicitly acknowledges the interrupt and allows further > interrupts to be generated. I can't explain how this would effectivly > increase the interrupt frequency by 1Hz. Is is possible your CMOS > battery is dead? After waiting a few days to be sure the problem doesn't happen again I can confirm that the problem was that the CMOS battery was dead. Changed it and now it's working without any problems. Is there any guide out there for tracking hardware failures? I think that a chapter about hardware related problems could be a great addition to the handbook. Thanks a lot for your help! -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros.