Date: Thu, 14 Oct 2004 09:19:29 -0400 From: Ken Smith <kensmith@cse.Buffalo.EDU> To: Herve Boulouis <amon@sockar.homeip.net> Cc: freebsd-sparc64@freebsd.org Subject: Re: Strange timing problems with BETA7 Message-ID: <20041014131929.GD3528@electra.cse.Buffalo.EDU> In-Reply-To: <20041014150624.B69222@ra.aabs> References: <20041014114647.A69222@ra.aabs> <20041014125330.GB3528@electra.cse.Buffalo.EDU> <20041014150624.B69222@ra.aabs>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 14, 2004 at 03:06:24PM +0200, Herve Boulouis wrote:
> Le 14/10/2004 à 08:53, Ken Smith a écrit:
> >
> > initializing counter-timer
> > Timecounter "counter-timer" frequency 1000000 Hz quality 100
> > Timecounters tick every 10.000 msec
> >
> > I'm worried that you might not have 'counter-timer'.
>
> Here is the relevant part of my dmesg :
>
> FreeBSD 5.3-BETA7 #5: Tue Oct 5 11:50:48 CEST 2004
> root@netra:/usr/obj/usr/src/sys/NETRA
> WARNING: MPSAFE network stack disabled, expect reduced performance.
> Timecounter "tick" frequency 296036546 Hz quality 0
> real memory = 805306368 (768 MB)
> avail memory = 772554752 (736 MB)
> cpu0: Sun Microsystems UltraSparc-II Processor (296.04 MHz CPU)
> cpu1: Sun Microsystems UltraSparc-II Processor (296.04 MHz CPU)
> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
> nexus0: <Open Firmware Nexus device>
> pcib0: <U2P UPA-PCI bridge> on nexus0
> pcib0: Psycho, impl 0, version 4, ign 0x7c0, bus B
> pcib0: [FAST]
> pcib0: [GIANT-LOCKED]
> pcib0: [FAST]
> pcib0: [GIANT-LOCKED]
> pcib0: [FAST]
> initializing counter-timer
> Timecounter "counter-timer" frequency 1000000 Hz quality 0
> ...
> Timecounters tick every 10.000 msec
>
> Do not hesitate to ask if you need info or want me to test patches,
> this box is not in production.
>
Do you follow along with cvsup, or by doing full installs from
ISO's? This looks like the configuration before the final set
of timer related patches, I think the last chunk went in late
last week. If you cvsup now you should get everything. Your
case may actually be one of the ones that this set of patches
was supposed to help - if the system chooses to use your CPU's
timer as its primary timecounter it might cause problems because
we don't even attempt to keep the clocks on the individual CPUs
in sync. The last set of patches sets it up so that on MP
systems the "quality" of the CPU's timers gets demoted so that
other counters should wind up being chosen as the primary
timecounter (in this case "counter-timer" should always be
chosen).
--
Ken Smith
- From there to here, from here to | kensmith@cse.buffalo.edu
there, funny things are everywhere. |
- Theodore Geisel |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041014131929.GD3528>