Message boards : Number crunching : Mac OS X Errors
Message board moderation

To post messages, you must log in.

1 · 2 · Next

AuthorMessage
alephnull

Send message
Joined: 2 Dec 05
Posts: 11
Credit: 2,660,795
RAC: 0
Message 24043 - Posted: 3 Jul 2012, 22:24:10 UTC

apologies in advance if im posting this question in the wrong place. i looked at the q&a section for unix/linux related issues and the threads there all seem to be quite old.

i got pretty excited recently when lhc started having work again so i wanted to crunch on my mac too. attempts today to do this have all ended in errors for

this host's tasks and
this host's tasks

i see on the applications page there is a mac app for sixtrack:

Intel 64-bit Mac OS 10.5 or later
444.01
3 Jul 2012 | 19:18:48 UTC

all the wu seemed to get the same error. here's an example:

<core_client_version>7.0.25</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
SIGBUS: bus error

Crashed executable name: sixtrack_apple_gen
Machine type Intel 80486 (32-bit executable)
System version: Macintosh OS 10.7.4 build 11E53
Tue Jul 3 17:45:00 2012

0 sixtrack_apple_gen 0x0020df9e PrintBacktrace (in sixtrack_apple_gen) + 1022

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xffffffe1 ebx: 0x00000003 ecx: 0xbfffa61c edx: 0x92166c22
edi: 0xbfffa678 esi: 0x00000003 ebp: 0xbfffa648 esp: 0xbfffa61c
ss: 0x00000023 efl: 0x00000206 eip: 0x92166c22 cs: 0x0000000b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f

Binary Images Description:
0x1000 - 0x31ffff /Library/Application Support/BOINC Data/slots/8/../../projects/lhcathomeclassic.cern.ch_sixtrack/sixtrack_apple_gen
0x90626000 - 0x90627fff /usr/lib/system/libunc.dylib
0x90783000 - 0x90786fff /usr/lib/system/libmathCommon.A.dylib
0x91085000 - 0x9108dfff /usr/lib/system/libcopyfile.dylib
0x911f1000 - 0x911f1fff /usr/lib/system/libdnsinfo.dylib
0x91de2000 - 0x91de9fff /usr/lib/system/libsystem_notify.dylib
0x92150000 - 0x9216efff /usr/lib/system/libsystem_kernel.dylib
0x92209000 - 0x9220efff /usr/lib/system/libmacho.dylib
0x940bb000 - 0x94186fff /usr/lib/system/libsystem_c.dylib
0x94eb6000 - 0x94eccfff /usr/lib/system/libxpc.dylib
0x96040000 - 0x96044fff /usr/lib/system/libsystem_network.dylib
0x9631a000 - 0x96349fff /usr/lib/system/libsystem_info.dylib
0x97944000 - 0x97952fff /usr/lib/system/libdispatch.dylib
0x9829f000 - 0x982a3fff /usr/lib/system/libcache.dylib
0x982a4000 - 0x982d2fff /usr/lib/libSystem.B.dylib
0x9838b000 - 0x983cefff /usr/lib/system/libcommonCrypto.dylib
0x983cf000 - 0x983d1fff /usr/lib/system/libdyld.dylib
0x983d2000 - 0x983d3fff /usr/lib/system/libquarantine.dylib
0x9a47e000 - 0x9a486fff /usr/lib/system/liblaunch.dylib
0x9aa2e000 - 0x9aa31fff /usr/lib/system/libcompiler_rt.dylib
0x9ab22000 - 0x9ab2afff /usr/lib/system/libunwind.dylib
0x9aeae000 - 0x9aeaffff /usr/lib/system/libremovefile.dylib
0x9bcc2000 - 0x9bcc2fff /usr/lib/system/libkeymgr.dylib
0x9bcc3000 - 0x9bccafff /usr/lib/system/libsystem_dnssd.dylib
0x9bd3c000 - 0x9bd3dfff /usr/lib/system/libsystem_sandbox.dylib
0x9be6f000 - 0x9be70fff /usr/lib/system/libsystem_blocks.dylib


