Message boards :
Number crunching :
post milkyway_i686-pc-linux-gnu problems here
Message board moderation
Author | Message |
---|---|
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
Please post any problems with the 32 bit linux app here. |
Send message Joined: 19 Oct 08 Posts: 19 Credit: 1,463,876 RAC: 0 |
any idea of when it will actually be available? |
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
any idea of when it will actually be available? We need to get a 32 bit linux machine to compile it on... I thought Dave had one but it's not looking like it. If anyone wants to compile the latest code for it and send us the binary we can make it available that way as well. (update) I'm going to see if our linux system will let us compile 32 bit binaries, if so we can probably make it available today. |
Send message Joined: 19 Oct 08 Posts: 19 Credit: 1,463,876 RAC: 0 |
still no news? |
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
still no news? Not yet, neither of us have access to a 32 bit linux machine. |
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
still no news? Not yet, neither of us have access to a 32 bit linux machine. |
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
Update to this -- We got some pre-compiled 32 bit linux boinc libraries, so we can just link our app to those and hopefully things should be peachy-keen. Hopefully have a 32bit linux app out tonight or tomorrow. |
Send message Joined: 19 Oct 08 Posts: 19 Credit: 1,463,876 RAC: 0 |
i'm testing it right now -- so far, no problem. |
Send message Joined: 13 Feb 08 Posts: 1124 Credit: 46,740 RAC: 0 |
Got some nm_test25s and the 04 linux 32bit client. Still have the checkpointing problem, client crashes on a restart. [edit]Otherwise its finished a work unit correctly.[/edit] |
Send message Joined: 27 Aug 07 Posts: 647 Credit: 27,592,547 RAC: 0 |
Errm, wrong thread... *grin* Lovely greetings, Cori |
Send message Joined: 22 Feb 08 Posts: 260 Credit: 57,387,048 RAC: 0 |
Just did my first new WU: nm_test11_75_1227466845_2 (app 0.4) No problems - valid. Although the stderr out doesn't look 'clean': <core_client_version>6.2.12</core_client_version> <![CDATA[ <stderr_txt> Unrecognized XML in parse_init_data_file: computation_deadline Skipping: 1227985432.136000 Skipping: /computation_deadline Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time Skipping: /mod_time Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct Skipping: 100.000000 Skipping: /max_ncpus_pct APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 </stderr_txt> ]]> Creditwise it's exactly the same as milksop's app on my Q9550. (2x crunch-time -->> 2x the credit) mic. |
Send message Joined: 19 Oct 08 Posts: 19 Credit: 1,463,876 RAC: 0 |
i just had some nm_test10 with following result: Outcome Client error Client state Downloading Exit status -186 (0xffffffffffffff46) <core_client_version>6.2.18</core_client_version> <![CDATA[ <message> WU download error: couldn't get input files: <file_xfer_error> <file_name>stars.txt</file_name> <error_code>-224</error_code> <error_message>file not found</error_message> </file_xfer_error> </message> ]]> nm_test25 were fine. edit: nm_test25 were fine but with same stdout as post above |
Send message Joined: 11 Nov 07 Posts: 41 Credit: 1,000,181 RAC: 0 |
Got about 70 WUs, really quick: 00:11 instead of 04:53. Seem to work fine but stderr out complains a bit: stderr out Edit: oops..3 failed:
Not with nm_test25 or nm_test26 though, they seem fine. |
Send message Joined: 2 Jan 08 Posts: 123 Credit: 69,522,293 RAC: 1,631 |
Ok Travis, I have downloaded your new stock app to see how it is going, mainly as you are going to cease the 1.22 Op app anyway and I could not get work. They run quite a bit longer than the Milksop 1.22 op app. (I have had to be very quick to get the results, even then I only got a couple then they were gone). The 'test' WU's run about twice as long as the Milksop app but the 'stripe' WU's run heaps longer and vary between different stripe versions (79; 86 etc). Also the run time between Windows and Linux is still quite a bit different to each other on the same WU type. Windows is much faster, this was the case on the original stock app, Milksop's app and now your new app (v0.04). AMD Opteron 285 Linux FC6....'stripe79_1' WU...3,652 sec, Op App..389 sec AMD Opteron 285 Windows XP...'stripe79_1' WU...2,837 sec, Op App..351 sec As you can see run times on near identical machines is slower with Linux. (I have noticed some variation in the run times of 'stripe79' WU's, so maybe it is not as consistent as the previous work units). The 'test' apps on my Linux machine run for about 910 sec on 'test26' and 920 sec on 'test27'. On my Intel P4 2.53 the 'test25' work units run for about 1,269 sec, not much slower than my Opteron, which user to be twice as quick at doing a WU. Maybe I need to learn how to compile source code on Linux ??? With the longer Work Units I have not had too much problem with the 8 WU limit per CPU. Thanks Travis and Dave for all your hard work on this. EDIT:-- Have just read another post (post is '20 work unit limit') about the difference in 'stripe79' and 'stripe79_1' and why they are not the same length. |
Send message Joined: 9 Sep 07 Posts: 22 Credit: 320,035 RAC: 0 |
Just had one error out after 35 minutes. Task ID 56879889 Name nm_stripe79_1_13099_1228123065_0 Workunit 57100851 Created 1 Dec 2008 9:17:50 UTC Sent 1 Dec 2008 9:28:30 UTC Received 1 Dec 2008 11:21:52 UTC Server state Over Outcome Client error Client state Compute error Exit status 255 (0xff) Computer ID 36872 Report deadline 4 Dec 2008 9:28:30 UTC CPU time 2143.636117 stderr out <core_client_version>6.4.1</core_client_version> <![CDATA[ <message> process exited with code 255 (0xff, -1) </message> <stderr_txt> Unrecognized XML in parse_init_data_file: computation_deadline Skipping: 1228379223.600000 Skipping: /computation_deadline Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time Skipping: /mod_time Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct Skipping: 100.000000 Skipping: /max_ncpus_pct APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 APP: error writing checkpoint (closing checkpoint file) 0 Unrecognized XML in parse_init_data_file: computation_deadline Skipping: 1228379223.600000 Skipping: /computation_deadline Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time Skipping: /mod_time Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct Skipping: 100.000000 Skipping: /max_ncpus_pct Error reading into stream_integrals </stderr_txt> ]]> Validate state Invalid Claimed credit 5.05409120118583 Granted credit 0 application version 0.04 This was after detaching/reattaching to get the stock app. Kathryn :o) The BOINC FAQ Service The Unofficial BOINC Wiki The Trac System More BOINC information than you can shake a stick of RAM at. |
Send message Joined: 22 Mar 08 Posts: 90 Credit: 501,728 RAC: 0 |
|
Send message Joined: 9 Jul 08 Posts: 7 Credit: 11,070,991 RAC: 0 |
And what with linux machines with gcc libs older than 4.2.0? cheers mindc |
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
Just had one error out after 35 minutes. There's an issue with checkpointing v0.4 and lower, this should be fixed with version 0.6 |
Send message Joined: 6 Sep 07 Posts: 66 Credit: 636,861 RAC: 0 |
AMD Opteron 285 Linux FC6....'stripe79_1' WU...3,652 sec, Op App..389 sec It might be because Linux manages power differently from Windows, running BOINC applications at a slow CPU frequency in order to save energy. See more details here. HTH |
Send message Joined: 6 Sep 07 Posts: 66 Credit: 636,861 RAC: 0 |
And what with linux machines with gcc libs older than 4.2.0? Is it too much to ask that the application be linked with the GCC option -static-libgcc in order to avoid this issue? TIA |
©2024 Astroinformatics Group