On Thu, 15 Apr 2010, Derek Gaston wrote:
> On Apr 15, 2010, at 9:57 AM, Roy Stogner wrote: > >> So the problem is OS, compiler, and MPI implementation independent. >> Still a slim chance it's PETSc (I've only reproduced it on 3.0.0, >> couldn't get it to crop up with a brief test using 3.1) but I'd bet >> it's us. > > We still use Petsc 2.3.3 around here... and haven't run into this > problem (and we do use Constant Monomials and adaptivity quite a > bit). That's just one data point... but it could be some > interaction with libMesh and Petsc 3.0. It might be triggered by PETSc in some subtle way, but I'm certain now it's not being caused by PETSc - we've got a corrupt entry being generated at the end of the send_list. Still need to figure out how. If you haven't triggered it, and I can't trigger it with any CG work, then my best guess is that I typoed Lorenzo's latest DG send_list patch when integrating that recently. --- Roy ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
