From owner-freebsd-stable@FreeBSD.ORG Sat Jul 26 04:55:37 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 1E4DA37B401 for ; Sat, 26 Jul 2003 04:55:37 -0700 (PDT) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id D750343F75 for ; Sat, 26 Jul 2003 04:55:35 -0700 (PDT) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.12.9/jtpda-5.4) with ESMTP id h6QBtSLJ096787 ; Sat, 26 Jul 2003 13:55:29 +0200 (CEST) Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) h6QBtR8C008792 ; Sat, 26 Jul 2003 13:55:27 +0200 (MEST) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.12.9/8.12.9/Submit) id h6QBtRGD008789; Sat, 26 Jul 2003 13:55:27 +0200 (MEST) To: Scott Mitchell References: <20030723104631.GA11861@llama.fishballoon.org> <20030723140217.P92624@carver.gumbysoft.com> <20030725123959.GB6218@llama.fishballoon.org> From: arno@heho.snv.jussieu.fr Date: 26 Jul 2003 13:55:27 +0200 In-Reply-To: <20030725123959.GB6218@llama.fishballoon.org> Message-ID: Lines: 41 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Antivirus: scanned by sophie at shiva.jussieu.fr 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 11:55:37 -0000 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 ?) : su-2.02# fgrep 'exited on signal' messages Jun 16 19:26:26 heho /kernel: pid 1344 (cvs), uid 21: exited on signal 11 Jun 16 19:26:29 heho /kernel: pid 1345 (cvs), uid 21: exited on signal 11 Jun 16 21:23:36 heho /kernel: pid 2094 (cvs), uid 118: exited on signal 11 Jun 17 10:42:51 heho /kernel: pid 5138 (cvs), uid 21: exited on signal 11 Jun 17 13:22:44 heho /kernel: pid 11959 (cvs), uid 134: exited on signal 11 Jun 17 13:22:49 heho /kernel: pid 11961 (cvs), uid 134: exited on signal 11 Jun 17 14:24:36 heho /kernel: pid 12314 (java), uid 134: exited on signal 6 (core dumped) Jun 30 02:02:43 heho /kernel: pid 23778 (cvs), uid 0: exited on signal 11 Jul 1 16:29:31 heho /kernel: pid 609 (cvs), uid 21: exited on signal 11 Jul 7 17:13:33 heho /kernel: pid 38639 (cvs), uid 21: exited on signal 11 Jul 18 16:07:36 heho /kernel: pid 73850 (cvs), uid 21: exited on signal 11 Jul 18 16:07:39 heho /kernel: pid 73851 (cvs), uid 21: exited on signal 11 Jul 19 20:57:59 heho /kernel: pid 83113 (cvs), uid 21: exited on signal 11 Jul 22 17:26:19 heho /kernel: pid 99828 (java), uid 134: exited on signal 6 (core dumped) All other server programs run flawlessly and I doubt seriously that the java core-dumps are related to hardware problems. I will rebuild world with the patch I applied in the 4-7 days and which was supposed to prevent leaving cvsd as CPU-bound zombie processes. Regards, Arno