1)
Message boards :
News :
maximum time limit elapsed bug
(Message 50039)
Posted 10 Jul 2011 by davebodger Post: You can get them from here, it does load slow though. Thanks very much Arkayn, exactly what I needed. All the best. Dave. |
2)
Message boards :
News :
maximum time limit elapsed bug
(Message 50036)
Posted 10 Jul 2011 by davebodger Post: Now, although I have .82 and .88 workunits processing OK by using an app_info.xml file, I am receiving messages from Milkway in the form :- 09/07/2011 22:08:33 | Milkyway@home | Message from server: Your app_info.xml file doesn't have a usable version of MilkyWay@Home N-Body Simulation. So I tried to add it by creating this app_info file :- <app_info> <app> <name>milkyway</name> </app> <file_info> <name>milkyway_nbody_0.66_windows_intelx86__mt.exe</name> <executable /> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>66</version_num> <cmdline></cmdline> <file_ref> <file_name>milkyway_nbody_0.66_windows_intelx86__mt.exe</file_name> <main_program/> </file_ref> </app_version> <file_info> <name>milkyway_separation_0.82_windows_intelx86__ati14.exe</name> <executable/> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>82</version_num> <flops>1.0e11</flops> <avg_ncpus>0.05</avg_ncpus> <max_ncpus>1</max_ncpus> <plan_class>ati14ati</plan_class> <coproc> <type>ATI</type> <count>1</count> </coproc> <cmdline></cmdline> <file_ref> <file_name>milkyway_separation_0.82_windows_intelx86__ati14.exe</file_name> <main_program/> </file_ref> </app_version> <file_info> <name>milkyway_separation_0.88_windows_intelx86.exe</name> <executable /> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>88</version_num> <cmdline></cmdline> <file_ref> <file_name>milkyway_separation_0.88_windows_intelx86.exe</file_name> <main_program/> </file_ref> </app_version> </app_info> But I realised that the .66 exe file is wrong because I copied it from my other machine which is 32 bit windows, not 64 bit. Can anyone tell me where I can get the 64 bit exe and dll files from so I can get this working until someone gets enough time to fix the MTLE bug with the .82 ? TIA. Dave. |
3)
Message boards :
News :
maximum time limit elapsed bug
(Message 49994)
Posted 7 Jul 2011 by davebodger Post: I think you chose the wrong download for your win xp machine u have to use this: Thanks franz, I have merged the app_info files together and now have both .82 and .88 running OK at the same time. No more MTLE problems. :-) Now if only I could get the files I need to run the ps_nbody stuff then I would be home and dry. Presumably when someone (Travis?) fixes the base code then I can delete the app_info file and everything will revert back to normal ? Regards. Dave. P.S. here's what I put in the app_info.xml :- <app_info> <app> <name>milkyway</name> </app> <file_info> <name>milkyway_separation_0.82_windows_x86_64__ati14.exe</name> <executable/> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>82</version_num> <flops>1.0e11</flops> <avg_ncpus>0.05</avg_ncpus> <max_ncpus>1</max_ncpus> <plan_class>ati14ati</plan_class> <coproc> <type>ATI</type> <count>1</count> </coproc> <cmdline></cmdline> <file_ref> <file_name>milkyway_separation_0.82_windows_x86_64__ati14.exe</file_name> <main_program/> </file_ref> </app_version> <file_info> <name>milkyway_separation_0.88_windows_x86_64.exe</name> <executable /> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>88</version_num> <cmdline></cmdline> <file_ref> <file_name>milkyway_separation_0.88_windows_x86_64.exe</file_name> <main_program/> </file_ref> </app_version> </app_info> |
4)
Message boards :
News :
maximum time limit elapsed bug
(Message 49958)
Posted 6 Jul 2011 by davebodger Post:
I tried this and followed the instructions but got lots of errors when restarting BOINC - should I have done anything else? I saw little in the xml file - i.e. lots of labels with most empty of content - is that correct? I'm afraid I have no experience in hacking this stuff so am not sure what I am looking at. 06/07/2011 23:19:32 | Milkyway@home | Found app_info.xml; using anonymous platform 06/07/2011 23:19:32 | Milkyway@home | [error] State file error: missing application milkyway_nbody 06/07/2011 23:19:32 | Milkyway@home | [error] Can't handle workunit in state file 06/07/2011 23:19:32 | Milkyway@home | [error] State file error: missing application milkyway_nbody 06/07/2011 23:19:32 | Milkyway@home | [error] Can't handle workunit in state file 06/07/2011 23:19:32 | Milkyway@home | [error] State file error: missing task ps_nbody_test3_243318 06/07/2011 23:19:32 | Milkyway@home | [error] Can't link task ps_nbody_test3_243318_0 in state file 06/07/2011 23:19:32 | Milkyway@home | [error] State file error: missing task ps_nbody_test3_243317 06/07/2011 23:19:32 | Milkyway@home | [error] Can't link task ps_nbody_test3_243317_0 in state file 06/07/2011 23:19:32 | Milkyway@home | [error] No application found for task: windows_x86_64 82 ati14; discarding 06/07/2011 23:19:32 | Milkyway@home | [error] No application found for task: windows_x86_64 82 ati14; discarding 06/07/2011 23:19:32 | Milkyway@home | [error] No application found for task: windows_x86_64 82 ati14; discarding 06/07/2011 23:19:32 | Milkyway@home | [error] No application found for task: windows_x86_64 82 ati14; discarding 06/07/2011 23:19:32 | Milkyway@home | [error] No application found for task: windows_x86_64 82 ati14; discarding 06/07/2011 23:19:32 | Milkyway@home | [error] No application found for task: windows_x86_64 82 ati14; discarding 06/07/2011 23:19:32 | Milkyway@home | [error] No application found for task: windows_x86_64 82 ati14; discarding 06/07/2011 23:19:32 | Milkyway@home | [error] No application found for task: windows_x86_64 82 ati14; discarding 06/07/2011 23:19:32 | Milkyway@home | [error] No application found for task: windows_x86_64 82 ati14; discarding 06/07/2011 23:19:32 | Milkyway@home | [error] No application found for task: windows_x86_64 82 ati14; discarding 06/07/2011 23:19:32 | Milkyway@home | [error] No application found for task: windows_x86_64 82 ati14; discarding 06/07/2011 23:19:32 | Milkyway@home | [error] No application found for task: windows_x86_64 82 ati14; discarding Now since I restarted I do not have any Milkyway tasks that want to use the GPU, so I suppose that is a kind of way to stop the Abort errors. :-) Regards. Dave. [/code] |
5)
Message boards :
News :
maximum time limit elapsed bug
(Message 49923)
Posted 5 Jul 2011 by davebodger Post: New insight - in BOINC if I select the Properties of a MilkyWay work unit it shows "Estimated app speed = 31110.33 GFLOPs/sec. This seems a little high to me (by a factor of around 100). PrimeGrid workunits report 322.12 GFLOPs/sec and Collatz workunits show 354.13 GFLOPs/sec. It looks to me like the MilkyWay app is mis-estimating the speed of the GPU. When is starts up, the BOINC event log shows my video card as capable of a peak of 1422 GFLOPs/sec. We know ATI cards seldom reach their peak throughput so ~300 GFLOPs/sec seems a resonable estimate of achievable throughput on my HD4890. Regards. Dave. |
6)
Message boards :
News :
maximum time limit elapsed bug
(Message 49900)
Posted 5 Jul 2011 by davebodger Post: I have this problem too - every unit seems to return this error, exactly as described in this thread. Sorry, forgot to say - I am running the latest Catalyst 11.6 drivers also. |
7)
Message boards :
News :
maximum time limit elapsed bug
(Message 49899)
Posted 5 Jul 2011 by davebodger Post: I have this problem too - every unit seems to return this error, exactly as described in this thread. To make it clear - it is the CPU that is overclocked 2.66 -> 3.43GHz. It is watercoooled (CPU and full chipset) so no overheating - in fact it runs cooler by 3 or 4 degrees running BOINC than it did running F@H. The GPU is an "overclocked" one but the "overclocking" was done by the manufacturer and I have not overclocked it further from it's standard settings (901MHz GPU/1000MHz RAM). It runs at 60C as standard with fan at 25% and ramps up to 81C under full 100% load with fan at 41%. I have already tried icreasing fan speed manually to 60% continuous, which drops temps by at least 20C at all loads, but this did not fix anything. These GPU chips are OK up to 90C+ so I am well within limits and the system is also running Rosetta and Climate Prediction OK (but they do not use the GPU). It also runs MilkyWay OK if I disable the GPU in BOINC. I don't know where to start debugging this as I am a new contributor and have not had time to look through all the config files to find if there are any settings I can change that might help. Of course if this is a feneral application problem then there is nothing I can do to fix it. :-( I did think of replacing the GPU card with a HD6950 that I have, but others here have already reported this problem on that card too, so there seems little point in trying that. Regards. Dave. |
8)
Message boards :
News :
maximum time limit elapsed bug
(Message 49887)
Posted 4 Jul 2011 by davebodger Post: I have this problem too - every unit seems to return this error, exactly as described in this thread. Sapphire HD4890 - WinXP 32bit SP3 - Q6600 @ 3.43GHz with 4Gb DDR2(800). I am a new contributor and only started last night, so presumed that this was normal operating, until I discovered this thread. I run an overclock so was concerned in case this was indicating an instability, however I have run this system at this overclock on Folding @ Home for several years without issue. I will stop using the GPU until this is fixed or at least beter understood so a work-around can be created, as I do not want to waste valuable WU processing time. Regards. Dave. |
©2024 Astroinformatics Group