Date: Mon, 18 Oct 2004 23:25:23 +0200 From: Marius Strobl <marius@alchemy.franken.de> To: Herve Boulouis <amon@sockar.homeip.net> Cc: freebsd-sparc64@freebsd.org Subject: Re: Strange timing problems with BETA7 Message-ID: <20041018232523.B12117@newtrinity.zeist.de> In-Reply-To: <20041018112424.A81638@ra.aabs>; from amon@sockar.homeip.net on Mon, Oct 18, 2004 at 11:24:24AM %2B0200 References: <20041014114647.A69222@ra.aabs> <20041014125330.GB3528@electra.cse.Buffalo.EDU> <20041014150624.B69222@ra.aabs> <20041014131929.GD3528@electra.cse.Buffalo.EDU> <20041015105439.A79558@ra.aabs> <20041015155748.A4506@newtrinity.zeist.de> <20041015173329.B79558@ra.aabs> <20041015174637.L7898@newtrinity.zeist.de> <20041018112424.A81638@ra.aabs>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 18, 2004 at 11:24:24AM +0200, Herve Boulouis wrote: > Le 15/10/2004 à 17:46, Marius Strobl a écrit: > > On Fri, Oct 15, 2004 at 05:33:29PM +0200, Herve Boulouis wrote: > > > Le 15/10/2004 à 15:57, Marius Strobl a écrit: > > > > > > > > Are there other problems like time elapsing too fast on that machine? > > > > > > I've not really paid attention to that so I will keep an eye on it > > > and I'll tell you in a few hours. > > > > > > > Thanks. But unfortunately I got it backwards, time would have to elapse > > too slow if it is the problem that I'm suspecting. > > Well, after 2 days of uptime and some activity all the symptoms are gone, > and no date problems. > > The thing I don't understand is that I cvsuped on Oct 14, rebooted with > new world & kernel, left the machine running for 12 hours, saw the problems > (stucked ping & netstat, power cycle necessary to reboot, ...) reappear, rebooted the > box Oct 15 and nothing since. The only thing I changed on the last reboot was > to put back debug.mpsafenet to 1. > > In all cases thanks to all for your help. > There's potential for problems with the counter-timer which should be fixed but this doesn't seem to have been the cause of your problems. I'm not sure if debug.mpsafenet=0 can cause such effects. OTOH I'm running -current with debug.mpsafenet=1 on an U60 (should be the same mainboard as your Netra t 1125) and haven't seen such problems but in -current John Baldwin also reworked how the kernel handles process times which also could take of these problems. Marius
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041018232523.B12117>