I had a strange behavior last night with the 6.6.2. SETI was set to No New Work and the Boinc Manager and the work cache to 1 day. Even so I set SETI to NNW the Boinc Manager was loading over 160 Seti extended WUs and 20 Astropuls WUs, thats much ure then the PC can do in one day. As a result he SETU WUs are all running in high prio mode. While I also have other projects running, I had to cancel the most of them.

I had the same experience. When installing 6.6.2 I (always) set 0.25 work cache but got 452 extended and 2 AP's. The last one must be finished at feb 26 so I think it will do.
On another PC same thing happened and I got 360 AP's(!) but 6.6.2 crached and all AP's disappeared when I installed 6.6.0 instead...
Believe something needs to be fixed in 6.6.2
Just read that 6.6.3 is available...

---

//Peter

I just tried 6.6.2 and it worked all fine and dandy except when I went to the tasks tab.... Boinc manager either locks up or crashes to the desktop...

I guess it has a problem with to many tasks... oh well

I had exactly the same problem with 3 of my quads. Boinc mgr not answering and then crached when hitting the task tab. Trying to install 6.6.0 and 6.4.5 many times back and forth, and trying all Raistmers mods, and suddenly (don't ask why) 2 of the quads was stable with 6.6.2 but on the third I have to run 6.4.5.
So it's not a matter of too many tasks.

Hope it's fixed in 6.6.3 just out...

---

//Peter

Have just installed v.6.6.3 and I could install both 32b and 64b version without any problems like I had with 6.6.2 on 4 of my Quads and 1 i7 and they are running very good.
2 of them also started the idle AP's and I did not get any huge amount of WU's either...
so now I'm happy again :)

Still only running 1 graphics card but I was told in another thread by Raistmer:

V8x combos: Can do SETI MB on CPU and GPU but can use only one GPU card.
V7x combos: Can do SETI MB on GPU only (but can use CPU for SETI AP ) but can use all GPUs in system.

For all dual/many GPU owners I recommend to use V7x packages, not V8x ones. That way you will get best performance from your hosts.

but I tried both version of V7 but they crashed Boinc Manager so I had to reinstall V8 to get it up and run again with only 1 graphics card...

---

//Peter

A small note for the "boincmgr" application...

Even though the boincmgr for 6.6.2 crashes/freezes on the tasks window, you can still use a previous version of boincmgr to see what is happening. For example, copying over the boincmgr from 6.4.5 works fine, even for displaying thousands of tasks.

Meanwhile, as noted in other threads, Boinc 6.6.2 has requested LOTs of work from all projects and so everything is running in EDF now. There's also reports that the "No New Work" setting isn't effective in that more work still gets requested regardless!

Here's hoping for some rapid debug!...

Happy crunchin',
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

Well, there is 6.6.3 and 6.6.4 are available and they have new an unique problems ... 6.6.3 has a major bug in the calculation of LTD so eventually you will not fetch work properly (though it takes a couple days to get there sometimes) and 6.6.4 does not fetch from some projects at all ... GPU Grid for one ...

Of the 6.x.y versions out there the best balance for me has been 6.5.0 which does have some queuing problems and does not distinguish the difference between CPU and CUDA tasks ...

Meanwhile, as noted in other threads, Boinc 6.6.2 has requested LOTs of work from all projects and so everything is running in EDF now.

The work fetch seems to have grabbed about x2 the work that can actually be done in time. To avoid timeouts, I've psuedo-selectively aborted about half the queued work. That's thrown about 1000 WUs back into the pot...

Grab em' while you can!

Happy crunchin',
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)