Why I got line in bold? :

02/06/2010 03:28:49 Milkyway@home Computation for task de_test_s11_3_1618_1275429631_0 finished
02/06/2010 03:28:49 Milkyway@home Starting de_test_s222_3_63996_1275428121_1
02/06/2010 03:28:49 Milkyway@home [cpu_sched] Starting de_test_s222_3_63996_1275428121_1 (initial)
02/06/2010 03:28:49 Milkyway@home Starting task de_test_s222_3_63996_1275428121_1 using milkyway version 23
02/06/2010 03:29:16 Milkyway@home Sending scheduler request: To fetch work.
02/06/2010 03:29:16 Milkyway@home Reporting 1 completed tasks, requesting new tasks for GPU
02/06/2010 03:29:21 Milkyway@home Scheduler request completed: got 1 new tasks
02/06/2010 03:30:23 SETI@home update requested by user
02/06/2010 03:30:27 SETI@home Sending scheduler request: Requested by user.
02/06/2010 03:30:27 SETI@home Not reporting or requesting tasks
02/06/2010 03:30:37 SETI@home Scheduler request completed
02/06/2010 03:30:42 Milkyway@home Sending scheduler request: To fetch work.
02/06/2010 03:30:42 Milkyway@home Requesting new tasks for GPU
02/06/2010 03:30:47 Milkyway@home Scheduler request completed: got 0 new tasks
02/06/2010 03:30:47 Milkyway@home Message from server: No work sent
02/06/2010 03:30:47 Milkyway@home Message from server: (reached limit of 24 tasks in progress)
02/06/2010 03:30:51 SETI@home update requested by user
02/06/2010 03:30:52 SETI@home Sending scheduler request: Requested by user.
02/06/2010 03:30:52 SETI@home Requesting new tasks for GPU
02/06/2010 03:31:02 SETI@home Scheduler request completed: got 0 new tasks

SETI still had shortage of GPU work. So why BOINC chose not to ask for it ??

---

Probably overworked (excess cuda_long_term_debt). But unless you enable [work_fetch_debug] logging, or at least look at the properties page for the project, you'll never know.

Probably overworked (excess cuda_long_term_debt). But unless you enable [work_fetch_debug] logging, or at least look at the properties page for the project, you'll never know.

Asked for ATI GPU so not CUDA debt.
Also, look next few lines - SETI asks new work almost immediately after.
I suppose it's interference with MW ATI GPU work asking.
Maybe until BOINC was not sure it can't get next work from MW it suppressed SETI ATI work request?

Will check MW and SETI debts then (for info, MW has resource share of 5000 and SETI of 10000. Also, MW has ATI work much often than SETI. So how SETI could managed to have bigger debt ?? ]

---

<cpu_sched_debug>: problems involving the choice of applications to run.
<work_fetch_debug>: problems involving work fetch (which projects are asked for work, and how much).

Of course it isn't the first time we asked it and something tells me it won't be the last. So until that time, my answer to your question is that the gyroscopical theorism of the genotiplex is merely crossing the dyhandrum in alpha where it should be dissecting it in a 90 degree angle opposing the diorama.

---

<cpu_sched_debug>: problems involving the choice of applications to run.
<work_fetch_debug>: problems involving work fetch (which projects are asked for work, and how much).

Of course it isn't the first time we asked it and something tells me it won't be the last. So until that time, my answer to your question is that the gyroscopical theorism of the genotiplex is merely crossing the dyhandrum in alpha where it should be dissecting it in a 90 degree angle opposing the diorama.

ROFL :) I appreciate your humor :)
I will enable logging flags (and thanks for reminding what they should be) next time I will have such situation. For now there are 14 AP tasks to crunch and MW disabled so situation can't be reproduced.

---