Linux Invalid Taskunit

Message boards : Number crunching : Linux Invalid Taskunit
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Steve S

Send message
Joined: 3 Apr 99
Posts: 33
Credit: 751,581
RAC: 0
Canada
Message 932578 - Posted: 11 Sep 2009, 21:17:01 UTC

A quick question about some of my tasks that are failing. I am running BOINC 6.6.36 with a Linux ptimized S@H Enhanced application V5.13; application version 5.28, and I am getting a number of workunits in the last few weeks that are getting the following stderr out

<core_client_version>6.6.36</core_client_version>
<![CDATA[
<message>
process exited with code 131 (0x83, -125)
</message>
<stderr_txt>
Linux optimized S@H Enhanced application by Alex Kan
Version info: SSSE3x (Intel, Core 2-optimized v8-nographics) V5.13 by Alex Kan
SSSE3x Linux64 Build 46 PGO, Ported by : Jason G, Raistmer, JDWhale

Processor Information:
  Model: Intel Core 2 Duo E6550, 2.33 GHz
  Package: 2 Cores

Processor Caches:
  L1 code cache, 32 KB
  L1 data cache, 32 KB
  L2 combined cache, 4 MB

Processor Features:   64bit   simd   [x86]   cmov   mmx   sse   sse2   sse3   ssse3   vmx   lm   lahf_lm   tm   tm2   eist   nx 

Work Unit Info:
...............
Credit multiplier is :  2.85
WU true angle range is :  0.435611
terminate called after throwing an instance of 'std::bad_alloc'
  what():  St9bad_alloc
SIGABRT: abort calledStack trace (18 frames):
AK_V8_linux64_ssse3(boinc_catch_signal+0x17d)[0x43b70d]
/lib/libpthread.so.0[0x7f3529fa6080]
/lib/libc.so.6(gsignal+0x35)[0x7f3529c57fb5]
/lib/libc.so.6(abort+0x183)[0x7f3529c59bc3]
AK_V8_linux64_ssse3[0x576234]
AK_V8_linux64_ssse3[0x56a706]
AK_V8_linux64_ssse3[0x56a733]
AK_V8_linux64_ssse3[0x56cafa]
AK_V8_linux64_ssse3[0x56c539]
AK_V8_linux64_ssse3[0x5cf0df]
AK_V8_linux64_ssse3[0x5bd1c5]
AK_V8_linux64_ssse3[0x419d0a]
AK_V8_linux64_ssse3[0x415950]
AK_V8_linux64_ssse3[0x4149a2]
AK_V8_linux64_ssse3[0x405f7a]
AK_V8_linux64_ssse3[0x405612]
/lib/libc.so.6(__libc_start_main+0xe6)[0x7f3529c435a6]
AK_V8_linux64_ssse3(realloc+0x181)[0x405379]

Exiting...

</stderr_txt>
]]>


Could anyone tell me what is going on and/or how to correct it? Thanks to all who respond !
ID: 932578 · Report as offensive
DJStarfox

Send message
Joined: 23 May 01
Posts: 1066
Credit: 1,226,053
RAC: 2
United States
Message 932588 - Posted: 11 Sep 2009, 22:15:52 UTC - in response to Message 932578.  

You need to use the SSE2 optimized application instead:
http://lunatics.kwsn.net/linux/64-bit-sse2-app.15.html
ID: 932588 · Report as offensive
Urs Echternacht
Volunteer tester
Avatar

Send message
Joined: 15 May 99
Posts: 692
Credit: 135,197,781
RAC: 211
Germany
Message 932589 - Posted: 11 Sep 2009, 22:24:17 UTC - in response to Message 932588.  

You need to use the SSE2 optimized application instead:
http://lunatics.kwsn.net/linux/64-bit-sse2-app.15.html

@DJStarfox:
No, this is NOT Astropulse 5.03

@Steve S:
which linux do you use ?
_\|/_
U r s
ID: 932589 · Report as offensive
Profile Steve S

Send message
Joined: 3 Apr 99
Posts: 33
Credit: 751,581
RAC: 0
Canada
Message 932592 - Posted: 11 Sep 2009, 22:32:19 UTC - in response to Message 932589.  

I am using Ubuntu 9.04, but the the kernal is Linux 2.6.28-15-generic
***************************************
-Steve
ID: 932592 · Report as offensive
Urs Echternacht
Volunteer tester
Avatar

Send message
Joined: 15 May 99
Posts: 692
Credit: 135,197,781
RAC: 211
Germany
Message 932596 - Posted: 11 Sep 2009, 22:42:45 UTC - in response to Message 932592.  
Last modified: 11 Sep 2009, 22:44:56 UTC

I am using Ubuntu 9.04, but the the kernal is Linux 2.6.28-15-generic

If you need kernel 2.6.28 then there is "currently" nothing you can do.

BUT if not, try kernel version 2.6.27, which should works without errors.
_\|/_
U r s
ID: 932596 · Report as offensive
DJStarfox

Send message
Joined: 23 May 01
Posts: 1066
Credit: 1,226,053
RAC: 2
United States
Message 933511 - Posted: 15 Sep 2009, 13:39:26 UTC - in response to Message 932589.  

Sorry for my confusion, Steve. Did you try what the others have suggested?

Perhaps you could revert back to the stock SETI application for MB and see if that makes a difference? If that works, then at least you can wait for the bugfix from the AK team. If not, then we'll have to investigate further into your system/kernel/etc.
ID: 933511 · Report as offensive

Message boards : Number crunching : Linux Invalid Taskunit


 
©2025 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.