Exiting...

</stderr_txt>
]]>

---------------------

of the two macs, one is a mac mini and the other is a macbook air. both are running os x lion 10.7.4. im not too familiar with mac or unix/linux so any information you can provide youll have to treat me like a new guy.

this thread seems to indicate working towards some apps for mac. i dont know if the sixtrack app being used is the correct version. it would be nice to get these two machines running sixtrack. they have had boinc installed and have been running other projects for quite a while now so i know they are stable. just having difficulty right now trying to get sixtrack working.

thanks for any help or information you can provide.

rob
ID: 24043 · Report as offensive     Reply Quote
Profile Igor Zacharov
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 16 May 11
Posts: 79
Credit: 111,419
RAC: 0
Message 24044 - Posted: 3 Jul 2012, 22:34:53 UTC - in response to Message 24043.  

thank you for the warning.

The MAC version was indeed intended for Apple machines with Intel processors.
I think we need to analyze this one to see why it is crashing.

Sorry about the difficulties.

Igor.
skype id: igor-zacharov
ID: 24044 · Report as offensive     Reply Quote
alephnull

Send message
Joined: 2 Dec 05
Posts: 11
Credit: 2,660,795
RAC: 0
Message 24045 - Posted: 3 Jul 2012, 22:57:56 UTC - in response to Message 24044.  

thank you for the warning.

The MAC version was indeed intended for Apple machines with Intel processors.
I think we need to analyze this one to see why it is crashing.

Sorry about the difficulties.

Igor.

i dont think the difficulties are based on the processor. the mac mini has an i7 and the macbook air has an i5, both of which are 64 bit i believe. the two machines are no more than a year and a half old.

if there is more information you would like me to provide regarding this, please let me know.

thanks.

rob
ID: 24045 · Report as offensive     Reply Quote
superempie

Send message
Joined: 28 Jul 05
Posts: 24
Credit: 6,603,623
RAC: 0
Message 24056 - Posted: 4 Jul 2012, 15:48:25 UTC
Last modified: 4 Jul 2012, 15:50:06 UTC

I'm getting only computation errors with the 444.01 application on my two Mac OS X machines (one hackintosh, one 27" iMac) ranging between 0 and a few seconds computation time. Both are stable at other projects.
Both are Intel based and running Lion. Tried updating Boinc to the latst version, but that didn't help either.

Log of one of them:
<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
SIGBUS: bus error

Crashed executable name: sixtrack_apple_gen
Machine type Intel 80486 (32-bit executable)
System version: Macintosh OS 10.7.4 build 11E53
Wed Jul  4 17:40:36 2012

atos cannot load symbols for the file sixtrack_apple_gen for architecture i386.
0   sixtrack_apple_gen                  0x0020df9e  

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0xffffffe1 ebx: 0x00000003 ecx: 0xbfffa61c edx: 0x985cdc22
  edi: 0xbfffa678 esi: 0x00000003 ebp: 0xbfffa648 esp: 0xbfffa61c
   ss: 0x00000023 efl: 0x00000206 eip: 0x985cdc22  cs: 0x0000000b
   ds: 0x00000023  es: 0x00000023  fs: 0x00000000  gs: 0x0000000f

Binary Images Description:
    0x1000 -   0x31ffff /Library/Application Support/BOINC Data/slots/4/../../projects/lhcathomeclassic.cern.ch_sixtrack/sixtrack_apple_gen
