From owner-freebsd-bugs@FreeBSD.ORG Mon Aug 4 03:20:11 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3744237B401 for ; Mon, 4 Aug 2003 03:20:11 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE2E543FB1 for ; Mon, 4 Aug 2003 03:20:10 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h74AKAUp089068 for ; Mon, 4 Aug 2003 03:20:10 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h74AKAVf089067; Mon, 4 Aug 2003 03:20:10 -0700 (PDT) Date: Mon, 4 Aug 2003 03:20:10 -0700 (PDT) Message-Id: <200308041020.h74AKAVf089067@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Scott Mitchell Subject: Re: bin/54854: cvs pserver sig11 crash on 4.8-R X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Scott Mitchell List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2003 10:20:11 -0000 The following reply was made to PR bin/54854; it has been noted by GNATS. From: Scott Mitchell To: FreeBSD-gnats-submit@FreeBSD.org Cc: Subject: Re: bin/54854: cvs pserver sig11 crash on 4.8-R Date: Mon, 4 Aug 2003 11:09:42 +0100 OK, I've run memtest86 on this machine for most of the weekend - it got through 37 loops of its extended test suite and found zero errors. So I'm as confident as I'm ever going to be that there are no hardware issues with the machine. I've been advised by one of the CVS developers to try a newer version of CVS from their repository, without the FreeBSD extensions. They have seen this behaviour before at a few sites, although it mostly seems to be related to using older clients with recent servers, which is not exactly what I have been seeing (it happens with new clients as well). Anyway, I'll try to get a newer release built and see what happens. Scott