From: Axel Kohlmeyer (akohlmey_at_gmail.com)
Date: Wed Jun 11 2014 - 03:13:56 CDT
On Wed, Jun 11, 2014 at 4:07 AM, Norman Geist <
norman.geist_at_uni-greifswald.de> wrote:
> Segfaults usually indicate either or programming error or incompatible
> binaries or libraries.
>
but those would happen instantly. not after several hours. that is more
likely caused by memory corruption, e.g. through bit flips in overheated
memory modules or overheated CPUs or GPUs. the described symptoms are more
similar to those observed by aggressive overclocking.
axel.
> Therefore please give us the output of:
>
>
>
> “ldd /your/namd/path/namd2”
>
>
>
> Because I think you might use the wrong “libcudart.so”.
>
>
>
> Norman Geist.
>
>
>
> *Von:* owner-namd-l_at_ks.uiuc.edu [mailto:owner-namd-l_at_ks.uiuc.edu] *Im
> Auftrag von *Vlastimil Zíma
> *Gesendet:* Mittwoch, 11. Juni 2014 09:37
> *An:* Namd Mailing List
> *Betreff:* namd-l: NAMD_2.9_Linux-x86_64-multicore-CUDA Segfaults
>
>
>
> Hi,
>
> I occasianlly run into Segmentation fault in my simulations but recently
> they become more often. I use NAMD2.9 which I downloaded from NAMD site as
> binary.
>
> It manifests on two of my machines so far, hence I don't expect any
> troubles with hardware. Both machines are running Debian wheezy, but with
> different GPU card. I have tried several versions of nvidia drivers.
>
> The simulation usually runs for 10 to 25 hours before it crashes.
>
> Are there any actions I should take in order to debug the segfault?
>
> Regards
>
> Vlastik
>
>
> ------------------------------
> <http://www.avast.com/>
>
> Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus
> <http://www.avast.com/> Schutz ist aktiv.
>
>
-- Dr. Axel Kohlmeyer akohlmey_at_gmail.com http://goo.gl/1wk0 College of Science & Technology, Temple University, Philadelphia PA, USA International Centre for Theoretical Physics, Trieste. Italy.
This archive was generated by hypermail 2.1.6 : Thu Dec 31 2015 - 23:20:51 CST