Now the similarity - when those WU's finally do run, they error with the same exit code -5 = no result file.

I got my first error -5 today, while doing some manual suspend/resume work to get a Beta test run to start before its time.

The full message is:

<core_client_version>6.6.28</core_client_version>
<![CDATA[
<message>
 - exit code -5 (0xfffffffb)
</message>
<stderr_txt>
SETI@home error -5 Can't open file
(work_unit.sah) in read_wu_state() errno=2

File: ..\worker.cpp
Line: 123

</stderr_txt>
]]>

- so nothing to do with result files. [BOINC's message about a missing file is always a consequence of the crash, and says nothing whatsoever about the cause of the crash]

The behaviour of BOINC when suspending/resuming CUDA tasks does still seem to have some problems - I'll try to write it up for boinc_alpha.

Knowing the usual response - Fred, would you be willing to catch some debug logs and screen shots (of BOINC, not the footy) next time there's a good match on?

Re-looking at my results, mine matches your result exactly, Richard.
Anything I can do to help, of course. I could even watch something other than soccer ;). What debug flags / screen-shots are needed?

F.

---

Re-looking at my results, mine matches your result exactly, Richard.
Anything I can do to help, of course. I could even watch something other than soccer ;). What debug flags / screen-shots are needed?

F.

Jorden usually says "Run at least once with these flags on: <work_fetch_debug>, <sched_op_debug> and one run with <debt_debug>", but I think he's away this weekend, so we can make our own rules ;-)

Don't worry about work_fetch or debt_debug for this one: sched_op hardly seems to do anything. I think we're going to need <cpu_sched> and <cpu_sched_debug>.

For screenshots, I was thinking of those "every 2 that start, one reports and the second goes to 'waiting to run'" - something showing those 'waiting to run' on the tasks tab, perhaps with a matching later one showing the errors.

Re-looking at my results, mine matches your result exactly, Richard.
Anything I can do to help, of course. I could even watch something other than soccer ;). What debug flags / screen-shots are needed?

F.

Jorden usually says "Run at least once with these flags on: <work_fetch_debug>, <sched_op_debug> and one run with <debt_debug>", but I think he's away this weekend, so we can make our own rules ;-)

Don't worry about work_fetch or debt_debug for this one: sched_op hardly seems to do anything. I think we're going to need <cpu_sched> and <cpu_sched_debug>.

For screenshots, I was thinking of those "every 2 that start, one reports and the second goes to 'waiting to run'" - something showing those 'waiting to run' on the tasks tab, perhaps with a matching later one showing the errors.

OK. I will give that a whirl tomorrow (should be watching the Spanish Grand Prix anyway). I've now upgraded to CUDA2.2 (and had to increase the GPU fan speed considerably) and BOINC 6.6.28 so, if it still happens it will prove that it is not driver or 6.6.23 causing it.

F.

---

Well I've gone back and given this another go and am getting the same results as you are :-


