topic cilk runtime error in Software Archive

cilk runtime error

chavhan__hitesh — Tue, 22 Apr 2014 05:48:52 GMT

I am using MYO model for offloading my code to MIC but it I am getting some sort of runtime errors .Is this errors are code related or some system issues.

CARD--ERROR:1 _myoiPageFaultHandler: 0x44108b068 switch to default signal handle
CARD--ERROR:1 Segment Fault!
HOST--ERROR:myoiScifGetRecvId: Call recv() Header Failed ! for source: 1, errno = 104
HOST--ERROR:myoiScifSend: Call send() Failed! errno = 104
HOST--ERROR:myoiSend: Fail to send message!
HOST--ERROR:_myoiWatchdogDaemon: could not send to target: 1
offload error: process on the device 0 unexpectedly exited with code 1

It does not necessarily imply

Kevin_D_Intel — Tue, 22 Apr 2014 17:09:32 GMT

It does not necessarily imply a system error. There are two examples noted below exhibiting some of the same messages where the fault was associated with variables used within the offloaded code. One example is not using the _Cilk_shared/_Cilk_offload method, one is.
https://software.intel.com/en-us/forums/topic/393636
https://software.intel.com/en-us/forums/topic/394302
If you can provide a reproducing example of your code then we would be able to help pinpoint the cause.

thanks for the response it

chavhan__hitesh — Wed, 23 Apr 2014 05:22:06 GMT

thanks for the response it helped the error is now not there.

I am facing another runtime issue, check this

HOST--ERROR:myoiOSSetPageAccess: mprotect failed!
Please increase the maximum of memory map areas
i.e. echo 256000 > /proc/sys/vm/max_map_count
offload error: process on the device 0 unexpectedly exited with code 1
HOST--ERROR:myoiThreadMutexDestroy1: Fail to destroy a mutex (0x1543508)! error: 16
HOST--ERROR:myoiOSDetachSharedMemory: shmdt failed: Invalid argument
HOST--ERROR:myoiOSDetachSharedMemory: shmdt failed: Invalid argument
HOST--ERROR:myoiOSDestroySharedMemory: shmctl failed: Invalid argument

Please refer to the response

Kevin_D_Intel — Wed, 30 Apr 2014 08:41:20 GMT

Please refer to the response here for more details and a resolution.