Thanks. Now that I know what to look for, I should be able to figure it
out.
BTW, I switched the script that ultimately runs the mpiexec from tcsh to
bash and the problem went away. Not complaining but do you have any idea
why that might be?
Gene
-- Eugene M Fluder, Jr, PhD
Computat
Holger,
Thanks. I appreciate the detail.
Gene
-- Eugene M Fluder, Jr, PhD
Computational Scientist
Scientific Computing
The Mt. Sinai School of Medicine
One Gustave L. Levy Place, Box 1498
New York, NY 10029-6574
T: 212 659 8608
F: 646
Oh, I just realized that you are probably using the Open MPI version of VT which
builds as part of the Open MPI build. I'm not 100% sure if the modification of
config.h works as laid out, but it should... you need to look out for VT's
config.h then, not Open MPI's.
Holger
On 07/06/2012 04:54 PM,
Hi Gene,
this error is often caused by insufficiently synchronized TSCs (time stamp
counter) of different processors/cores.
When VT uses the TSC for timing the events (it does that by default), and the
processes switch to another core during execution, it may well happen that the
next recorded tim
I got the following error running a VT enabled run of AMBER. This was reported
in December of 2009 under almost identical conditions but the thread does not
contain a resolution. I reran the test with VT_UNIFY=no and it completed
normally. The same error occurred when I ran vtunify separately.
