From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 5 10:41:40 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 B3C221065670 for ; Sun, 5 Feb 2012 10:41:40 +0000 (UTC) (envelope-from janm-freebsd-hackers@transactionware.com) Received: from midgard.transactionware.com (mail2.transactionware.com [203.14.245.36]) by mx1.freebsd.org (Postfix) with SMTP id EFA2A8FC0A for ; Sun, 5 Feb 2012 10:41:39 +0000 (UTC) Received: (qmail 92974 invoked by uid 907); 5 Feb 2012 10:41:37 -0000 Received: from b13FC.static.pacific.net.au (HELO [192.168.1.154]) (202.7.88.252) (smtp-auth username janm, mechanism plain) by midgard.transactionware.com (qpsmtpd/0.84) with (AES128-SHA encrypted) ESMTPSA; Sun, 05 Feb 2012 21:41:37 +1100 Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=windows-1252 From: Jan Mikkelsen In-Reply-To: Date: Sun, 5 Feb 2012 21:41:57 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: <5D37298B-9D68-4F0F-8AAB-E8F2DBB9D9C3@transactionware.com> References: <201201110806.30620.jhb@freebsd.org> To: freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.1251.1) Cc: Garrett Cooper , Xin LI , Ivan Voras , 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: Sun, 05 Feb 2012 10:41:40 -0000 On 12/01/2012, at 3:47 AM, Garrett Cooper wrote: > [ builds hanging in python with waf =85 ] > Glad to see that iXsystems isn't the only one ([1] -- please add a "me > too" to the PR). The problem is that we do FreeNAS nightlies and they > frequently get stuck building tdb (10%~20% of the time) and it sticks > 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 (build.ix's copy of python doesn't have it enabled, but > streetfighter.ix, my system bayonetta, etc do). Any progress on this? Or a workaround? Just had another build stuck on this =85 Jan.