[parsec-users] ferret deadlock
cbienia at CS.Princeton.EDU
Mon Apr 21 12:47:36 EDT 2008
We know of no deadlocks in any of the PARSEC workloads, but due to the
nondeterministic nature of multithreading we expected that problems like that
would show up. We are very interested in fixing this bug, can you provide us
with more information? You seem to be able to reproduce the deadlock
consistently, could you tell us which synchronization primitives are
On Monday 21 April 2008 11:54 am, Marc de Kruijf wrote:
> I am seeing frequent deadlock running ferret on any input size
> (happens approx. 50% of the time) . My platform is "i686-linux.gcc",
> which uses gcc 3.4.4 running on an Intel Core2 Duo. I see the same
> problem with versions of gcc 4.x as well. Below is a sample output.
> The deadlock happens as the program is completing.
> Has nobody seen this before?
> $ bin/parsecmgmt -a run -p ferret -c gcc -i simsmall
> [PARSEC] Benchmarks to run: ferret
> [PARSEC] [========== Running benchmark ferret ==========]
> [PARSEC] Deleting old run directory.
> [PARSEC] Setting up run directory.
> [PARSEC] Unpacking benchmark input 'simsmall'.
> [PARSEC] Running 'time
>/apps/ferret/inst/i686-Linux.gcc/bin/ferret corel lsh queries 10 20 1
> [PARSEC] [---------- Beginning of output ----------]
> parsec-users mailing list
> parsec-users at lists.cs.princeton.edu
More information about the parsec-users