Jan Blechta <[email protected]> writes: > 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.
When I said "you", I was addressing the list in general, which includes FEniCS developers. >> > [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. It appears that way, but that appears to be independent of whatever causes Hypre to return an error. >> 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. You can try dumping the matrix using '-ksp_view_mat binary' (writes 'binaryoutput'), for example, then try solving it using a PETSc example, e.g. src/ksp/ksp/examples/tutorials/ex10.c with the same configuration via run-time options. _______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
