Hi! Here is my problem:
We are tring to test MM5 on different platforms. Our first configuration was Suse Linux 10.0 on AMD X2 4800+ dual core (4GB of memory), with PGI 6.0 compilers. Here our compiling settings in configure.user
FC = pgf90
FCFLAGS = -I$(LIBINCLUDE) -Mnosgimp -pc 32 -byteswapio -tp k8-64 -fastsse -Mconcur -DDEC_ALPHA -mp
CPP = /lib/cpp
CFLAGS = -O -DDEC_ALPHA -pc 32 -tp k8-64 -Mnosgimp -byteswapio -DDEC_ALPHA -Mconcur -mp
CPPFLAGS = -I$(LIBINCLUDE) -DDEC_ALPHA -m64 -mp
LDOPTIONS = -byteswapio -fastsse -Mconcur -mp -DDEC_ALPHA
CC = pgcc
After setting NCPUS=2 and unlimiting the stack size, we were able to make different kind of simulations on all cores at the same time. There was no problem about number of nests, domain size and simulation duration (we were able to test even with maxnes 5, mix=120 and mjx=120 for several meteorological months). The only problem was on very large domains, where we had to delete -mp from LDOPTIONS; this operation resolved our problems
After that, we tested MM5 on the same platform, but with Suse 10.1 and PGI 6.2. With the same compilers options we had many segmentation faults, that didn’t seem to depend on the domain size or simulation length.
After that, we tested it on AMD FX5600+ dual core (4 Gb of memory) with suse 10.2 and PGI 6.2. We had the same problems. So we were waiting for PGI 7.0 compilers. After their realase, we tested it on this platform, and the same problems occurred. We have found that setting NCPUS=1 there is no segmentation fault, even if the program works only on 1 core (as expected).
Can you help me with this problem, please?