Date: Wed, 22 Jun 2005 10:57:47 -0400 From: John Baldwin <jhb@FreeBSD.org> To: Jens Schweikhardt <schweikh@schweikhardt.net> Cc: freebsd-current@FreeBSD.org Subject: Re: Timekeeping hosed by factor 3, high lapic[01] interrupt rates Message-ID: <200506221057.48595.jhb@FreeBSD.org> In-Reply-To: <20050621195113.GB840@schweikhardt.net> References: <20050516113420.GA786@schweikhardt.net> <200506201344.10176.jhb@FreeBSD.org> <20050621195113.GB840@schweikhardt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 21 June 2005 03:51 pm, Jens Schweikhardt wrote: > John, > > # > See > http://lists.freebsd.org/pipermail/freebsd-current/2005-May/050210.html # > > for the whole thread. > # > # I did glance over it, but I don't really have time to read every e-mail > on # current@ in detail. :( Do you have verbose dmesg's for both cases? > If so, # can you get the 'lapic: Divisor' lines from each boot? > > Sure, they are the same: > lapic: Divisor 2, Frequency 99829738 hz > > It appears Chris Gilbert has the same problem, see "Timekeeping gone > whack in 6-CURRENT" on this list. Ok, this is weird. Does this happen if you disable SMP via 'kern.smp.disabled=1' from the loader? UP has more timecounters available for use, so I'm curious if this is a problem with the 8254 timecounter code for some reason. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506221057.48595.jhb>