| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home
Thread: illegal instruction error with application 715 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 16
|
|
| Author |
|
|
sgoll
Advanced Cruncher Joined: Oct 24, 2006 Post Count: 87 Status: Offline Project Badges: 
|
<core_client_version>6.10.58</core_client_version>
----------------------------------------<![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> INFO:[02:20:07] Start AutoGrid... SIGILL: illegal instruction Stack trace (7 frames): [0x80a4ebd] [0xb7740400] [0x808e512] [0x8093eb4] [0x80959a8] [0x811e558] [0x8048131] Exiting... </stderr_txt> ]]> Hmmm ... looks like the new app is compiled for i686 class systems, but this system is a i586 class system. The old 640 application was fine: <core_client_version>6.10.58</core_client_version> <![CDATA[ <stderr_txt> INFO:[08:33:29] Start AutoGrid... autogrid4: WARNING: I just prevented an attempt to take the arccosine of -1, a value less than -1. autogrid: autogrid4: Successful Completion. INFO:[08:51:33] End AutoGrid... Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 0) _maxGenSeenSoFar changed: 2500 _maxGenSeenSoFar changed: 2626 _maxGenSeenSoFar changed: 2758 _maxGenSeenSoFar changed: 2896 _maxGenSeenSoFar changed: 3041 _maxGenSeenSoFar changed: 3194 _maxGenSeenSoFar changed: 3354 _maxGenSeenSoFar changed: 3522 _maxGenSeenSoFar changed: 3699 _maxGenSeenSoFar changed: 3885 _maxGenSeenSoFar changed: 4080 _maxGenSeenSoFar changed: 4285 _maxGenSeenSoFar changed: 4500 _maxGenSeenSoFar changed: 4726 _maxGenSeenSoFar changed: 4963 _maxGenSeenSoFar changed: 5212 _maxGenSeenSoFar changed: 5473 _maxGenSeenSoFar changed: 5747 _maxGenSeenSoFar changed: 6035 _maxGenSeenSoFar changed: 6337 _maxGenSeenSoFar changed: 6654 _maxGenSeenSoFar changed: 6987 _maxGenSeenSoFar changed: 7337 _maxGenSeenSoFar changed: 7704 _maxGenSeenSoFar changed: 8090 _maxGenSeenSoFar changed: 8495 _maxGenSeenSoFar changed: 8920 _maxGenSeenSoFar changed: 9367 _maxGenSeenSoFar changed: 9836 _maxGenSeenSoFar changed: 10328 Updating Best Energy for WU: 0.00 Finished Docking number 0 Updating Best Energy for WU: -6.54 Finished Docking number 1 Finished Docking number 2 Finished Docking number 3 Finished Docking number 4 Finished Docking number 5 Finished Docking number 6 Finished Docking number 7 Updating Best Energy for WU: -7.71 Finished Docking number 8 Finished Docking number 9 Finished Docking number 10 Finished Docking number 11 Finished Docking number 12 Finished Docking number 13 Finished Docking number 14 Finished Docking number 15 Finished Docking number 16 Finished Docking number 17 Finished Docking number 18 Finished Docking number 19 Finished Docking number 20 Finished Docking number 21 Finished Docking number 22 Finished Docking number 23 Finished Docking number 24 Finished Docking number 25 Finished Docking number 26 Finished Docking number 27 Finished Docking number 28 Finished Docking number 29 Finished Docking number 30 Finished Docking number 31 Finished Docking number 32 Finished Docking number 33 Finished Docking number 34 Restoring grahics. bestEnergy: -8.079260 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 35) Finished Docking number 35 Finished Docking number 36 Finished Docking number 37 Finished Docking number 38 Finished Docking number 39 ________________________________________________________________________________ autodock4: Successful Completion on "World Community Grid device" ________________________________________________________________________________ INFO:[01:55:24] Start AutoGrid... autogrid: autogrid4: Successful Completion. INFO:[02:07:11] End AutoGrid... Beginning AutoDock... INFO: Setting num_generations: 27000 About to enter main loop...(dockings already completed: 40) Finished Docking number 0 ________________________________________________________________________________ autodock4: Successful Completion on "World Community Grid device" Look like time to leave the faah reseach with this system. Stephan  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
That would be a sad departure, sgoll. So far ran 1 on my 7 year old laptop that was upgraded from XP to Vista to W7-32 over it's life. This job had 20 dockings in it. The project mean-time went up from just under 4.9 hours on Friday to 5.5 hours on Sunday, so not quite sure what happened. It's not jiving with what was said in the announcement [faster, more accurate]: http://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,34768 One reason could be more dockings. Anyone knows who's been crunching this science from old app to new app?
|
||
|
|
herflick
Senior Cruncher Joined: Nov 11, 2009 Post Count: 176 Status: Offline Project Badges:
|
I also noticed that the work units seem to be taking about an hour longer on my 2 year old laptop. Went from about 4.5 hours to 5.5 hours per WU.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
So, can you answer the number of dockings question?
|
||
|
|
sgoll
Advanced Cruncher Joined: Oct 24, 2006 Post Count: 87 Status: Offline Project Badges:
|
> Finished Docking number 23 ... 3.54 / 3.65 h ... old application on a c2d
----------------------------------------> Finished Docking number 26 ... 5.10 / 5.24 h ... new application on the same system > Finished Docking number 33 (old app, different system) > Finished Docking number 31 (old app, another different system) (always the last line) I'm not sure but it looks like the number of dockings in a work unit is not a constant value. So it it hard to guess ... -- Stephan [Edit 1 times, last edit by sgoll at Feb 25, 2013 5:09:45 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thx. Will watch herflick's weekly update to see what the batch progression will be versus runtime... up / down / same. If more accurate requires more time, than so be it.
"This update will result in faster and more accurate docking results". In due time I'll run them on my Linux-64 system, just to gauge if the 64 bit version gives an downtick in processing time over Windows. The plan is to up my FAAH contrib. to 5 years at least this year. In beta the Windows-64 ran them in fact faster than Linux, but it could be apples/oranges, given that old and new batches [different build] were tested. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Not much data left on the results page but here is what I have on one Linux machine....
Laptop i686 1.6 GHz Centrino Client 7.0.29 Fedora-17 Repo Version, Intel Video: FAAH 6.40: 29 dockings, 7.39 cpu hrs FAAH 7.15: 23, 32, 20 dockings 14.12, 13.52, 13.50 cpu hrs respectfully These new app WU's do appear to be taking a lot longer. I mentioned in the Beta forum that I was having issues with the with the client counting and crediting CPU time that I thought was fixed after the last beta batch release. I was wrong but after much troubleshooting, I have determined that there is a definate incompatibiliy issue between the: nVidia drivers || Boinc Client 7.0.29 version || FAAH app 7.15. I just recently was able to get the two 64 bit machines up and running with this app properly by removing the nVidia drivers and going back to the Nouveau drivers. Unfortunately, that took my one GPU machine off the HCC gpu project. |
||
|
|
armstrdj
Former World Community Grid Tech Joined: Oct 21, 2004 Post Count: 695 Status: Offline Project Badges: 
|
Stephan,
What operating system and version are you runnint? Thanks, armstrdj |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Just in case, guessing "what version?" as in what client version, which the log says is 6.10.58, but it would not harm to know that on top of platform and version [XP/Vista/W98 [if there's anyone left using that]
----------------------------------------@armstrdj, an old request [not infringing on privacy]. Could future app build also please log the platform / OS release? It would help greatly in Q&A problem fixing, without immediate need of asking that in supplemental inquiries [At other projects volunteer helpers have the advantage of being able to drill into a log and the client particular, not given here at all...that would be a great feature to have on the dev ToDo list ;] [Edit 1 times, last edit by Former Member at Feb 26, 2013 7:01:23 PM] |
||
|
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1326 Status: Offline Project Badges:
|
J @armstrdj, an old request [not infringing on privacy]. Could future app build also please log the platform / OS release? It would help greatly in Q&A problem fixing, without immediate need of asking that in supplemental inquiries [At other projects volunteer helpers have the advantage of being able to drill into a log and the client particular, not given here at all...that would be a great feature to have on the dev ToDo list ;] I I love this idea it would be very helpful indeed, if we could also see what type of CPU the computer has it would help participants understand why some tasks run faster than others e.g. where those particular tasks run on a faster computer or was it simply down to the number of documents per unit and Mac case of FH @ home  |
||
|
|
|