[petsc-users] Anyone meet mumps crash on AIX?

[Barry Smith]

  I would report all the memory issues found with valgrind to the MUMPS developers and demand action on their part. Minor memory corruption on some systems can do no harm while on other systems it leads to crashes.


   Barry

On Nov 22, 2011, at 8:47 AM, Gong Ding wrote:

> Hi,
> I am testing my code on AIX.
> petsc 3.2 with MUMPS 4.10 ALWAYS crash, both serial and parallel, with ERROR: 0031-250  task 0: Segmentation fault.
> However, other direct solver seems ok, i.e. superlu.
> 
> The core file was checked by gdb, but only littel information: 
> Program terminated with signal 11, Segmentation fault.
> #0  0x000000010150d8ec in dmumps_462 ()
> 
> I had checked the code with valgrind on Linux/AMD64, which also reported some memory problem (but never crash)
> ==10354== Invalid read of size 8
> ==10354==    at 0x57BE749: __intel_new_memcpy (in /opt/intel/Compiler/11.1/038/lib/intel64/libirc.so)
> ==10354==    by 0x57A0AF5: _intel_fast_memcpy.J (in /opt/intel/Compiler/11.1/038/lib/intel64/libirc.so)
> ==10354==    by 0x185F043: dmumps_363_ (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x186B114: dmumps_26_ (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x193D382: dmumps_.P (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x183EA6E: dmumps_f77_ (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x181EBE7: dmumps_c (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x1406EFE: MatLUFactorSymbolic_AIJMUMPS (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x1321009: MatLUFactorSymbolic (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x15FF044: PCSetUp_LU (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x15AB193: PCSetUp (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x16364DD: KSPSetUp (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==  Address 0x9318d78 is 248 bytes inside a block of size 252 alloc'd
> ==10354==    at 0x4A0776F: malloc (vg_replace_malloc.c:263)
> ==10354==    by 0x5CB3C43: for_allocate (in /opt/intel/Compiler/11.1/038/lib/intel64/libifcore.so.5)
> ==10354==    by 0x19CF545: mumps_754_ (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x186A392: dmumps_26_ (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x193D382: dmumps_.P (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x183EA6E: dmumps_f77_ (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x181EBE7: dmumps_c (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x1406EFE: MatLUFactorSymbolic_AIJMUMPS (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x1321009: MatLUFactorSymbolic (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x15FF044: PCSetUp_LU (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x15AB193: PCSetUp (in /home/gdiso/genius_master/bin/genius.LINUX)
> ==10354==    by 0x16364DD: KSPSetUp (in /home/gdiso/genius_master/bin/genius.LINUX)
> 
> Any suggestion?
> 
> Gong Ding
> 
>