forum@abinit.org

Subject: The ABINIT Users Mailing List ( CLOSED )

List archive

Re: [abinit-forum] p4_error: interrupt SIGx: 13 in band structure calculation

From: "Anglade Pierre-Matthieu" <anglade@gmail.com>
To: forum@abinit.org
Subject: Re: [abinit-forum] p4_error: interrupt SIGx: 13 in band structure calculation
Date: Thu, 1 Jun 2006 08:59:38 +0200
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=nQANsQw51/HlPm4w4OT89z1O2MDz4CH3erjhtrZa710tI/mVquzXGtV8YXcdawoWZqzTblU1QfWAkyUxq2OvHehlv3VJookLLREemTgpBa3NUjx9Gd9NCDNtN/oBUgqgfIGRnoi6enFsg8WeUmygrRl8Bk67wDwKX3DhXA4Xcqk=

Is this problem related to the memory size??

It doesn't look like beeing memory linked

Would you give me any comments?

-> process 0 died first because of the signal number 13
-> other processes died because of error number 32
:-)
A little bit criptic isn't it?
On posix systems (you're not running windows do you?)
SIG 13 means broken pipe (see you signum.h file)
#define SIGPIPE 13 /* Broken pipe (POSIX). */

And If you are running linux on a x86_64 as I do this means that:
the errno 32 also means broken pipe (see errno.h)
#define EPIPE 32 /* Broken pipe */

It looks like a communication problems.
Yet I'm not at all an expert and I can't tell you if this comes from
a) abinit
b) your mpi layer
c) your system

regards

PMA

Best regards,
Yunhee Chang

--
Pierre-Matthieu Anglade

p4_error: interrupt SIGx: 13 in band structure calculation, yhjang, 06/01/2006
- Re: [abinit-forum] p4_error: interrupt SIGx: 13 in band structure calculation, Anglade Pierre-Matthieu, 06/01/2006
  - Re: Re: [abinit-forum] p4_error: interrupt SIGx: 13 in band structurecalculation, Hai-Ping Lan, 06/01/2006