0x90497000 - 0x9049cfff /usr/lib/system/libmacho.dylib
0x90585000 - 0x9058cfff /usr/lib/system/libsystem_dnssd.dylib
0x90c43000 - 0x90c44fff /usr/lib/system/libquarantine.dylib
0x91231000 - 0x91231fff /usr/lib/system/libkeymgr.dylib
0x9130e000 - 0x9130ffff /usr/lib/system/libsystem_blocks.dylib
0x91a4d000 - 0x91a5bfff /usr/lib/system/libdispatch.dylib
0x91b21000 - 0x91b50fff /usr/lib/system/libsystem_info.dylib
0x92c24000 - 0x92c26fff /usr/lib/system/libdyld.dylib
0x93274000 - 0x9328afff /usr/lib/system/libxpc.dylib
0x93dae000 - 0x93daffff /usr/lib/system/libremovefile.dylib
0x9483c000 - 0x9483dfff /usr/lib/system/libunc.dylib
0x94a64000 - 0x94a64fff /usr/lib/system/libdnsinfo.dylib
0x965c8000 - 0x965d0fff /usr/lib/system/libunwind.dylib
0x9660b000 - 0x9660efff /usr/lib/system/libmathCommon.A.dylib
0x96f11000 - 0x96f3ffff /usr/lib/libSystem.B.dylib
0x97e40000 - 0x97e44fff /usr/lib/system/libsystem_network.dylib
0x984c0000 - 0x984c7fff /usr/lib/system/libsystem_notify.dylib
0x984e9000 - 0x984f1fff /usr/lib/system/libcopyfile.dylib
0x985b7000 - 0x985d5fff /usr/lib/system/libsystem_kernel.dylib
0x98884000 - 0x98885fff /usr/lib/system/libsystem_sandbox.dylib
0x98886000 - 0x98889fff /usr/lib/system/libcompiler_rt.dylib
0x99959000 - 0x9995dfff /usr/lib/system/libcache.dylib
0x9b827000 - 0x9b86afff /usr/lib/system/libcommonCrypto.dylib
0x9bad8000 - 0x9bba3fff /usr/lib/system/libsystem_c.dylib
0x9cc19000 - 0x9cc21fff /usr/lib/system/liblaunch.dylib


Exiting...

</stderr_txt>
]]>

ID: 24056 · Report as offensive     Reply Quote
Eric Mcintosh
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 12 Jul 11
Posts: 857
Credit: 1,619,050
RAC: 0
Message 24057 - Posted: 4 Jul 2012, 16:42:33 UTC

THANKS this is very interesting and helpful
MACs are a new venture for us. I'll keep you posted.
Eric.
ID: 24057 · Report as offensive     Reply Quote
superempie

Send message
Joined: 28 Jul 05
Posts: 24
Credit: 6,603,623
RAC: 0
Message 24063 - Posted: 4 Jul 2012, 19:25:46 UTC

No problem. If I can help more, please email me.
ID: 24063 · Report as offensive     Reply Quote
pbeaudet

Send message
Joined: 5 Dec 09
Posts: 2
Credit: 149,679
RAC: 0
Message 24111 - Posted: 7 Jul 2012, 5:56:30 UTC - in response to Message 24057.  
Last modified: 7 Jul 2012, 5:58:40 UTC

I just discovered that SixTrack can run on a 64-bit mac. I have two, an i7 and Core2 Duo. It is too soon to see if I have any crashes.

I hope I can be of some help.

Philip
ID: 24111 · Report as offensive     Reply Quote
alephnull

Send message
Joined: 2 Dec 05
Posts: 11
Credit: 2,660,795
RAC: 0
Message 24112 - Posted: 7 Jul 2012, 6:47:01 UTC - in response to Message 24043.  

I just discovered that SixTrack can run on a 64-bit mac. I have two, an i7 and Core2 Duo. It is too soon to see if I have any crashes.

I hope I can be of some help.

Philip

hopefully youll have success. according to the applications page there should be a 64 bit mac version. according to the errors i got it seemed to me like my mac was using a 32 bit version but im not sure:



...
<core_client_version>7.0.25</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
SIGBUS: bus error

Crashed executable name: sixtrack_apple_gen
Machine type Intel 80486 (32-bit executable)

System version: Macintosh OS 10.7.4 build 11E53
Tue Jul 3 17:45:00 2012
...