<![CDATA[
<message>
- exit code -5 (0xfffffffb)
</message>
<stderr_txt>
SETI@home error -5 Can't open file
(work_unit.sah) in read_wu_state() errno=2

File: ..\worker.cpp
Line: 123


</stderr_txt>

Also get <status>-161</status> in the file_info section of client_state.xml which I use to track the errors and do a fix up.

Apologies for the "no result file" red herring. I think I had this problem mixed up with another issue I had.

I've also tried running with a few avg/nax_ncpus values ranging from 0.15 down to 0.04 on a Core 2 6600 / GT9600T (driver 18250) on Windows XP (not exhaustively).

I hadn't previously tried the lower settings but this seems on my set up to produce the same level of -5 errors when suspending as the
higher settings.
0.099 which seemed to be most reliable I found now does still give some -5 errors so it is hard to say what the full influences are.

Another thing I have noticed on just this machine is that some CUDA jobs occasionally hang and the elapsed and completed times continue to clock up into hours but progress doesn't move.
I don't think they are VLAR tasks (I have been doing a fairly coarse rebranding of those since I started getting flooded by them) and stop/starting BOINC kicks them into life again.

I also notice that some versions of app_info.xml in these threads give avg/max_ncpus = 1.000000 settings for the the non cuda apps.
My files do not have this entry. Is this significant or is it just for completeness and the 1.000000 the default setting anyway?

As I seem to be able to recreate the error -5s at will, I am happy to produce some debug output if it is of use.


John.

---

GPU Users Group

I think I've worked out what's happening here, and I've submitted a bug report. Fred, you have mail (ISP permitting).

It seems likely to happen whenever a running CUDA task is pre-empted, and a new CUDA task started in its place. I think it will happen with every version of BOINC from v6.6.23 onwards, because of a bug with new code added then:

Changes for 6.6.23

- client: for coproc jobs, don't start a job while a quit is pending. Otherwise the new job may fail on memory allocation.

If the job start is delayed to allow the old one to tidy up after itself, the next attempt is treated as a re-start, instead of a new start: that's presumably why the work_unit.sah file isn't copied into the slot directory ready for use.

I wasn't familiar with using the debug output so thought I'd have a go anyway out of interest. I assume that is what you were also seeing Richard?

1. When everything works OK after suspending a task, another one runs OK.

2. Sometimes an attempt to start a new task after a supend fails because the previous task has not exited (or it thinks it hasn't)
When this occurs however it has already changed the sched state of the task from 0 to 2.

When it does manage to run the task it does it as a resume not a start. As the task has never run previously you get
the error and it exits.


John




---------------------------------------------------------------------------------------------------------------------------------------

Here is a suspend that does not error :-


10-May-2009 20:17:07 [SETI@home] task 07fe09ab.14570.6207.11.8.131_1 suspended by user
10-May-2009 20:17:07 [---] [cpu_sched_debug] Request CPU reschedule: result suspended, resumed or aborted by user
10-May-2009 20:17:08 [---] [cpu_sched_debug] schedule_cpus(): start
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] scheduling 07fe09ab.14570.6207.11.8.151_1 (coprocessor job, FIFO)
10-May-2009 20:17:08 [---] [cpu_sched_debug] reserving 1 of coproc CUDA
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] highest debt: -3600.000000 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] scheduling 07fe09aa.24575.16841.15.8.21_0 (CPU job, debt order)
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] highest debt: -7200.000000 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] scheduling 01fe09ae.13226.25021.14.8.65_0 (CPU job, debt order)
10-May-2009 20:17:08 [---] [cpu_sched_debug] Request enforce CPU schedule: schedule_cpus
10-May-2009 20:17:08 [---] [cpu_sched_debug] enforce_schedule(): start
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] want to run: 07fe09ab.14570.6207.11.8.151_1
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] want to run: 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] want to run: 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] processing 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] processing 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] processing 07fe09ab.14570.6207.11.8.151_1
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09aa.24575.16841.15.8.21_0 sched state 2 next 2 task state 1
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.75_0 sched state 1 next 1 task state 0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.61_0 sched state 1 next 1 task state 0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.72_0 sched state 1 next 1 task state 0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.74_0 sched state 1 next 1 task state 0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.31_1 sched state 1 next 1 task state 0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 01fe09ae.13226.25021.14.8.65_0 sched state 2 next 2 task state 1
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.129_1 sched state 1 next 1 task state 0
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.131_1 sched state 2 next 1 task state 1
10-May-2009 20:17:08 [SETI@home] [cpu_sched] Preempting 07fe09ab.14570.6207.11.8.131_1 (left in memory)
10-May-2009 20:17:08 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.151_1 sched state 0 next 2 task state 0
10-May-2009 20:17:08 [SETI@home] Starting 07fe09ab.14570.6207.11.8.151_1
10-May-2009 20:17:08 [SETI@home] [cpu_sched] Starting 07fe09ab.14570.6207.11.8.151_1 (initial)
10-May-2009 20:17:08 [SETI@home] Starting task 07fe09ab.14570.6207.11.8.151_1 using setiathome_enhanced version 608
10-May-2009 20:17:08 [---] [cpu_sched_debug] enforce_schedule: end
10-May-2009 20:17:26 [---] Exit requested by user
10-May-2009 20:17:27 [---] [cpu_sched_debug] Request CPU reschedule: exit_tasks


