From owner-freebsd-current@FreeBSD.ORG  Thu Jul 17 18:35:38 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id DAF4E37B401; Thu, 17 Jul 2003 18:35:38 -0700 (PDT)
Received: from HAL9000.homeunix.com (ip114.bella-vista.sfo.interquest.net
	[66.199.86.114])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2551B43F3F; Thu, 17 Jul 2003 18:35:38 -0700 (PDT)
	(envelope-from das@FreeBSD.ORG)
Received: from HAL9000.homeunix.com (localhost [127.0.0.1])
	by HAL9000.homeunix.com (8.12.9/8.12.9) with ESMTP id h6I1ZOLv065929;
	Thu, 17 Jul 2003 18:35:24 -0700 (PDT)
	(envelope-from das@FreeBSD.ORG)
Received: (from das@localhost)
	by HAL9000.homeunix.com (8.12.9/8.12.9/Submit) id h6I1ZHc1065928;
	Thu, 17 Jul 2003 18:35:17 -0700 (PDT)
	(envelope-from das@FreeBSD.ORG)
Date: Thu, 17 Jul 2003 18:35:17 -0700
From: David Schultz <das@FreeBSD.ORG>
To: Dag-Erling Smorgrav <des@des.no>
Message-ID: <20030718013517.GA50428@HAL9000.homeunix.com>
Mail-Followup-To: Dag-Erling Smorgrav <des@des.no>,
	Harti Brandt <brandt@fokus.fraunhofer.de>, sparc64@freebsd.org,
	current@freebsd.org, Marcel Moolenaar <marcel@xcllnt.net>
References: <200307141153.h6EBrJKk045346@cueball.rtp.FreeBSD.org>
	<20030715175821.K34004@beagle.fokus.fraunhofer.de>
	<xzp65m3vfw1.fsf@dwp.des.no> <20030715185438.GB15674@dhcp01.pn.xcllnt.net>
	<xzpy8yzty2m.fsf@dwp.des.no> <20030715190456.GC15674@dhcp01.pn.xcllnt.net>
	<xzpn0ffts1c.fsf@dwp.des.no>
	<20030717095257.C30394@beagle.fokus.fraunhofer.de>
	<20030717083101.GA51198@des.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030717083101.GA51198@des.no>
cc: Marcel Moolenaar <marcel@xcllnt.net>
cc: current@FreeBSD.ORG
cc: sparc64@FreeBSD.ORG
Subject: Re: [-CURRENT tinderbox] failure on sparc64/sparc64
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jul 2003 01:35:39 -0000

On Thu, Jul 17, 2003, Dag-Erling Smorgrav wrote:
> On Thu, Jul 17, 2003 at 09:58:10AM +0200, Harti Brandt wrote:
> > I have no idea how a program can core in vfork(). Probably a vm problem?
> 
> Most likely a KSE-related problem in vfork().  Try replacing vfork() with
> fork() in make(1) and see if the problem goes away.  Warning: build times
> may increase significantly...

I would guess that the problem doesn't occur in the vfork() call
itself, but in the child process (gzip?), and there's a problem
that causes the child to be incompletely divorced from the parent.
Is there any trick to reproducing this problem?  I just did a make
universe on i386 and didn't see it, but maybe my sources are too
old.

It would be interesting to see if fork() fixes the problem.  With
the VM optimizations, vfork() is only about 20% faster than
fork(), so build times shouldn't be significantly impacted.