Date: Mon, 23 May 2005 23:01:41 +0200 From: Jens Schweikhardt <schweikh@schweikhardt.net> To: Doug White <dwhite@gumbysoft.com> Cc: freebsd-current@freebsd.org Subject: Re: Timekeeping hosed by factor 3, high lapic[01] interrupt rates Message-ID: <20050523210141.GA779@schweikhardt.net> In-Reply-To: <20050523175609.GA779@schweikhardt.net> References: <20050516113420.GA786@schweikhardt.net> <20050518150346.S87264@carver.gumbysoft.com> <20050519190129.GA1048@schweikhardt.net> <20050520122944.B8229@carver.gumbysoft.com> <20050521092857.GA847@schweikhardt.net> <20050522112845.S27009@carver.gumbysoft.com> <20050523175609.GA779@schweikhardt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
... # # 3. Backout rev 1.218 of src/sys/i386/isa/clock.c so the irq0 interrupt # # handler is reactivated and the RTC fiddled. # # Will do so next. I've nailed the change between March 6 and March 30. # 1.218 is from 2005/03/24 21:34:16, which would fit. We have a winner. Backing out 1.218 from a 2005/03/24 system does the trick, as well as a CURRENT without 1.218 (but 1.219-220 in there) bring back irq0 and time dilation is gone. All clocks work correctly. Now the question is: what is so special in my system so that I appear to be the only one to notice the problem? Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050523210141.GA779>