---------------------------------------------------------------------------------------------------------------------------------------



---------------------------------------------------------------------------------------------------------------------------------------

and here is one that does error from the point of suspend onwards :-


10-May-2009 20:33:18 [SETI@home] task 07fe09ab.14570.6207.11.8.135_1 suspended by user
10-May-2009 20:33:18 [---] [cpu_sched_debug] Request CPU reschedule: result suspended, resumed or aborted by user
10-May-2009 20:33:18 [---] [cpu_sched_debug] schedule_cpus(): start
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] scheduling 07fe09ab.14570.6207.11.8.234_0 (coprocessor job, FIFO)
10-May-2009 20:33:18 [---] [cpu_sched_debug] reserving 1 of coproc CUDA
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] highest debt: -3600.000000 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] scheduling 07fe09aa.24575.16841.15.8.21_0 (CPU job, debt order)
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] highest debt: -7200.000000 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] scheduling 01fe09ae.13226.25021.14.8.65_0 (CPU job, debt order)
10-May-2009 20:33:18 [---] [cpu_sched_debug] Request enforce CPU schedule: schedule_cpus
10-May-2009 20:33:18 [---] [cpu_sched_debug] enforce_schedule(): start
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] want to run: 07fe09ab.14570.6207.11.8.234_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] want to run: 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] want to run: 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] processing 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] processing 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] processing 07fe09ab.14570.6207.11.8.234_0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09aa.24575.16841.15.8.21_0 sched state 2 next 2 task state 1
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.75_0 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.61_0 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.72_0 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.74_0 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.31_1 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 01fe09ae.13226.25021.14.8.65_0 sched state 2 next 2 task state 1
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.129_1 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.131_1 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.151_1 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.141_0 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.154_0 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.138_1 sched state 1 next 1 task state 0
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.142_0 sched state 1 next 1 task state 9
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.135_1 sched state 2 next 1 task state 1
10-May-2009 20:33:18 [SETI@home] [cpu_sched] Preempting 07fe09ab.14570.6207.11.8.135_1 (removed from memory)
10-May-2009 20:33:18 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.234_0 sched state 0 next 2 task state 0

**** state of new task 234 = 0 ****

10-May-2009 20:33:18 [---] [cpu_sched_debug] enforce_schedule: end
10-May-2009 20:33:18 [---] [cpu_sched_debug] coproc quit pending, deferring start
10-May-2009 20:33:18 [---] [cpu_sched_debug] Request enforce CPU schedule: coproc quit retry

**** unable to start new task 234 - last task not exited yet??? ****

10-May-2009 20:33:19 [---] [cpu_sched_debug] enforce_schedule(): start
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] want to run: 07fe09ab.14570.6207.11.8.234_0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] want to run: 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] want to run: 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] processing 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] processing 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] processing 07fe09ab.14570.6207.11.8.234_0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09aa.24575.16841.15.8.21_0 sched state 2 next 2 task state 1
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.75_0 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.61_0 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.72_0 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.74_0 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.31_1 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 01fe09ae.13226.25021.14.8.65_0 sched state 2 next 2 task state 1
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.129_1 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.131_1 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.151_1 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.141_0 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.154_0 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.138_1 sched state 1 next 1 task state 0
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.142_0 sched state 1 next 1 task state 9
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.135_1 sched state 1 next 1 task state 8
10-May-2009 20:33:19 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.234_0 sched state 2 next 2 task state 0

**** State of new task 234 now = 2 ****

10-May-2009 20:33:19 [---] [cpu_sched_debug] enforce_schedule: end
10-May-2009 20:33:19 [---] [cpu_sched_debug] coproc quit pending, deferring start
10-May-2009 20:33:19 [---] [cpu_sched_debug] Request enforce CPU schedule: coproc quit retry

