From owner-freebsd-stable@FreeBSD.ORG Sun May 20 19:38:17 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 75F4216A41F for ; Sun, 20 May 2007 19:38:17 +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 D51D413C480 for ; Sun, 20 May 2007 19:38:16 +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 l4KJc9os002137; Sun, 20 May 2007 21:38:14 +0200 (CEST) (envelope-from victor@bsdes.net) Date: Sun, 20 May 2007 21:38:09 +0200 From: Victor Balada Diaz To: Peter Jeremy Message-ID: <20070520193808.GA857@pato.euesrg02.net> References: <20070520162630.GA1481@pato.euesrg02.net> <20070520191123.GR1164@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: <20070520191123.GR1164@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]); Sun, 20 May 2007 21:38:14 +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: Sun, 20 May 2007 19:38:17 -0000 On Mon, May 21, 2007 at 05:11:23AM +1000, Peter Jeremy wrote: > On 2007-May-20 18:26:30 +0200, Victor Balada Diaz wrote: > >I have a server with FreeBSD 6.2 that is not generating RTC IRQs. > >When the system boots everything it's working fine and I get 128 > >interrupts per second but after a few hours the system starts > >losing RTC interrupts. If I enable powerd it happens much faster > >than without it. > > The RTC has a "feature" that if you ever lose an RTC interrupt > (because the interrupt handler wasn't called fast enough), you don't > get any more interrupts because the RTC knows it has an interrupt > pending and so doesn't generate any more interrupts. > > I have also bumped into this problem whilst trying to work around > a problem with a TurionX2 CPU. I just got the correct fix to work > and ignored the work-around. > > I did find that you can restart the RTC interrupts by setting > machdep.adjkerntz (you can leave the value the same, it's the > assignment that's important). Thanks for your fast reply! 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. Do you know of any other workaround/patch that i can try? -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros.