Tim,
I meant 9.1.037. And the same code has been running with the same ifort compiler and the same version of lam-mpi for many months on the single core AMD machines. We suspect that it is a memory leak or an allocation issue, but we were checking to see if anyone has had similar problems.
Thanks for the prompt response.
-Daniel
On 3/5/07, Tim Prince <tprince@myrealbox.com> wrote:
REASOR wrote:
> All,
> I currently run lam-mpi on small commodity clusters. I use lam-mpi with
> ifort 9.1.3 for compiling and running fortran 90 fluid dynamics codes.
> I have been running on AMD 2500+ (32bit), P4 (32bit), and AMD 3200+
> (64bit)
> nodes single core without any problems, but when I upgraded to running on
> AMD 4600+ dual core nodes and Core2Duo e6400 dual core nodes I get the
> error
> below after an arbitrary number of iterations. Has anyone had any similar
> problems using lam-mpi with ifort on these processors? If so have they
> had
> any luck addressing the problem?
> Thanks,
> -DR
>
> forrtl: severe (174): SIGSEGV, segmentation fault occurred
Nearly everyone has addressed segfault problems, but not by claiming
that they are an inevitable result of running ifort with lam on dual
core. Your ifort version number doesn't make any sense; you should use
the current version (9.1.041), as well as following normal procedures to
identify the location of your segfault.
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/