Hi
Thanks for reporting the issue. It should be fixed now by PR #3442 in the CP2K development version.
Best
Matthias
--
You received this message because you are subscribed to the Google Groups "cp2k" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
cp2k+uns...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/cp2k/4c2de455-efb6-4886-8f1d-e1c1b2eac4a0n%40googlegroups.com.
Did you increase the OMP_STACKSIZE to 16M or more, e.g. with export OMP_STACKSIZE=16M ?
HTH
Matthias
To view this discussion on the web visit https://groups.google.com/d/msgid/cp2k/9e7679a2-0155-4ed9-8c52-adc07f58af90n%40googlegroups.com.
The CP2K Apple M1 tester for the current CP2K development version shows no issues in the log file.
Did you follow all the instructions in the howto, like to deactivate brew’s clang based openmpi installation with “brew unlink open-mpi” to avoid any interference with the openmpi installation which is performed by the CP2K toolchain using the GNU compiler?
To view this discussion on the web visit https://groups.google.com/d/msgid/cp2k/d3d0d560-59dc-490f-aa03-9dcb8e2481ffn%40googlegroups.com.
By contrast to the Apple M1 psmp regression test, the corresponding ssmp test is not run continuously. I have synced the Apple M1 ssmp arch file with the psmp one. An ssmp test run with that file showed no issues on my Apple M1 using 2 OpenMP threads.
To view this discussion on the web visit https://groups.google.com/d/msgid/cp2k/835a2e55-f240-4b21-8ad4-62fcaf29dcdbn%40googlegroups.com.