Date: Mon, 21 May 2007 16:55:32 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Victor Balada Diaz <victor@bsdes.net> Cc: stable@freebsd.org Subject: Re: RTC clock doesn't generate interrupts Message-ID: <20070521065532.GC1143@turion.vk2pj.dyndns.org> In-Reply-To: <20070520193808.GA857@pato.euesrg02.net> References: <20070520162630.GA1481@pato.euesrg02.net> <20070520191123.GR1164@turion.vk2pj.dyndns.org> <20070520193808.GA857@pato.euesrg02.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--rQ2U398070+RC21q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-May-20 21:38:09 +0200, Victor Balada Diaz <victor@bsdes.net> 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? >Do you know of any other workaround/patch that i can try? Setting the time/date will have the same effect. --=20 Peter Jeremy --rQ2U398070+RC21q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGUUJk/opHv/APuIcRAiYeAKCSYwdm7lbu3MUWsEP4cA1Rqoh6OQCgo7yW LWijL/VyLYy92I1VIGdr3gY= =0oYA -----END PGP SIGNATURE----- --rQ2U398070+RC21q--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070521065532.GC1143>