Date: Wed, 11 Jan 2012 14:41:07 -0800 From: Garrett Cooper <yanegomi@gmail.com> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-hackers@freebsd.org, Xin LI <delphij@delphij.net>, davidxu@freebsd.org Subject: Re: sem(4) lockup in python? Message-ID: <CAGH67wTGP3qDbE6miFEg7ddaKx6C%2BTxQMG%2BzAbfQdFL=998NJg@mail.gmail.com> In-Reply-To: <CAF-QHFUjNe3RvDT-LQW2wMSgn46aW2QfJLw35ZzTnjYuzMJn8g@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> <CAF-QHFUjNe3RvDT-LQW2wMSgn46aW2QfJLw35ZzTnjYuzMJn8g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 11, 2012 at 9:16 AM, Ivan Voras <ivoras@freebsd.org> wrote:
> 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.
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGH67wTGP3qDbE6miFEg7ddaKx6C%2BTxQMG%2BzAbfQdFL=998NJg>