**** Second attempt to restart task failed ****

10-May-2009 20:33:20 [---] [cpu_sched_debug] Request CPU reschedule: application exited
10-May-2009 20:33:20 [---] [cpu_sched_debug] schedule_cpus(): start
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] scheduling 07fe09ab.14570.6207.11.8.234_0 (coprocessor job, FIFO)
10-May-2009 20:33:20 [---] [cpu_sched_debug] reserving 1 of coproc CUDA
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] highest debt: -3600.000000 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] scheduling 07fe09aa.24575.16841.15.8.21_0 (CPU job, debt order)
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] highest debt: -7200.000000 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] scheduling 01fe09ae.13226.25021.14.8.65_0 (CPU job, debt order)
10-May-2009 20:33:20 [---] [cpu_sched_debug] Request enforce CPU schedule: schedule_cpus
10-May-2009 20:33:20 [---] [cpu_sched_debug] enforce_schedule(): start
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] want to run: 07fe09ab.14570.6207.11.8.234_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] want to run: 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] want to run: 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] processing 07fe09aa.24575.16841.15.8.21_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] processing 01fe09ae.13226.25021.14.8.65_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] processing 07fe09ab.14570.6207.11.8.234_0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09aa.24575.16841.15.8.21_0 sched state 2 next 2 task state 1
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.75_0 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.61_0 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.72_0 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.74_0 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.4571.11.8.31_1 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 01fe09ae.13226.25021.14.8.65_0 sched state 2 next 2 task state 1
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.129_1 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.131_1 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.151_1 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.141_0 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.154_0 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.138_1 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.142_0 sched state 1 next 1 task state 9
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.135_1 sched state 1 next 1 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched_debug] 07fe09ab.14570.6207.11.8.234_0 sched state 2 next 2 task state 0
10-May-2009 20:33:20 [SETI@home] [cpu_sched] Starting 07fe09ab.14570.6207.11.8.234_0(resume)

**** Third attempt -now trying to resume task 234 which has never run yet ****

10-May-2009 20:33:20 [SETI@home] Restarting task 07fe09ab.14570.6207.11.8.234_0 using setiathome_enhanced version 608
10-May-2009 20:33:20 [---] [cpu_sched_debug] enforce_schedule: end
10-May-2009 20:33:21 [---] [cpu_sched_debug] Request CPU reschedule: application exited
10-May-2009 20:33:21 [SETI@home] Computation for task 07fe09ab.14570.6207.11.8.234_0 finished

**** Task 234 exits without doing anything ****


---------------------------------------------------------------------------------------------------------------------------------------

---

GPU Users Group

I wasn't familiar with using the debug output so thought I'd have a go anyway out of interest. I assume that is what you were also seeing Richard?

1. When everything works OK after suspending a task, another one runs OK.

