On Wed, 29 May 2013 10:30:29 -0500 Jed Brown <[email protected]> wrote: > Jan Blechta <[email protected]> writes: > > > On my system with PETSc 3.4.0, hypre 2.9.1a and also with PETSc > > 3.2-p7, hypre 2.8.0b occassionaly following error is raised in > > parallel when using Krylov solver with AMG > > > > [2]PETSC ERROR: Error in external library! > > [2]PETSC ERROR: Error in HYPRE_IJMatrixCreate()! > > [2]PETSC ERROR: MatHYPRE_IJMatrixCreate() line 71 > > in /petsc-3.4.0/src/dm/impls/da/hypre/mhyp.c [2]PETSC ERROR: > > PCSetUp_HYPRE() line 110 > > in /petsc-3.4.0/src/ksp/pc/impls/hypre/hypre.c [2]PETSC ERROR: > > PCSetUp() line 890 in /petsc-3.4.0/src/ksp/pc/interface/precon.c > > [2]PETSC ERROR: KSPSetUp() line 278 > > in /petsc-3.4.0/src/ksp/ksp/interface/itfunc.c [2]PETSC ERROR: > > KSPSolve() line 399 in /petsc-3.4.0/src/ksp/ksp/interface/itfunc.c > > [2]PETSC ERROR: PCDestroy_HYPRE() line 190 > > in /petsc-3.4.0/src/ksp/pc/impls/hypre/hypre.c > > This stack is messed up. PCDestroy_HYPRE does not call KSPSolve.
Maybe this is PETSc stack from previous time step - this is provided by DOLFIN. > Maybe you aren't checking error codes and try to do something else > collective? I don't know, I'm just using FEniCS. > > > [2]PETSC ERROR: PCDestroy() line 121 > > in /petsc-3.4.0/src/ksp/pc/interface/precon.c [2]PETSC ERROR: > > KSPDestroy() line 788 in /petsc-3.4.0/src/ksp/ksp/interface/itfunc.c > > > > and deadlocks. Did you seen it before? Where can be the problem? > > Deadlock must be back in your code. This error occurs on > PETSC_COMM_SELF, which means we have no way to ensure that the error > condition is collective. You can't just go calling other collective > functions after such an error. This means that DOLFIN handles poorly some error condition. > > Anyway, please set up a reproducible test case and/or get a trace from > inside Hypre. It will be useful for them to debug the problem. I'm not PETSc user so it would be quite time-consuming for me to try to reproduce it without FEniCS. I will try at least get a trace. Jan > _______________________________________________ > fenics mailing list > [email protected] > http://fenicsproject.org/mailman/listinfo/fenics _______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
