Message boards :
News :
Nobdy Release 1.02
Message board moderation
Author | Message |
---|---|
Send message Joined: 23 Sep 12 Posts: 159 Credit: 16,977,106 RAC: 0 |
We have updated the binaries for Nbody. Currently the Windows 64 bit and Apple Macintosh 64 bit versions are testing successfully. We are releasing a test run to test the Windows and Apple variants on the boinc system. We are monitoring this as. Please post any error details. And we will monitor the data as it comes back. Thank you. |
Send message Joined: 14 Dec 09 Posts: 161 Credit: 589,318,064 RAC: 0 |
Hello, Imminent errors. Exit status: -1073741515 (0xffffffffc0000135) Unknown error number. http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=345135096 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=345135092 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=345134892 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=345134537 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=345134536 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=345134303 |
Send message Joined: 23 Sep 12 Posts: 159 Credit: 16,977,106 RAC: 0 |
Thank you. We are leaving the run up for a short time interval to gather some statistics on the systems seeing errors versus the systems that are not. We will post details in here as we proceed and work on resolving all these issues. |
Send message Joined: 14 Nov 12 Posts: 1 Credit: 2,078,076 RAC: 0 |
I'm new to this project having problems with this crashing all over the place. Faulting application milkyway_nbody_1.02_windows_x86_64__mt.exe, version 0.0.0.0, time stamp 0x50a94316, faulting module libgomp_64-1.dll, version 6.0.6002.18541, time stamp 0x4ec3e855, exception code 0xc0000135, fault offset 0x00000000000b6fc8, process id 0x4ffc, application start time 0x01cdc6a15be48670. When I try and run milkyway_nbody_1.02_windows_x86_64__mt.exe manually it says libgomp_64-1.dll was not found and I can't find it anywhere on my computer. |
Send message Joined: 4 Sep 12 Posts: 219 Credit: 456,474 RAC: 0 |
The 0xc0000135 errors will probably be missing libgomp_64-1.dll and pthreadGC2_64.dll files - you're still not specifying them in <app_version> With the files downloaded manually and in place, I'm getting exit code -1073740940 (0xc0000374) like last time: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=345208264 |
Send message Joined: 20 Sep 09 Posts: 1 Credit: 5,989,675 RAC: 0 |
Thank you I have pulled down the jobs. The Macintosh Release and the 0.94 64bit Linux release were returning valid results. The bulk of our errors are coming the windows clients though not exclusively. Thanks for the dll information. I will check the linking. I believe this should have been statically compiled into the executable and may be part of the problem we are seeing. Though I need to look in more deeply. |
Send message Joined: 23 Sep 12 Posts: 159 Credit: 16,977,106 RAC: 0 |
As you may have noted that was posted as Annette Thompson and not Jeffery M. Thompson. My account as a user was set up on my wife's machine when Milkway@home first came out. I noticed she had received some nbody work and wanted to look at the work unit ids quickly. So oops I posted as my wife sorry for that. But what she said does apply. |
Send message Joined: 4 Sep 12 Posts: 219 Credit: 456,474 RAC: 0 |
Unfortunately, it requires at least one of the files as an external DLL - this is the same as I was seeing with v0.84 |
Send message Joined: 30 Jan 09 Posts: 21 Credit: 13,256,888 RAC: 0 |
Four tasks successfully completed (Linux & NVidia), but can't validate... |
Send message Joined: 10 Dec 10 Posts: 1 Credit: 153,063 RAC: 0 |
|
Send message Joined: 8 Feb 08 Posts: 261 Credit: 104,050,322 RAC: 0 |
The app_info for nbody v0.84 64bit looked something like <app_info> <app><!-- CPU app for N-Body 0.84 mt 64bit --> <name>milkyway_nbody</name> <user_friendly_name>MilkyWay@Home nbody</user_friendly_name> </app> <file_info> <name>milkyway_nbody_0.84_windows_x86_64__mt.exe</name> <executable/> </file_info> <file_info> <name>libgomp_64-1_nbody_0.84.dll</name> <executable/> </file_info> <file_info> <name>pthreadGC2_64_nbody_0.84.dll</name> <executable/> </file_info> <app_version> <app_name>milkyway_nbody</app_name> <version_num>84</version_num> <plan_class>mt</plan_class> <avg_ncpus>4</avg_ncpus> <max_ncpus>4</max_ncpus> <cmdline>--nthreads=4</cmdline> <file_ref> <file_name>milkyway_nbody_0.84_windows_x86_64__mt.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libgomp_64-1_nbody_0.84.dll</file_name> <open_name>libgomp_64-1.dll</open_name> <copy_file/> </file_ref> <file_ref> <file_name>pthreadGC2_64_nbody_0.84.dll</file_name> <open_name>pthreadGC2_64.dll</open_name> </file_ref> </app_info>
|
Send message Joined: 4 Sep 12 Posts: 219 Credit: 456,474 RAC: 0 |
If you're going to the bother of creating an app_info.xml, it's probably easier to download the DLLs under their 'real' names, rather than going for the versioned aliases and renaming them back again. http://milkyway.cs.rpi.edu/milkyway/download/libgomp_64-1.dll http://milkyway.cs.rpi.edu/milkyway/download/pthreadGC2_64.dll Then you can do away with the <open_name> and <copy_file/> lines entirely - you forgot the copy on the second file, anyway. While I've got the download directory open, we may as well link http://milkyway.cs.rpi.edu/milkyway/download/milkyway_nbody_1.02_windows_x86_64__mt.exe But I got nothing but errors with this version too - always 0xc0000374 The best explanation I've found for that one is at codeguru - there's a lot of off-topic waffling in the thread, but if you persevere to page 2 (#22), you'll see that the very first reply contains the correct diagnosis. The symptoms here match that description - the application crashes at the end, after reaching 100% (sometimes several seconds after reaching 100%), which is when you would expect memory to be freed and heap corruption (if any) discovered. |
Send message Joined: 8 Feb 08 Posts: 261 Credit: 104,050,322 RAC: 0 |
If you're going to the bother of creating an app_info.xml, it's probably easier to download the DLLs under their 'real' names, rather than going for the versioned aliases and renaming them back again. Good catch on the missing <copy_file/> line. Did not run nbody for a long time, so it was more like quick putting some fragments together. :) Could not test w/o nbody WUs. Point is that you need to get the versioned dlls from the download directory when downloading manually, if you rename them locally is your choice. Those without version number are very old (used for nbody v0.40 or v0.60). AFAIR Matt moved to versioning them at that time and renaming them while downloading to the users, so he could keep the versions online without conflicts. That's why I choosed to keep the numbers locally too and used open/copy for runtime. Less confusion for me to keep the proper versions together. I did read the explanation on codeguru. It goes basically into the same direction I was thinking; maybe my english wasn't the best to make it clear. You are building (and testing) an exe with a new set of external dlls and trying to run it than with far older dlls. This can lead to a whole set of errors because of critical changes between those dll versions; heap corruption and memory out of bound would be far up on that list. That's why I am saying: First make sure to use the same dynamically linked dlls the exe was build and internally tested with, than see what errors are still left. See (Message 56239) that the statically linked exes (MAC and Linux) are returning mostly valid results while the bulk of errors are coming from windows clients with the dynamically linked dlls. Only my 2¢ and I hope they find the root of the problem soon. |
Send message Joined: 4 Sep 12 Posts: 219 Credit: 456,474 RAC: 0 |
OK, my turn to say 'good catch'. When I joined the project (primarily out of interest to see how well the development BOINC v7.0.38 coped with scheduling multi_threaded apps), I found Matt's post at message 53919, and from it assumed - wrongly, as it turns out - that the only reason for versioning the libgomp and pthread DLLs was to comply with BOINC's stratagem for managing multifile applications. As you point out (and FC confirms), there are in fact binary differences too. The DLLs haven't been recompiled (or at least placed in the download folder) with either the 0.94 or 1.02 releases, so the newest versions available for download are still http://milkyway.cs.rpi.edu/milkyway/download/libgomp_64-1_nbody_0.84.dll http://milkyway.cs.rpi.edu/milkyway/download/ pthreadGC2_64_nbody_0.84.dll and we'll have to use either file renaming or the <copy_file/> construct until Jeffery comes back with an explanation of what the app really needs. Talking of MT, here's an example of an app_info that I was using at AQUA until they went off the air about 18 months ago - ignore the file names and parameters, but it shows the sort of extra tags that will be needed when NBody is ready to go fully MT. <app_version> At the least, some analogue of the lines I've picked out in red (which will be familiar to GPU users here, I'm sure) will be needed. |
Send message Joined: 10 Mar 11 Posts: 9 Credit: 16,497,101 RAC: 0 |
Greetings Crunchers! My machine was cranking out N-Body's quite well - and at one point I was doing them exclusively when there was lots of work to do and I felt my 8 core machine should practice working as a team. Recently though I have noticed 5 Errors using MilkyWay@Home N-Body Simulation so far since the project started offering them again to my system. Looking at the task ID numbers I notice my box isn't the only one choking on these bits and bytes. Cheers to all! Life's short; make fun of it! |
Send message Joined: 4 Sep 12 Posts: 219 Credit: 456,474 RAC: 0 |
|
Send message Joined: 16 Aug 09 Posts: 12 Credit: 143,222,763 RAC: 0 |
Hi everyone, I have been running MilkyWay for a year or two now with no real problems but the last two days my computer turns itself off after running the program for about five minutes, suspend the activity and no problems.Any one else having problems or know what's happening. Nick |
Send message Joined: 8 Feb 08 Posts: 261 Credit: 104,050,322 RAC: 0 |
Hi everyone, I have been running MilkyWay for a year or two now with no real problems but the last two days my computer turns itself off after running the program for about five minutes, suspend the activity and no problems.Any one else having problems or know what's happening. Nick Sounds like a heat problem. Australian summer ... Try a tool like HWMonitor to find out about the temps in your box. |
Send message Joined: 25 Jan 11 Posts: 12 Credit: 16,960,651 RAC: 0 |
On Windows 8
On Windows 7
On Linux OpenSuse [/u] |
Send message Joined: 18 Sep 07 Posts: 1 Credit: 36,532,853 RAC: 0 |
Bis zum 24.11.2012 11:56:49 UTC war alles in Ordnung: http://milkyway.cs.rpi.edu/milkyway/results.php?userid=339&offset=0&show_names=0&state=3&appid= Danach ging nichts mehr: http://milkyway.cs.rpi.edu/milkyway/results.php?userid=339&offset=0&show_names=0&state=5&appid= Was soll das???????????????????????? |
©2024 Astroinformatics Group