that error was on a mac mini with an i7 processor so i dont know if that machine may have downloaded the wrong application for some reason. i would assume it should have downloaded the 64 bit app? the boinc client runs in 32 bit mode on that mac but for other projects that have 64 bit apps, they run fine.

rob
ID: 24112 · Report as offensive     Reply Quote
Eric Mcintosh
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 12 Jul 11
Posts: 857
Credit: 1,619,050
RAC: 0
Message 24122 - Posted: 7 Jul 2012, 19:38:30 UTC

All our excutablesiare 32-bit but they run on 64-bit
systems OK. Well at least on some....
More news soonest. Eric.
ID: 24122 · Report as offensive     Reply Quote
alephnull

Send message
Joined: 2 Dec 05
Posts: 11
Credit: 2,660,795
RAC: 0
Message 24125 - Posted: 7 Jul 2012, 21:03:18 UTC - in response to Message 24122.  

All our excutablesiare 32-bit but they run on 64-bit
systems OK. Well at least on some....
More news soonest. Eric.

thanks for the explanation on the executables. will wait to hear more before i attempt lhc on those machines again.

if theres any other information you would like to know about these machines to help diagnose any problems, please let me know.

thanks for the update.

rob
ID: 24125 · Report as offensive     Reply Quote
Xtampida

Send message
Joined: 22 Sep 08
Posts: 1
Credit: 34,764
RAC: 0
Message 24151 - Posted: 8 Jul 2012, 10:55:19 UTC

Same problem here. Nine tasks, nine errors.

Lion 10.7.3 on a Hackintosh: Intel(R) Celeron(R) CPU E3300 @ 2.50GHz [x86 Family 6 Model 23 Stepping 10]
ID: 24151 · Report as offensive     Reply Quote
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 12 Jul 11
Posts: 76
Credit: 1,064,445
RAC: 0
Message 24163 - Posted: 8 Jul 2012, 20:06:29 UTC - in response to Message 24151.  
Last modified: 8 Jul 2012, 20:07:09 UTC

Same for me on my i7 860, standard iMac late 2009 with Lion :

Stderr output

<core_client_version>7.0.29</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
SIGBUS: bus error

Crashed executable name: sixtrack_apple_gen
Machine type Intel 80486 (32-bit executable)
System version: Macintosh OS 10.7.4 build 11E53
Sun Jul 8 12:25:40 2012

atos cannot load symbols for the file sixtrack_apple_gen for architecture i386.
0 sixtrack_apple_gen 0x0020df9e

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xffffffe1 ebx: 0x00000003 ecx: 0xbfffa71c edx: 0x9473fc22
edi: 0xbfffa778 esi: 0x00000003 ebp: 0xbfffa748 esp: 0xbfffa71c
ss: 0x00000023 efl: 0x00000206 eip: 0x9473fc22 cs: 0x0000000b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f

