Posts by Rebirther

11)

Message boards : Number crunching : only errors on linux 64bit

( Message 4300 )
Posted 3269 days ago by Profile Rebirther
I can see that, =( then isn't a corrupted file.

This is what I found in the BOINC wiki http://www.boinc-wiki.info/SIGILL:_illegal_instruction_Exiting.. It's an OS problem, we are not including processor-specific optimizations in the application.

Let me see if I can find how to solve that problem

Just 2 quick questions:

  • you are not having the problem for other projects right?
  • did you compile your own client? or did you get the binary?



In my list there is only one WU got successfully finished, on windows I have no probs.
Other user like saenger can finishing WUs successfully without errors ^^ Iam surprised.

Iam running official version, dl from berkeley, I have no problems so far with other projects.
12)

Message boards : Number crunching : only errors on linux 64bit

( Message 4298 )
Posted 3269 days ago by Profile Rebirther
It seems to be a corrupted file. I think that it will be fixed once you detach-reattach to the project. So far this error is present only in host 7310.

Please let me know if the error persists after reattaching and I'll try to find another solution.

Thanks again


Tried my other host with attach to project, after 9min computation error. Waiting for other one... Both running on VMware server 1.0.5 on win xp 32bit
13)

Message boards : Number crunching : only errors on linux 64bit

( Message 4295 )
Posted 3269 days ago by Profile Rebirther
Could be BOINC 6.2.15, try now 6.2.14

Edit:
Same with 6.2.14, no chance without a computation error ^^

All other projects running fine, could be an app issue...
14)

Message boards : Number crunching : only errors on linux 64bit

( Message 4293 )
Posted 3270 days ago by Profile Rebirther
http://docking.cis.udel.edu/result.php?resultid=54561

Every WU crashed after some time.
15)

Message boards : Wish list : Frequent Cruncher Credits

( Message 3202 )
Posted 3754 days ago by Profile Rebirther
Disagree, not a good idea, only fixed credits and thats all ;)
16)

Message boards : Web site : Newsletter broken

( Message 3161 )
Posted 3756 days ago by Profile Rebirther
I checked again and now it works :o
17)

Message boards : Web site : Newsletter broken

( Message 3153 )
Posted 3757 days ago by Profile Rebirther
The second newsletter http://docking.utep.edu/newsletters.php is damaged.
18)

Message boards : Number crunching : Issues with Charmm 5.07

( Message 3140 )
Posted 3757 days ago by Profile Rebirther
Charmm 5.06/5.07=5h/2:48h
great improvement :)
19)

Message boards : Number crunching : Excessive disk activity

( Message 3135 )
Posted 3757 days ago by Profile Rebirther
Where are you seeing this. I just looked at the _0 through _3 , std???dae.txt and std???gui.txt files for a 90% complete WU (the real files not the windows soft links) and I'm not seeing any excessive output like that in them. This is on Vista.

Is there a chance that there's some kind of debug override flag set and that it's also causing the checkpoints as well as reporting them? I've never worked with any of the override flags. OTOH, I'm a programmer and debug code is well known for changing the behavior of a program, although usually it makes the problem you're trying to find go away until you remove the debug code and then the problem comes back :-)

-- David


The debug code is only for testing, without it its the same problem. You can use the cc_config.xml with <task_debug>1</task_debug> to debug on/off while boinc is running.
20)

Message boards : Number crunching : Excessive disk activity

( Message 3131 )
Posted 3757 days ago by Profile Rebirther
Charmm 5.07 for windows:

27/04/2007 11:11:21|Docking@Home|[task_debug] result 1tng_mod0011_117_389293_1 checkpointed
27/04/2007 11:11:23|Docking@Home|[task_debug] result 1tng_mod0011_117_389293_1 checkpointed
27/04/2007 11:11:24|Docking@Home|[task_debug] result 1tng_mod0011_117_389293_1 checkpointed
27/04/2007 11:11:26|Docking@Home|[task_debug] result 1tng_mod0011_117_389293_1 checkpointed
27/04/2007 11:11:29|Docking@Home|[task_debug] result 1tng_mod0011_117_389293_1 checkpointed
27/04/2007 11:11:31|Docking@Home|[task_debug] result 1tng_mod0011_117_389293_1 checkpointed
27/04/2007 11:11:32|Docking@Home|[task_debug] result 1tng_mod0011_117_389293_1 checkpointed
27/04/2007 11:11:34|Docking@Home|[task_debug] result 1tng_mod0011_117_389293_1 checkpointed
27/04/2007 11:11:36|Docking@Home|[task_debug] result 1tng_mod0011_117_389293_1 checkpointed
27/04/2007 11:11:37|Docking@Home|[task_debug] result 1tng_mod0011_117_389293_1 checkpointed
27/04/2007 11:11:40|Docking@Home|[task_debug] result 1tng_mod0011_117_389293_1 checkpointed
27/04/2007 11:11:42|Docking@Home|[task_debug] result 1tng_mod0011_117_389293_1 checkpointed

I see no changes. If you can extend the percentage status every 1% (writing) it could be better and have no checkpoints every 2sec.


Next 10 posts