I can confirm that. The same problem happens to me, even though with mumps and metis obtained from official site this doesn't happen.
Regards, Alexander ----- Reply message ----- From: "John Fettig" <[email protected]> To: "For users of the development version of PETSc" <petsc-dev at mcs.anl.gov> Subject: [petsc-dev] Problem with MUMPS+metis Date: Mon, Feb 20, 2012 18:48 When I run MUMPS in parallel with parmetis ordering (icntl(28)=2, icntl(29)=2), everything seems to work fine.? However, if I try to run it serially it reverts back to metis ordering and seems to get caught in some kind of infinite recursion.? I've run it through valgrind and attached the output.? Also I attached it to a debugger and the stack is enormous when it hangs, something like 10,000 frames deep.? You can sort of see that from the valgrind output towards the end. My question is: who do you suspect to be at fault here?? Is it a bug in MUMPS, metis, or PETSc?? My suspicion is MUMPS.? This is with the PETSc-automatically compiled MUMPS, metis, and parmetis, retrieved today. Thanks, John -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120220/a2111565/attachment.html>
