**From:** Bryan Roessler (*roessler_at_uab.edu*)

**Date:** Mon Jun 24 2013 - 09:52:36 CDT

**Next message:**James Starlight: "Re: Protein-ligand simulation"**Previous message:**Chris Chipot: "Re: Protein-ligand simulation"**Messages sorted by:**[ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Anyone have an idea of what's going on here...this has just started

happening recently on 2.8 and 2.9.

Info: Reading from binary file sim50.coor

Info:

Info: Entering startup at 11.0477 s, 354.359 MB of memory in use

[0] wc[0] status 12 wc[i].opcode 0

[0] wc[0] status 5 wc[i].opcode 0

[0] wc[1] status 5 wc[i].opcode 3671259

[0] Stack Traceback:

[0:0] CmiAbort+0x5c [0xbf56fa]

[0:1] /share/apps/namd/NAMD_2.8_Linux-x86_64-ibverbs/namd2 [0xbee7ec]

[0:2] /share/apps/namd/NAMD_2.8_Linux-x86_64-ibverbs/namd2 [0xbf9a3a]

[0:3] CcdRaiseCondition+0x59 [0xbf9879]

[0:4] CsdScheduleForever+0x111 [0xbf6737]

[0:5] CsdScheduler+0x1c [0xbf62cc]

[0:6] _ZN7BackEnd7suspendEv+0xb [0x53e321]

[0:7] _ZN9ScriptTcl9initcheckEv+0x80 [0xa7c2a4]

[0:8] _ZN9ScriptTcl14Tcl_reinitvelsEPvP10Tcl_InterpiPPc+0x1d [0xa7c067]

[0:9] TclInvokeStringCommand+0x91 [0xc24c18]

[0:10] TclExecuteByteCode+0x856 [0xc3f4ff]

[0:11] Tcl_EvalObjEx+0x2bb [0xc2562b]

[0:12] Tcl_WhileObjCmd+0x6a [0xc31dad]

[0:13] /share/apps/namd/NAMD_2.8_Linux-x86_64-ibverbs/namd2 [0xc5aa68]

[0:14] Tcl_EvalEx+0x176 [0xc5b0ab]

[0:15] Tcl_EvalFile+0x134 [0xc52ab4]

[0:16] _ZN9ScriptTcl4loadEPc+0x10 [0xa77d82]

[0:17] _Z18after_backend_initiPPc+0x448 [0x539c08]

[0:18] main+0x3a [0x53978a]

[0:19] __libc_start_main+0xf4 [0x39ec01d9c4]

[0:20] _ZNSt8ios_base4InitD1Ev+0x52 [0x534d7a]

And my node file:

Got 128 slots.

group main

host sipsey-compute-2-14

host sipsey-compute-2-14

host sipsey-compute-2-14

host sipsey-compute-1-15

host sipsey-compute-1-15

host sipsey-compute-1-15

host sipsey-compute-1-15

host sipsey-compute-1-1

host sipsey-compute-1-1

host sipsey-compute-1-1

host sipsey-compute-1-1

host sipsey-compute-1-1

host sipsey-compute-0-10

host sipsey-compute-0-10

host sipsey-compute-1-9

host sipsey-compute-0-2

host sipsey-compute-0-12

host sipsey-compute-2-8

host sipsey-compute-1-2

host sipsey-compute-1-2

host sipsey-compute-1-2

host sipsey-compute-0-14

host sipsey-compute-0-14

host sipsey-compute-2-5

host sipsey-compute-2-5

host sipsey-compute-2-5

host sipsey-compute-2-5

host sipsey-compute-0-16

host sipsey-compute-0-16

host sipsey-compute-2-12

host sipsey-compute-2-12

host sipsey-compute-0-8

host sipsey-compute-0-8

host sipsey-compute-0-8

host sipsey-compute-0-5

host sipsey-compute-0-5

host sipsey-compute-0-5

host sipsey-compute-0-5

host sipsey-compute-0-5

host sipsey-compute-1-10

host sipsey-compute-1-10

host sipsey-compute-1-10

host sipsey-compute-1-10

host sipsey-compute-2-11

host sipsey-compute-2-11

host sipsey-compute-2-11

host sipsey-compute-2-16

host sipsey-compute-2-16

host sipsey-compute-2-16

host sipsey-compute-2-1

host sipsey-compute-2-1

host sipsey-compute-2-1

host sipsey-compute-2-1

host sipsey-compute-2-1

host sipsey-compute-0-3

host sipsey-compute-0-3

host sipsey-compute-0-4

host sipsey-compute-0-4

host sipsey-compute-0-4

host sipsey-compute-0-15

host sipsey-compute-0-15

host sipsey-compute-0-15

host sipsey-compute-0-1

host sipsey-compute-0-1

host sipsey-compute-0-1

host sipsey-compute-2-4

host sipsey-compute-2-4

host sipsey-compute-2-4

host sipsey-compute-2-15

host sipsey-compute-2-15

host sipsey-compute-2-15

host sipsey-compute-2-15

host sipsey-compute-2-15

host sipsey-compute-2-15

host sipsey-compute-2-2

host sipsey-compute-2-2

host sipsey-compute-2-2

host sipsey-compute-2-7

host sipsey-compute-2-7

host sipsey-compute-2-7

host sipsey-compute-2-7

host sipsey-compute-2-7

host sipsey-compute-2-7

host sipsey-compute-1-14

host sipsey-compute-1-14

host sipsey-compute-1-14

host sipsey-compute-1-3

host sipsey-compute-1-3

host sipsey-compute-1-3

host sipsey-compute-1-11

host sipsey-compute-1-11

host sipsey-compute-1-11

host sipsey-compute-0-13

host sipsey-compute-0-13

host sipsey-compute-1-4

host sipsey-compute-1-4

host sipsey-compute-1-4

host sipsey-compute-0-11

host sipsey-compute-0-11

host sipsey-compute-0-11

host sipsey-compute-2-3

host sipsey-compute-2-3

host sipsey-compute-2-3

host sipsey-compute-2-9

host sipsey-compute-2-9

host sipsey-compute-2-9

host sipsey-compute-2-9

host sipsey-compute-2-9

host sipsey-compute-2-9

host sipsey-compute-1-16

host sipsey-compute-1-16

host sipsey-compute-2-13

host sipsey-compute-2-13

host sipsey-compute-2-13

host sipsey-compute-0-6

host sipsey-compute-0-6

host sipsey-compute-0-6

host sipsey-compute-1-7

host sipsey-compute-1-7

host sipsey-compute-1-7

host sipsey-compute-1-7

host sipsey-compute-1-7

host sipsey-compute-1-7

host sipsey-compute-1-12

host sipsey-compute-1-12

host sipsey-compute-1-12

host sipsey-compute-1-12

host sipsey-compute-1-12

Charmrun> started all node programs in 4.347 seconds.

------------- Processor 0 Exiting: Called CmiAbort ------------

Reason: Wrong type of work completion object in recvq

Fatal error on PE 0> Wrong type of work completion object in recvq

*Bryan Roessler | Graduate Research Assistant*

UAB | The University of Alabama at Birmingham

*uab.edu/cmdb*

Knowledge that will change your world

**Next message:**James Starlight: "Re: Protein-ligand simulation"**Previous message:**Chris Chipot: "Re: Protein-ligand simulation"**Messages sorted by:**[ date ] [ thread ] [ subject ] [ author ] [ attachment ]

*
This archive was generated by hypermail 2.1.6
: Tue Dec 31 2013 - 23:23:22 CST
*