[petsc-users] KSPConvergedReason = KSP_CONVERGED_ITERATING

[Barry Smith]

   Hmm, KSPSolve() should never complete with a KSP_CONVERGED_ITERATING so something is definitely not going well.

   Have you run your code with valgrind to make sure there is not some subtle memory bug that only rears its ugly head after a great deal of time? http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind  I would do this first.

    It is possible to use the -g flag even with optimized builds to get debug symbols even with optimization (in fact that is our new default) so depending on the machine you are running on and how many MPI processes you use it could be possible to simply run the run in the debugger (-start_in_debugger) and then come back the next day when one process returns and the others hang then control c the other processes and see where they are in the code.

Barry


> On Jan 11, 2016, at 8:53 PM, Chung-Kan Huang <ckhuangf at gmail.com> wrote:
> 
> 
> Hi,
> 
> I am encountering KSPSolve hanging with one process finished KSPSolve reporting KSPConvergedReason = KSP_CONVERGED_ITERATING while other processes stuck in KSPSolve. 
> 
> The problem is not seen when code was compiled in debug mode and problem only appears after more than 10 hours of run time with production mode.
> 
> Can anyone suggest how I can do to debug this case?
> 
> Thanks,
> 
> Ken
>