Binary Images Description:
0x1000 - 0x31ffff /Library/Application Support/BOINC Data/slots/8/../../projects/lhcathomeclassic.cern.ch_sixtrack/sixtrack_apple_gen
0x90168000 - 0x9016bfff /usr/lib/system/libcompiler_rt.dylib
0x91e2e000 - 0x91e2ffff /usr/lib/system/libsystem_sandbox.dylib
0x929c7000 - 0x929c7fff /usr/lib/system/libdnsinfo.dylib
0x9306d000 - 0x93072fff /usr/lib/system/libmacho.dylib
0x9448c000 - 0x94494fff /usr/lib/system/libcopyfile.dylib
0x946bc000 - 0x946c0fff /usr/lib/system/libsystem_network.dylib
0x94729000 - 0x94747fff /usr/lib/system/libsystem_kernel.dylib
0x94753000 - 0x94753fff /usr/lib/system/libkeymgr.dylib
0x9620f000 - 0x9623efff /usr/lib/system/libsystem_info.dylib
0x9686b000 - 0x96872fff /usr/lib/system/libsystem_dnssd.dylib
0x968c7000 - 0x968d5fff /usr/lib/system/libdispatch.dylib
0x97015000 - 0x97043fff /usr/lib/libSystem.B.dylib
0x97944000 - 0x97945fff /usr/lib/system/libquarantine.dylib
0x98082000 - 0x98084fff /usr/lib/system/libdyld.dylib
0x99938000 - 0x99939fff /usr/lib/system/libsystem_blocks.dylib
0x99a23000 - 0x99a2afff /usr/lib/system/libsystem_notify.dylib
0x99a2b000 - 0x99a33fff /usr/lib/system/liblaunch.dylib
0x9a785000 - 0x9a78dfff /usr/lib/system/libunwind.dylib
0x9b6a1000 - 0x9b6a2fff /usr/lib/system/libunc.dylib
0x9b82f000 - 0x9b830fff /usr/lib/system/libremovefile.dylib
0x9b84f000 - 0x9b865fff /usr/lib/system/libxpc.dylib
0x9be78000 - 0x9be7bfff /usr/lib/system/libmathCommon.A.dylib
0x9c2fc000 - 0x9c3c7fff /usr/lib/system/libsystem_c.dylib
0x9c7fd000 - 0x9c840fff /usr/lib/system/libcommonCrypto.dylib
0x9cc1d000 - 0x9cc21fff /usr/lib/system/libcache.dylib


Exiting...

</stderr_txt>
]]>
ID: 24163 · Report as offensive     Reply Quote
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 12 Jul 11
Posts: 76
Credit: 1,064,445
RAC: 0
Message 24324 - Posted: 13 Jul 2012, 6:22:09 UTC - in response to Message 24163.  

I still have the same errors with the latest WU received, and worse, I see in my account there are other units with "errors while downloading", dated 2 days ago.

<core_client_version>7.0.29</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>w1jul_niebb1d__18__s__64.28_59.31__10.2_10.4__6__34_1_sixvf_boinc31273.zip</file_name>
<error_code>-224</error_code>
<error_message>permanent HTTP error</error_message>
</file_xfer_error>

</message>
]]>
ID: 24324 · Report as offensive     Reply Quote
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 12 Jul 11
Posts: 76
Credit: 1,064,445
RAC: 0
Message 24729 - Posted: 27 Aug 2012, 5:51:45 UTC

I come back from holidays, upgrade boinc as suggested (new official version 7.0.31) and I only have errors from LHC units :

