From owner-freebsd-hackers@FreeBSD.ORG  Wed Jan 11 17:16:47 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 55212106566B;
	Wed, 11 Jan 2012 17:16:47 +0000 (UTC)
	(envelope-from ivoras@gmail.com)
Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com
	[209.85.213.182])
	by mx1.freebsd.org (Postfix) with ESMTP id DF71A8FC13;
	Wed, 11 Jan 2012 17:16:46 +0000 (UTC)
Received: by yenm1 with SMTP id m1so469895yen.13
	for <multiple recipients>; Wed, 11 Jan 2012 09:16:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=mime-version:sender:in-reply-to:references:from:date
	:x-google-sender-auth:message-id:subject:to:cc:content-type;
	bh=YSpeY/pvDzUqWzxPCSCX7YmtRSMUSDz8lOoq54v+vAM=;
	b=Rv0Rj6UDaQzijgW5+NCiwsBb+9lSh3wGZgQhyBz5teKdLxDEWN95mKlhjfSRfWA8M/
	9xJLKVmZDaWkZ8WlyqOtCp/GTUOqd2+wq4f4Di9D5hf+vdaQeFhRy/L5Z77vfeXqivwX
	iDBf7Vx91vBm7EE/kLp+bA2U3OZ4c+7KZsdoU=
Received: by 10.236.155.40 with SMTP id i28mr33617859yhk.130.1326302206180;
	Wed, 11 Jan 2012 09:16:46 -0800 (PST)
MIME-Version: 1.0
Sender: ivoras@gmail.com
Received: by 10.100.214.14 with HTTP; Wed, 11 Jan 2012 09:16:05 -0800 (PST)
In-Reply-To: <CAGH67wRsek2-WY_ETW6QEER1r5dDXLXfDjbzpHMjtv059Y8cJw@mail.gmail.com>
References: <jejrbe$or8$1@dough.gmane.org> <201201110806.30620.jhb@freebsd.org>
	<CAF-QHFWFvYTPeM68Mk+OYVX--MNhKOJ2o1GF9ZOsBmtiC5fYFQ@mail.gmail.com>
	<CAGH67wRsek2-WY_ETW6QEER1r5dDXLXfDjbzpHMjtv059Y8cJw@mail.gmail.com>
From: Ivan Voras <ivoras@freebsd.org>
Date: Wed, 11 Jan 2012 18:16:05 +0100
X-Google-Sender-Auth: ly_t-964BKD9AFWJGk8idagMCzc
Message-ID: <CAF-QHFUjNe3RvDT-LQW2wMSgn46aW2QfJLw35ZzTnjYuzMJn8g@mail.gmail.com>
To: Garrett Cooper <yanegomi@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: freebsd-hackers@freebsd.org, Xin LI <delphij@delphij.net>,
	davidxu@freebsd.org
Subject: Re: sem(4) lockup in python?
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jan 2012 17:16:47 -0000

On 11 January 2012 17:47, Garrett Cooper <yanegomi@gmail.com> wrote:

> when doing interactive builds as well. The issue appears to be
> exacerbated when we have more builds running in parallel on the same
> machine. I've also run into the same issue compiling talloc because it
> uses the same waf infrastructure as tdb, which was designed to "speed
> things up by forcing builds to be parallelized" (It builds
> kern.smp.ncpus jobs instead of -j 1). Furthermore, it seems to occur
> regardless of whether or not we have the WITH_SEM enabled in python or
> not

... which is interesting as I've habitually enabled WITH_SEM on 8.x
systems and there it worked without problems. Must be the new code.