2. Sometimes an attempt to start a new task after a supend fails because the previous task has not exited (or it thinks it hasn't)
When this occurs however it has already changed the sched state of the task from 0 to 2.

When it does manage to run the task it does it as a resume not a start. As the task has never run previously you get
the error and it exits.

John

Yes, that's exactly what I reported - both the change from sched state 0 to sched state 2, and the restart.

I wasn't familiar with using the debug output so thought I'd have a go anyway out of interest. I assume that is what you were also seeing Richard?

1. When everything works OK after suspending a task, another one runs OK.

2. Sometimes an attempt to start a new task after a supend fails because the previous task has not exited (or it thinks it hasn't)
When this occurs however it has already changed the sched state of the task from 0 to 2.

When it does manage to run the task it does it as a resume not a start. As the task has never run previously you get
the error and it exits.

John

Yes, that's exactly what I reported - both the change from sched state 0 to sched state 2, and the restart.

I'm trying to work out why the completion of one EDF task on my GTX295 should shove the WU on the other core into "Waiting to tun" so that 2 new tasks can be started simultaneously (and that "Waiting to run" WU then loses its output file).
@Richard: You have mail - I can't make head nor tail of it but it may contribute another element to the eventual fix.

F.

---

@Richard: You have mail.

Received and forwarded to the bug-reporting list.

@Richard: You have mail.

Received and forwarded to the bug-reporting list.

Thank you. I guess I really ought to sign up.

F.

[edit]Creating that eMail sent my DCF from .23 to .64 resulting in another EDF and I now have 30+ WU's "Waiting to run" than will fail (if I don't abort them).[/edit]

[edit2]Another feature of this is that when the WU that is pre-empted is close to the end of crunching (as is often the case on my GTX295), the elapsed time recorded against it is close to full crunch-time. If it is a "shorty" - no checkpoint - it restarts from the beginning so the eventual crunch-time is double what it should be which kicks the DCF further out and prolongs the EDF mode. [/edit2]

---

I think I've worked out what's happening here, and I've submitted a bug report. Fred, you have mail (ISP permitting).

It seems likely to happen whenever a running CUDA task is pre-empted, and a new CUDA task started in its place. I think it will happen with every version of BOINC from v6.6.23 onwards, because of a bug with new code added then:

Changes for 6.6.23

- client: for coproc jobs, don't start a job while a quit is pending. Otherwise the new job may fail on memory allocation.

If the job start is delayed to allow the old one to tidy up after itself, the next attempt is treated as a re-start, instead of a new start: that's presumably why the work_unit.sah file isn't copied into the slot directory ready for use.

Presumably its less likely to preempt tasks under 6.6.28 than 23. But still its an issue that needs to be addressed.

Richard I cross posted your message over at GPUgrid (hope you don't mind). A bunch of the guys over there are having issues with tasks aborting, possibly unrelated but you never know.

---

BOINC blog

Recived error:
11/05/2009 19:25:05 SETI@home [error] No app version for result: windows_x86_64 608

with :
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.04</max_ncpus>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>

What is wrong here ??

Recived error:
11/05/2009 19:25:05 SETI@home [error] No app version for result: windows_x86_64 608

with :
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.04</max_ncpus>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>

What is wrong here ??

Could it be because the platform is x86_64 and <file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name> is only for the x86? That's just a guess though. Other than that and not having the flop count it is exactly like mine.

---

PROUD MEMBER OF Team Starfire World BOINC

I would try it without the <platform> tag. I don't think it is contributing anything, anyway, as you are calling a 32-bit App.

F.

---

BuMp.

---

Rob

there is not need to Bump as it is preserved in FAQ's, Astropulse, Cuda, MultiBeam - Read Only along with a link to this thread.

Regards

---

Please consider a Donation to the Seti Project.

I had the same problem just remove the _64 from the Platform Tag and all should be well.
Dave

---

Thanks all.
This stripped version works well now on my host (I crunch only MB on it for now).

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_x64_SSSE3x.exe</name>
<executable/>
</file_info>
<file_info>
<name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_v8b_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.04</max_ncpus>
<plan_class>cuda</plan_class>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V11_VLARKill_refined.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>

I have just set up this pc to do Astropulse only using the Intel Opt APP
GenuineIntelIntel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz [x86 Family 6 Model 15 Stepping 11] (2 processors)
It is returning 2 results in around 15hrs each.
Question: Is there a reason why this is quicker than my i7 which is returning 8 results in around 20hrs each.
I realise that it may be because 1 or more of the i7 cores is feeding the Cuda apps but 5hrs is a big difference.
I believe I have the same AP Opt app running on both pc's (ap_5.03r112_SSE3.exe).
Should I run ssse4 app on the i7.
Thank's in advance.
Dave

---

Check around Dave, you will see others have noticed the i7 as being slower though most are compared to Quads. It has to do with the hyperthreading ( basically running two WUs on one core). Though it takes you longer to do each WU, you are doing 8 to their 4. (or 2 in this case.)

---

PROUD MEMBER OF Team Starfire World BOINC