Lun 27 aoû 06:04:57 2012 | LHC@home 1.0 | Starting task wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__33_1_sixvf_boinc26336_0 using sixtrack version 44402 in slot 0
Lun 27 aoû 06:04:59 2012 | LHC@home 1.0 | Computation for task wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__33_1_sixvf_boinc26336_0 finished
Lun 27 aoû 06:04:59 2012 | LHC@home 1.0 | Output file wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__33_1_sixvf_boinc26336_0_0 for task wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__33_1_sixvf_boinc26336_0 absent
Lun 27 aoû 06:04:59 2012 | LHC@home 1.0 | Starting task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__28.5_1_sixvf_boinc26451_0 using sixtrack version 44402 in slot 0
Lun 27 aoû 06:05:00 2012 | LHC@home 1.0 | Computation for task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__28.5_1_sixvf_boinc26451_0 finished
Lun 27 aoû 06:05:00 2012 | LHC@home 1.0 | Output file wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__28.5_1_sixvf_boinc26451_0_0 for task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__28.5_1_sixvf_boinc26451_0 absent
Lun 27 aoû 06:05:00 2012 | LHC@home 1.0 | Starting task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__31.5_1_sixvf_boinc26453_1 using sixtrack version 44402 in slot 0
Lun 27 aoû 06:05:01 2012 | LHC@home 1.0 | Computation for task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__31.5_1_sixvf_boinc26453_1 finished
Lun 27 aoû 06:05:01 2012 | LHC@home 1.0 | Output file wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__31.5_1_sixvf_boinc26453_1_0 for task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__31.5_1_sixvf_boinc26453_1 absent
Lun 27 aoû 06:05:01 2012 | LHC@home 1.0 | Starting task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__4.5_1_sixvf_boinc26435_0 using sixtrack version 44402 in slot 0
Lun 27 aoû 06:05:02 2012 | LHC@home 1.0 | Computation for task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__4.5_1_sixvf_boinc26435_0 finished
Lun 27 aoû 06:05:02 2012 | LHC@home 1.0 | Output file wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__4.5_1_sixvf_boinc26435_0_0 for task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__4.5_1_sixvf_boinc26435_0 absent
Lun 27 aoû 06:05:02 2012 | LHC@home 1.0 | Starting task wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__64.5_1_sixvf_boinc26357_1 using sixtrack version 44402 in slot 0
Lun 27 aoû 06:05:03 2012 | LHC@home 1.0 | Computation for task wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__64.5_1_sixvf_boinc26357_1 finished
Lun 27 aoû 06:05:03 2012 | LHC@home 1.0 | Output file wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__64.5_1_sixvf_boinc26357_1_0 for task wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__64.5_1_sixvf_boinc26357_1 absent
Lun 27 aoû 06:05:03 2012 | LHC@home 1.0 | Starting task wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__88.5_1_sixvf_boinc26373_0 using sixtrack version 44402 in slot 0
Lun 27 aoû 06:05:04 2012 | LHC@home 1.0 | Computation for task wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__88.5_1_sixvf_boinc26373_0 finished
Lun 27 aoû 06:05:04 2012 | LHC@home 1.0 | Output file wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__88.5_1_sixvf_boinc26373_0_0 for task wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__88.5_1_sixvf_boinc26373_0 absent
Lun 27 aoû 06:05:04 2012 | LHC@home 1.0 | Starting task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__3_1_sixvf_boinc26434_0 using sixtrack version 44402 in slot 0
Lun 27 aoû 06:05:05 2012 | LHC@home 1.0 | Computation for task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__3_1_sixvf_boinc26434_0 finished
Lun 27 aoû 06:05:05 2012 | LHC@home 1.0 | Output file wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__3_1_sixvf_boinc26434_0_0 for task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__3_1_sixvf_boinc26434_0 absent
Lun 27 aoû 06:05:05 2012 | LHC@home 1.0 | Starting task wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__76.5_1_sixvf_boinc26365_0 using sixtrack version 44402 in slot 0
Lun 27 aoû 06:05:06 2012 | LHC@home 1.0 | Computation for task wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__76.5_1_sixvf_boinc26365_0 finished
Lun 27 aoû 06:05:06 2012 | LHC@home 1.0 | Output file wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__76.5_1_sixvf_boinc26365_0_0 for task wlxscan_w5cbb__44__s__64.31_59.32__4_5__6__76.5_1_sixvf_boinc26365_0 absent
Lun 27 aoû 06:05:06 2012 | LHC@home 1.0 | Starting task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__64.5_1_sixvf_boinc26475_1 using sixtrack version 44402 in slot 0
Lun 27 aoû 06:05:07 2012 | LHC@home 1.0 | Computation for task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__64.5_1_sixvf_boinc26475_1 finished
Lun 27 aoû 06:05:07 2012 | LHC@home 1.0 | Output file wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__64.5_1_sixvf_boinc26475_1_0 for task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__64.5_1_sixvf_boinc26475_1 absent
Lun 27 aoû 06:05:07 2012 | LHC@home 1.0 | Starting task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__27_1_sixvf_boinc26450_1 using sixtrack version 44402 in slot 0
Lun 27 aoû 06:05:08 2012 | LHC@home 1.0 | Computation for task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__27_1_sixvf_boinc26450_1 finished
Lun 27 aoû 06:05:08 2012 | LHC@home 1.0 | Output file wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__27_1_sixvf_boinc26450_1_0 for task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__27_1_sixvf_boinc26450_1 absent
Lun 27 aoû 06:05:08 2012 | LHC@home 1.0 | Starting task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__72_1_sixvf_boinc26480_0 using sixtrack version 44402 in slot 0
Lun 27 aoû 06:05:09 2012 | LHC@home 1.0 | Computation for task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__72_1_sixvf_boinc26480_0 finished
Lun 27 aoû 06:05:09 2012 | LHC@home 1.0 | Output file wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__72_1_sixvf_boinc26480_0_0 for task wlxscan_w5cbb__45__s__64.31_59.32__4_5__6__72_1_sixvf_boinc26480_0 absent
Lun 27 aoû 06:05:09 2012 | LHC@home 1.0 | Starting task wlxt48_ncebb0d__3__s__64.31_59.32__4.8_5__6__70_1_sixvf_boinc3986_2 using sixtrack version 44402 in slot 0
Lun 27 aoû 06:05:10 2012 | LHC@home 1.0 | Computation for task wlxt48_ncebb0d__3__s__64.31_59.32__4.8_5__6__70_1_sixvf_boinc3986_2 finished
Lun 27 aoû 06:05:10 2012 | LHC@home 1.0 | Output file wlxt48_ncebb0d__3__s__64.31_59.32__4.8_5__6__70_1_sixvf_boinc3986_2_0 for task wlxt48_ncebb0d__3__s__64.31_59.32__4.8_5__6__70_1_sixvf_boinc3986_2 absent
ID: 24729 · Report as offensive     Reply Quote
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 12 Jul 11
Posts: 76
Credit: 1,064,445
RAC: 0
Message 24742 - Posted: 30 Aug 2012, 21:00:01 UTC

