Date: Wed, 11 Jan 2012 18:16:05 +0100 From: Ivan Voras <ivoras@freebsd.org> To: Garrett Cooper <yanegomi@gmail.com> Cc: freebsd-hackers@freebsd.org, Xin LI <delphij@delphij.net>, davidxu@freebsd.org Subject: Re: sem(4) lockup in python? Message-ID: <CAF-QHFUjNe3RvDT-LQW2wMSgn46aW2QfJLw35ZzTnjYuzMJn8g@mail.gmail.com> In-Reply-To: <CAGH67wRsek2-WY_ETW6QEER1r5dDXLXfDjbzpHMjtv059Y8cJw@mail.gmail.com> References: <jejrbe$or8$1@dough.gmane.org> <201201110806.30620.jhb@freebsd.org> <CAF-QHFWFvYTPeM68Mk%2BOYVX--MNhKOJ2o1GF9ZOsBmtiC5fYFQ@mail.gmail.com> <CAGH67wRsek2-WY_ETW6QEER1r5dDXLXfDjbzpHMjtv059Y8cJw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF-QHFUjNe3RvDT-LQW2wMSgn46aW2QfJLw35ZzTnjYuzMJn8g>