From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 05:13:00 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4A7D37B401 for ; Sat, 26 Jul 2003 05:13:00 -0700 (PDT) Received: from mta05-svc.ntlworld.com (mta05-svc.ntlworld.com [62.253.162.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 597B343FA3 for ; Sat, 26 Jul 2003 05:12:59 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.199]) by mta05-svc.ntlworld.comESMTP <20030726121257.VGRK28183.mta05-svc.ntlworld.com@llama.fishballoon.org>; Sat, 26 Jul 2003 13:12:57 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 19gNuH-00059r-Bb; Sat, 26 Jul 2003 13:12:13 +0100 Date: Sat, 26 Jul 2003 13:12:13 +0100 From: Scott Mitchell To: arno@heho.snv.jussieu.fr Message-ID: <20030726121213.GA19771@llama.fishballoon.org> References: <20030723104631.GA11861@llama.fishballoon.org> <20030723140217.P92624@carver.gumbysoft.com> <20030725123959.GB6218@llama.fishballoon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell cc: freebsd-stable@freebsd.org Subject: Re: cvs pserver sig11 on 4.8-R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 12:13:01 -0000 On Sat, Jul 26, 2003 at 01:55:27PM +0200, arno@heho.snv.jussieu.fr wrote: > Scott Mitchell 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