Well, still giving the same errors, suspending LHC for now...
ID: 24742 · Report as offensive     Reply Quote
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 12 Jul 11
Posts: 76
Credit: 1,064,445
RAC: 0
Message 24887 - Posted: 9 Oct 2012, 19:08:55 UTC
Last modified: 9 Oct 2012, 19:12:16 UTC

EDIT : actually it's the other way, it started bad with the 25 errors on the 07/10, but the WU crunched today seem to be OK...


1 month later, I decided to give it another try.

It started well, 8 valid tasks crunched yesterday, but then today with the same application version, 25 errors...

Stderr output

<core_client_version>7.0.31</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
SIGBUS: bus error

Crashed executable name: sixtrack_apple_gen
Machine type Intel 80486 (32-bit executable)
System version: Macintosh OS 10.7.5 build 11G63
Sun Oct 7 23:27:40 2012

0 sixtrack_apple_gen 0x0020df9e PrintBacktrace (in sixtrack_apple_gen) + 1022

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xffffffe1 ebx: 0x00000003 ecx: 0xbfffa59c edx: 0x96ff5c22
edi: 0xbfffa5f8 esi: 0x00000003 ebp: 0xbfffa5c8 esp: 0xbfffa59c
ss: 0x00000023 efl: 0x00000206 eip: 0x96ff5c22 cs: 0x0000000b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f

