From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 14:41:48 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 AF8F037B401 for ; Wed, 23 Jul 2003 14:41:48 -0700 (PDT) Received: from mta06-svc.ntlworld.com (mta06-svc.ntlworld.com [62.253.162.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8490B43F3F for ; Wed, 23 Jul 2003 14:41:47 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.199]) by mta06-svc.ntlworld.comESMTP <20030723214144.SBAU16215.mta06-svc.ntlworld.com@llama.fishballoon.org>; Wed, 23 Jul 2003 22:41:44 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 19fRM4-0004Mu-0Q; Wed, 23 Jul 2003 22:41:00 +0100 Date: Wed, 23 Jul 2003 22:40:59 +0100 From: Scott Mitchell To: Doug White Message-ID: <20030723214059.GA16594@llama.fishballoon.org> References: <20030723104631.GA11861@llama.fishballoon.org> <20030723140217.P92624@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030723140217.P92624@carver.gumbysoft.com> 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: Wed, 23 Jul 2003 21:41:49 -0000 On Wed, Jul 23, 2003 at 02:02:55PM -0700, Doug White wrote: > On Wed, 23 Jul 2003, Scott Mitchell wrote: > > > We recently moved our CVS repository from a 4.6-STABLE machine to a brand > > new 4.8 install, on another identical machine. The server runs cvs in > > 'pserver' mode, for remote access by various Windows/Solaris/Linux/FreeBSD > > clients. > > > > We pretty soon noticed that the cvs server process was occasionally crashing > > on sig11 (ie. a segfault). > > Does the new machine have ECC memory? If not, it could be something as > simple as bad RAM in the new system. It does have ECC, as does the old machine. Bad RAM was my first thought, too, but surely that's a bit unlikely when it's only one program that crashes, and always at *exactly* the same point in the code... The machine is due for a RAM upgrade anyway, so maybe I'll swap the whole lot out and see if that makes any difference, but I'm not hopeful. Scott