This forum is probably not the best way to reach OASIS community or at least an experienced audience in running coupled models with it. Actually NEMO does not even seem to be the cause of the deadlock or the crash of your runs.
I suggest you to send a message to OASIS mailing list (email@example.com) ou to post a message to their users forum on Oasis Forum
I am not an XIOS specialist, but I had the same issue with a recent XIOS_2.5 revision (#2018) and found some work-around by commenting the MPI_Barrier and MPI_Comm_free instructions located immediately after the MPI_Intercomm_create instruction, in both client.cpp and server.cpp. XIOS developers are warned and a better solution hoped.
Thank you for the reply.
I did as suggested and now the coupled model freezes after
starting wrf task 0 of 1
---> prism_initxios.x 0
-> info : CServer : Register new Context : nemo_server
-> info : Register new Context : nemo
-> info : update step : 0 timestep 300s
-> info : CClientBuffer: allocated 2 x 73907148 bytes for server 0 with a maximum of 16 buffered events
I checked that the model freezes when xios_close_context_definition() is called in SUBROUTINE iom_init in NEMOGCM.
it seems that there is an issue with compiler.
Can you please tell me which compiler did you use?
We now compile both xios and nemo with intel-compilers-2021.4.0.
The compiling options were also changed to -O2 (instead of -Ofast) and march=native (instead of march=core-avx2).
This helped on our system.