[CP2K-user] [CP2K:21627] Re: DFTB calculations KILLED BY SIGNAL: 9 (Killed)

[bijaya pathak]

Thank you so much. Let me try to do things you have suggested. 

On Monday, July 7, 2025 at 6:47:10 PM UTC+5:30 Konstantin Tokarev wrote:

> Please try `dmesg | grep oom-killer`. If you see cp2k there, this is it. 
> Other running process might have also been affected. Alternatively, if you 
> investigate "killed 9" crash right after it happened, you can just look at 
> the end of `dmesg | less` (press End key, or type "G" (shift and 'g' key) 
> to scroll "less" to the end).
>
> Other info you may find there is details of memory consumption before 
> process was killed, but this may be  overwhelming to read if you aren't 
> used to such things. What is the most important, if there are no other 
> memory hungry processes running in the system in parallel with cp2k and you 
> still get oom, you'll probably have to reduce your system, basis set, or 
> find another way to reduce memory consumption. Adding some swap on NVMe SSD 
> might be helpful, but performance should be monitored carefully to ensure 
> that it does not cause "thrashing" (constant swapping memory in and out) 
> which would cause catastrophic slowdown of calculations.
>

-- 
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+unsubscribe at googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/cp2k/394b86d6-0ee3-44eb-b429-f49fd287899en%40googlegroups.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cp2k.org/archives/cp2k-user/attachments/20250707/0fbd2eb2/attachment.htm>