Binary Images Description:
0x1000 - 0x31ffff /Library/Application Support/BOINC Data/slots/4/../../projects/lhcathomeclassic.cern.ch_sixtrack/sixtrack_apple_gen
0x90652000 - 0x90668fff /usr/lib/system/libxpc.dylib
0x913e1000 - 0x913e6fff /usr/lib/system/libmacho.dylib
0x917a1000 - 0x917a9fff /usr/lib/system/libunwind.dylib
0x91a4b000 - 0x91a4dfff /usr/lib/system/libdyld.dylib
0x91aa2000 - 0x91ad1fff /usr/lib/system/libsystem_info.dylib
0x9202c000 - 0x92030fff /usr/lib/system/libcache.dylib
0x92031000 - 0x92038fff /usr/lib/system/libsystem_notify.dylib
0x920a6000 - 0x920a7fff /usr/lib/system/libunc.dylib
0x94424000 - 0x94425fff /usr/lib/system/libremovefile.dylib
0x94bfe000 - 0x94bfefff /usr/lib/system/libkeymgr.dylib
0x95aaa000 - 0x95aabfff /usr/lib/system/libsystem_blocks.dylib
0x96fdf000 - 0x96ffdfff /usr/lib/system/libsystem_kernel.dylib
0x97547000 - 0x97555fff /usr/lib/system/libdispatch.dylib
0x97556000 - 0x9755efff /usr/lib/system/liblaunch.dylib
0x984b7000 - 0x984fafff /usr/lib/system/libcommonCrypto.dylib
0x98537000 - 0x9853efff /usr/lib/system/libsystem_dnssd.dylib
0x99c03000 - 0x99c03fff /usr/lib/system/libdnsinfo.dylib
0x99c1d000 - 0x99c20fff /usr/lib/system/libmathCommon.A.dylib
0x9a10b000 - 0x9a1d6fff /usr/lib/system/libsystem_c.dylib
0x9b9a1000 - 0x9b9a4fff /usr/lib/system/libcompiler_rt.dylib
0x9b9e6000 - 0x9b9e7fff /usr/lib/system/libsystem_sandbox.dylib
0x9bb10000 - 0x9bb18fff /usr/lib/system/libcopyfile.dylib
0x9bb1d000 - 0x9bb4bfff /usr/lib/libSystem.B.dylib
0x9bf62000 - 0x9bf63fff /usr/lib/system/libquarantine.dylib
0x9ce26000 - 0x9ce2afff /usr/lib/system/libsystem_network.dylib


Exiting...

</stderr_txt>
]]>


Uncool.
ID: 24887 · Report as offensive     Reply Quote
Eric Mcintosh
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 12 Jul 11
Posts: 857
Credit: 1,619,050
RAC: 0
Message 24890 - Posted: 14 Oct 2012, 13:34:10 UTC - in response to Message 24887.  

Very uncool indeed! maybe your CPU is too hot! :-)
Seriously I am trying to get feedback from other MacOS
users and from our logs. I am really very very surprised
that you can run some WUs OK and then have a failure.
I really suspect your machine. Could you please let me
know your CPU ID so we check. Thanks. Eric.
ID: 24890 · Report as offensive     Reply Quote
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 12 Jul 11
Posts: 76
Credit: 1,064,445
RAC: 0
Message 24900 - Posted: 26 Oct 2012, 5:33:34 UTC - in response to Message 24890.  
Last modified: 26 Oct 2012, 5:34:11 UTC

Hi

I hadn't seen your answer (bloody "no notificiation boinc forums"), it turns out I came back here cause I see I have again LHC in my boinc, I had removed the "no more work" doing other things with my list of projects (I have many) and let it like that, the good news is they seem to be running (after 5 hours for one of them) and didn't brake... They are here

The point is I don't have major issue with all my other projects (I even do Test4Theory), so I'm not convinced "my mac would have a problem"...
ID: 24900 · Report as offensive     Reply Quote
Eric Mcintosh
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 12 Jul 11
Posts: 857
Credit: 1,619,050
RAC: 0
Message 24901 - Posted: 26 Oct 2012, 6:38:51 UTC - in response to Message 24900.  

Good, thanks and keep me posted. You can always mail me direct
at eric.mcintosh@cern.ch. I am not very comfortable with Message
boards either! Eric.
ID: 24901 · Report as offensive     Reply Quote
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 12 Jul 11
Posts: 76
Credit: 1,064,445
RAC: 0
Message 24926 - Posted: 4 Nov 2012, 16:18:33 UTC - in response to Message 24901.  

Got another loads of WU, worked fine. Good :)
ID: 24926 · Report as offensive     Reply Quote
1 · 2 · Next

Message boards : Number crunching : Mac OS X Errors


©2022 CERN