ABP2 CPU-only applications
Anonymous
9 Jan 2010 2:56:49 UTC
Topic 13802
(moderation:
Quote:
Got two(161484922, 161484846) signal 11 results on my i7 920 root server with the quad ABP2 WUs yesterday. Before and afterwords everything works like a charm. Both WUs crashed at the same time, no hints in the system log files.
Interesting. Anything running on this machine that could eati up memory at that time?
Quote:
Interesting thing is I still get APP2 WUs stamped to be done by app 1.08, while the actual app should be 1.11.
The CUDA App version is at 1.11; the CPU App is 1.08. That's ok.
BM
ABP2 CPU-only applications
)
I see this 'segfault' errors occasionally happen on some machines, usually all app instances running there get this signal at the very same time, and without any relation to the application source code line they are in or the data they are processing, so this isn't a real programming error.
I suspected the Linux 'optimistic memory allocation' to be responsible for that, that randomly kills processes if the physical memory isn't enough for the memory it 'optimistically' assigned to processes, but it's hard to believe that this is the case here.
We currently loose us up to ~2000h of computing time per day due to this problem.
BM
BM