Can you try with a simple call that only calls PetscInitialize/Finalize?

> On Oct 11, 2021, at 3:30 PM, Roland Richter <[email protected]> wrote:
> 
> At least according to configure.log mpiexec was defined as
> 
> Checking for program /opt/intel/oneapi/mpi/2021.4.0//bin/mpiexec...found
>                   Defined make macro "MPIEXECEXECUTABLE" to 
> "/opt/intel/oneapi/mpi/2021.4.0/bin/mpiexec"
> 
> When running ex19 with this mpiexec it fails with the usual error, even 
> though all configuration steps worked fine. I attached the configuration log.
> 
> Regards,
> 
> Roland
> 
> Am 11.10.21 um 14:24 schrieb Stefano Zampini:
>> You are most probably using a different mpiexec then the one used to compile 
>> petsc.
>> 
>> 
>> 
>>> On Oct 11, 2021, at 3:23 PM, Roland Richter <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>> 
>>> I tried either ./ex19 (SNES-example), mpirun ./ex19 or mpirun -n 1 ./ex19, 
>>> all with the same result.
>>> 
>>> Regards,
>>> 
>>> Roland
>>> 
>>> Am 11.10.21 um 14:22 schrieb Matthew Knepley:
>>>> On Mon, Oct 11, 2021 at 8:07 AM Roland Richter <[email protected] 
>>>> <mailto:[email protected]>> wrote:
>>>> Hei,
>>>> 
>>>> at least in gdb it fails with
>>>> 
>>>> Attempting to use an MPI routine before initializing MPICH 
>>>> [Inferior 1 (process 7854) exited with code 01] 
>>>> (gdb) backtrace 
>>>> No stack.
>>>> 
>>>> 
>>>> What were you running? If it never makes it into PETSc code, I am not sure 
>>>> what we are
>>>> doing to cause this.
>>>> 
>>>>   Thanks,
>>>> 
>>>>      Matt
>>>>  
>>>> Regards,
>>>> 
>>>> Roland
>>>> 
>>>> Am 11.10.21 um 13:57 schrieb Matthew Knepley:
>>>>> On Mon, Oct 11, 2021 at 5:24 AM Roland Richter <[email protected] 
>>>>> <mailto:[email protected]>> wrote:
>>>>> Hei,
>>>>> 
>>>>> I compiled PETSc with Intel MPI (MPICH) and GCC as compiler (i.e. using
>>>>> Intel OneAPI together with the supplied mpicxx-compiler). Compilation
>>>>> and installation worked fine, but running the tests resulted in the
>>>>> error "Attempting to use an MPI routine before initializing MPICH". A
>>>>> simple test program (attached) worked fine with the same combination.
>>>>> 
>>>>> What could be the reason for that?
>>>>> 
>>>>> Hi Roland,
>>>>> 
>>>>> Can you get a stack trace for this error using the debugger?
>>>>> 
>>>>>   Thanks,
>>>>> 
>>>>>      Matt
>>>>>  
>>>>> Thanks!
>>>>> 
>>>>> Regards,
>>>>> 
>>>>> Roland Richter
>>>>> 
>>>>> 
>>>>> -- 
>>>>> What most experimenters take for granted before they begin their 
>>>>> experiments is infinitely more interesting than any results to which 
>>>>> their experiments lead.
>>>>> -- Norbert Wiener
>>>>> 
>>>>> https://www.cse.buffalo.edu/~knepley/ 
>>>>> <http://www.cse.buffalo.edu/~knepley/>
>>>> 
>>>> 
>>>> -- 
>>>> What most experimenters take for granted before they begin their 
>>>> experiments is infinitely more interesting than any results to which their 
>>>> experiments lead.
>>>> -- Norbert Wiener
>>>> 
>>>> https://www.cse.buffalo.edu/~knepley/ 
>>>> <http://www.cse.buffalo.edu/~knepley/>
>> 
> <configure.log>

Reply via email to