sem(4) lockup in python?
yanegomi at gmail.com
Wed Jan 11 22:41:08 UTC 2012
On Wed, Jan 11, 2012 at 9:16 AM, Ivan Voras <ivoras at freebsd.org> wrote:
> On 11 January 2012 17:47, Garrett Cooper <yanegomi at 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
> ... 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 :).
More information about the freebsd-hackers