Date: Sat, 26 Jul 2003 13:12:13 +0100 From: Scott Mitchell <scott+freebsd@fishballoon.org> To: arno@heho.snv.jussieu.fr Cc: freebsd-stable@freebsd.org Subject: Re: cvs pserver sig11 on 4.8-R Message-ID: <20030726121213.GA19771@llama.fishballoon.org> In-Reply-To: <wpwue5biz4.fsf@heho.snv.jussieu.fr> References: <20030723104631.GA11861@llama.fishballoon.org> <20030723140217.P92624@carver.gumbysoft.com> <20030725123959.GB6218@llama.fishballoon.org> <wpwue5biz4.fsf@heho.snv.jussieu.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 26, 2003 at 01:55:27PM +0200, arno@heho.snv.jussieu.fr wrote: > Scott Mitchell <scott+freebsd@fishballoon.org> writes: > > > On Wed, Jul 23, 2003 at 02:02:55PM -0700, Doug White wrote: > > > > > > Does the new machine have ECC memory? If not, it could be something as > > > simple as bad RAM in the new system. > > > > I've just done four successive buildworlds on this machine, one with -j4, > > just for fun. They all completed without complaint, so I'm reasonably > > confident there's no dodgy RAM here. > > I second your expereinces : I see the same on my laboratory > main server (Athlon 700) ever since cvs was updated from 1.10 > to 1.11 (4.7-R ?) : I've just had a look in the (freebsd.org) cvs logs -- it looks like FreeBSD was using cvs 1.11.1p1 for 4.5-R through 4.7-R, then moved to 1.11.2 and then 1.11.5 for 4.8-R. I have not seen this problem with any release before 4.8, although we skipped 4.7 entirely. That said, without knowing what the bug is, or even if there really is a bug, I'm not making any statements about which versions it appears in :-) In the dodgy RAM department, the diagnostic tools for the server board do seem to include a comprehensive RAM test, so I plan to give this and memtest86 a workout when I can schedule some downtime on the server. Will report back when that is done. Cheers, Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030726121213.GA19771>