[parsec-users] ferret deadlock

Marc de Kruijf dekruijf at cs.wisc.edu
Mon Apr 21 11:54:59 EDT 2008


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'.
corel/
corel/__cass.env
corel/corel.raw
corel/lsh.lsh
corel/map_corel.map
queries/
queries/acorn.jpg
queries/air-fighter.jpg
queries/airplane-2.jpg
queries/airplane-takeoff-3.jpg
queries/alcatraz-island-prison.jpg
queries/american-flag-3.jpg
queries/apartment.jpg
queries/apollo-2.jpg
queries/apollo-earth.jpg
queries/apple-11.jpg
queries/apple-14.jpg
queries/apple-16.jpg
queries/apple-7.jpg
queries/aquarium-fish-25.jpg
queries/arches-9.jpg
queries/arches.jpg
[PARSEC] Running 'time
/media/usbdisk/top/users/dekruijf/parsec-1.0/pkgs/apps/ferret/../../../pkgs/apps/ferret/inst/i686-Linux.gcc/bin/ferret
corel lsh queries 10 20 1 output.txt':
[PARSEC] [---------- Beginning of output ----------]
(12,1)
(12,2)
(12,3)
(12,4)
(12,5)
(12,6)
(12,7)
(12,8)
(12,9)
(12,10)
(12,11)
(12,12)
(13,13)
(14,14)
(15,15)
(16,16)

----

Marc


More information about the parsec-users mailing list