log in

193 (0x000000C1) EXIT_SIGNAL

Message boards : Questions/Problems/Bugs : 193 (0x000000C1) EXIT_SIGNAL
Message board moderation

To post messages, you must log in.

AuthorMessage
bozz4science

Send message
Joined: 7 May 20
Posts: 1
Credit: 311,916
RAC: 0
Message 2105 - Posted: 11 Sep 2020, 10:09:31 UTC
Last modified: 11 Sep 2020, 10:14:03 UTC

Recently, I have been getting a lot of error messages. It only applies to 16e Lattice Sieve V5 tasks so far, but all of the WUs on my system error out after ~2 min.

The errored-out WUs show the following output in the stderr_txt file. Pls advice as to what might cause this error as I am kind of clueless here. The system is a 64 bit MacOS system.

<core_client_version>7.16.11</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)</message>
<stderr_txt>
boinc initialized
work files resolved, now working
-> lasieve5f_1.11_x86_64-apple-darwin
-> -r
-> -f
-> 925556000
-> -c
-> 2000
-> -R
-> -o
-> ../../projects/escatter11.fullerton.edu_nfs/S3p668_925556_0_r888688854_0
-> ../../projects/escatter11.fullerton.edu_nfs/S3p668.poly
SIGSEGV: segmentation violation

Crashed executable name: lasieve5f_1.11_x86_64-apple-darwin
built using BOINC library version 7.5.0
Machine type Intel x86-64h Haswell (64-bit executable)
System version: Macintosh OS 10.15.6 build 19G2021
Fri Sep 11 09:33:57 2020

atos cannot load symbols for the file lasieve5f_1.11_x86_64-apple-darwin for architecture x86_64.
0 lasieve5f_1.11_x86_64-apple-darwin 0x000000010007d21c
SIGPIPE: write on a pipe with no reader
1 lasieve5f_1.11_x86_64-apple-darwin 0x0000000100071ad7
SIGPIPE: write on a pipe with no reader
2 libsystem_platform.dylib 0x00007fff6fd505fd
SIGPIPE: write on a pipe with no reader
3 libsystem_kernel.dylib 0x00007fff6fc9a241

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0100001f rbx: 0x00000003 rcx: 0x7ffeefbfbdc8 rdx: 0x00000028
rdi: 0x7ffeefbfbe38 rsi: 0x00000003 rbp: 0x7ffeefbfbe20 rsp: 0x7ffeefbfbdc8
r8: 0x00000607 r9: 0x00000000 r10: 0x000009c8 r11: 0x00000206
r12: 0x00000003 r13: 0x000009c8 r14: 0x7ffeefbfbe38 r15: 0x00000028
rip: 0x7fff6fc98dfa rfl: 0x00000206

