From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 11 22:41:08 2012 Return-Path: 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 D7EF5106566B; Wed, 11 Jan 2012 22:41:08 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 74C5C8FC12; Wed, 11 Jan 2012 22:41:08 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so2301595obb.13 for ; Wed, 11 Jan 2012 14:41:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KZRT371D8SG/OoajzGdUlklyBE5UnzLREnq4UUfJzWA=; b=d5CEsnBaFTegOZgvdXjsTqMZ682fPPrvp6tU7YaRZgtUO+9uofeW/DWgFZUQ0fM9vi 5GA6SXxQ4yFk3sAtOCGb0FQfaeCZeM6B9zQ7gt+P55Lhk8MrcymLaSP4qqUnXb0YQnHX /wgLnTIBPvzOp01knwiqJ1rqsfZcPa4BOBRRg= MIME-Version: 1.0 Received: by 10.182.49.106 with SMTP id t10mr940320obn.49.1326321668021; Wed, 11 Jan 2012 14:41:08 -0800 (PST) Received: by 10.182.152.6 with HTTP; Wed, 11 Jan 2012 14:41:07 -0800 (PST) In-Reply-To: References: <201201110806.30620.jhb@freebsd.org> Date: Wed, 11 Jan 2012 14:41:07 -0800 Message-ID: From: Garrett Cooper To: Ivan Voras Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org, Xin LI , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 22:41:08 -0000 On Wed, Jan 11, 2012 at 9:16 AM, Ivan Voras wrote: > On 11 January 2012 17:47, Garrett Cooper 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. Maybe, maybe not. I've repro'ed this issue once on my 8-core 9.0 box too, but remember that tdb and talloc were converted over to use waf stuff recently... and this might be a race that's easier to repro on 9.x+ than 8.x :). Thanks, -Garrett