Binary Images Description:
0x100000000 - 0x10009bfff /Library/Application Support/BOINC Data/slots/4/../../projects/escatter11.fullerton.edu_nfs/lasieve5f_1.11_x86_64-apple-darwin
0x7fff6cb3c000 - 0x7fff6cb3dfff /usr/lib/libSystem.B.dylib
0x7fff6ce22000 - 0x7fff6ce74fff /usr/lib/libc++.1.dylib
0x7fff6ce75000 - 0x7fff6ce8afff /usr/lib/libc++abi.dylib
0x7fff6e99c000 - 0x7fff6e9cffff /usr/lib/libobjc.A.dylib
0x7fff6ee25000 - 0x7fff6ee6ffff /usr/lib/libstdc++.6.dylib
0x7fff6f939000 - 0x7fff6f93efff /usr/lib/system/libcache.dylib
0x7fff6f93f000 - 0x7fff6f94afff /usr/lib/system/libcommonCrypto.dylib
0x7fff6f94b000 - 0x7fff6f952fff /usr/lib/system/libcompiler_rt.dylib
0x7fff6f953000 - 0x7fff6f95cfff /usr/lib/system/libcopyfile.dylib
0x7fff6f95d000 - 0x7fff6f9effff /usr/lib/system/libcorecrypto.dylib
0x7fff6fafc000 - 0x7fff6fb3cfff /usr/lib/system/libdispatch.dylib
0x7fff6fb3d000 - 0x7fff6fb73fff /usr/lib/system/libdyld.dylib
0x7fff6fb74000 - 0x7fff6fb74fff /usr/lib/system/libkeymgr.dylib
0x7fff6fb82000 - 0x7fff6fb82fff /usr/lib/system/liblaunch.dylib
0x7fff6fb83000 - 0x7fff6fb88fff /usr/lib/system/libmacho.dylib
0x7fff6fb89000 - 0x7fff6fb8bfff /usr/lib/system/libquarantine.dylib
0x7fff6fb8c000 - 0x7fff6fb8dfff /usr/lib/system/libremovefile.dylib
0x7fff6fb8e000 - 0x7fff6fba5fff /usr/lib/system/libsystem_asl.dylib
0x7fff6fba6000 - 0x7fff6fba6fff /usr/lib/system/libsystem_blocks.dylib
0x7fff6fba7000 - 0x7fff6fc2efff /usr/lib/system/libsystem_c.dylib
0x7fff6fc2f000 - 0x7fff6fc32fff /usr/lib/system/libsystem_configuration.dylib
0x7fff6fc33000 - 0x7fff6fc36fff /usr/lib/system/libsystem_coreservices.dylib
0x7fff6fc37000 - 0x7fff6fc3ffff /usr/lib/system/libsystem_darwin.dylib
0x7fff6fc40000 - 0x7fff6fc47fff /usr/lib/system/libsystem_dnssd.dylib
0x7fff6fc48000 - 0x7fff6fc49fff /usr/lib/system/libsystem_featureflags.dylib
0x7fff6fc4a000 - 0x7fff6fc97fff /usr/lib/system/libsystem_info.dylib
0x7fff6fc98000 - 0x7fff6fcc4fff /usr/lib/system/libsystem_kernel.dylib
0x7fff6fcc5000 - 0x7fff6fd0cfff /usr/lib/system/libsystem_m.dylib
0x7fff6fd0d000 - 0x7fff6fd34fff /usr/lib/system/libsystem_malloc.dylib
0x7fff6fd35000 - 0x7fff6fd42fff /usr/lib/system/libsystem_networkextension.dylib
0x7fff6fd43000 - 0x7fff6fd4cfff /usr/lib/system/libsystem_notify.dylib
0x7fff6fd4d000 - 0x7fff6fd55fff /usr/lib/system/libsystem_platform.dylib
0x7fff6fd56000 - 0x7fff6fd60fff /usr/lib/system/libsystem_pthread.dylib
0x7fff6fd61000 - 0x7fff6fd65fff /usr/lib/system/libsystem_sandbox.dylib
0x7fff6fd66000 - 0x7fff6fd68fff /usr/lib/system/libsystem_secinit.dylib
0x7fff6fd69000 - 0x7fff6fd70fff /usr/lib/system/libsystem_symptoms.dylib
0x7fff6fd71000 - 0x7fff6fd87fff /usr/lib/system/libsystem_trace.dylib
0x7fff6fd89000 - 0x7fff6fd8efff /usr/lib/system/libunwind.dylib
0x7fff6fd8f000 - 0x7fff6fdc4fff /usr/lib/system/libxpc.dylib


Exiting...

</stderr_txt>
]]>


Edit: I have just seen one WU 16e validated successfully and I 2 other WUs well beyond the 2 min mark which should finish and upload soon....
ID: 2105 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
sweede

Send message
Joined: 14 Sep 11
Posts: 1
Credit: 322,934
RAC: 0
Message 2132 - Posted: 7 Mar 2021, 9:50:38 UTC - in response to Message 2105.  

Got the same error on multiple tasks.

See https://escatter11.fullerton.edu/nfs/result.php?resultid=222140912 for reference.
ID: 2132 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
xii5ku

Send message
Joined: 26 Jul 17
Posts: 4
Credit: 70,673,304
RAC: 0
Message 2160 - Posted: 12 May 2021, 20:29:59 UTC

I am seeing this failure (SIGSEV) too, on a linux computer. Have yet to try another computer.

It gets weirder: After the scheduler received the failure result, it creates a replica task and may send the replica to the very same host, naturally with the same outcome. Speak of flogging a dead horse.
ID: 2160 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
shift
Avatar

Send message
Joined: 29 Jun 18
Posts: 6
Credit: 568,920
RAC: 0
Message 2264 - Posted: 5 Jan 2022, 8:34:01 UTC - in response to Message 2160.  
Last modified: 5 Jan 2022, 8:34:18 UTC

I'm getting this error as well. Only on my mac running macOS 10.15 (not on my mac running macOS 10.13). At least it errors quickly.
ID: 2264 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
shift
Avatar

Send message
Joined: 29 Jun 18
Posts: 6
Credit: 568,920
RAC: 0
Message 2265 - Posted: 5 Jan 2022, 23:21:09 UTC - in response to Message 2264.  

Actually, now I think they run for the entire time and then afterwards error and report the run time was less than 2 minutes. I'll be unticking 16e for that computer I guess.
ID: 2265 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Questions/Problems/Bugs : 193 (0x000000C1) EXIT_SIGNAL


Home | My Account | Message Boards