Thanks, Multibeam GPU tasks are going out to both Stock & Anonymous Platform 
running hosts, and Astropulse GPU tasks to Anonymous Platform running hosts,

One thing i've noticed on my XP3200+ host is that the 'Number of tasks 
completed' record for Stock 6.03 is one less than the 'Consecutive valid 
tasks' record,
is that because the counting started at result Zero, or has it been excluded 
because one of the completed tasks was a 'SETI@Home Informational message -9 
result_overflow' result?

http://setiathome.berkeley.edu/host_app_versions.php?hostid=5306154

http://setiathome.berkeley.edu/results.php?hostid=5306154

Claggy

----- Original Message ----- 
From: "David Anderson" <[email protected]>
To: "Richard Haselgrove" <[email protected]>
Cc: "Stephen Maclagan" <[email protected]>
Sent: Thursday, October 06, 2011 3:55 AM
Subject: Re: [boinc_dev] Seti@home scheduler inability to send out Wu's to 
certain GPU's


> OK, I think I fixed this; it will be in SAH tomorrow.
> -- David
>
> On 05-Oct-2011 5:12 PM, Richard Haselgrove wrote:
>> This from BOINC v6.12.34
>>
>> --- On *Thu, 6/10/11, David Anderson /<[email protected]>/* wrote:
>>
>>
>>     From: David Anderson <[email protected]>
>>     Subject: Re: [boinc_dev] Seti@home scheduler inability to send out 
>> Wu's to
>>     certain GPU's
>>     To: "Richard Haselgrove" <[email protected]>
>>     Cc: "Stephen Maclagan" <[email protected]>
>>     Date: Thursday, 6 October, 2011, 0:28
>>
>>     please send scheduler_request files.
>>     -- David
>>
>>     On 05-Oct-2011 4:15 PM, Richard Haselgrove wrote:
>>      > Likewise. I have twin hosts, both Q6600 plus 9800GT (so 'pure' 
>> cuda, again at
>>      > cuda23 level). The anonymous platform member of the pair is 
>> getting new work,
>>      > but the one I've just set to stock work and reset got:
>>      > 06/10/2011 00:05:04 | SETI@home <mailto:SETI@home> | Resetting 
>> project
>>      > 06/10/2011 00:05:08 | SETI@home <mailto:SETI@home> | work fetch 
>> resumed
>>     by user
>>      > 06/10/2011 00:05:10 | SETI@home <mailto:SETI@home> | [sched_op] 
>> Starting
>>      > scheduler request
>>      > 06/10/2011 00:05:10 | SETI@home <mailto:SETI@home> | Sending 
>> scheduler
>>     request:
>>      > To fetch work.
>>      > 06/10/2011 00:05:10 | SETI@home <mailto:SETI@home> | Requesting 
>> new tasks for
>>      > NVIDIA GPU
>>      > 06/10/2011 00:05:10 | SETI@home <mailto:SETI@home> | [sched_op] 
>> CPU work
>>      > request: 0.00 seconds; 0.00 CPUs
>>      > 06/10/2011 00:05:10 | SETI@home <mailto:SETI@home> | [sched_op] 
>> NVIDIA
>>     GPU work
>>      > request: 1.00 seconds; 0.75 GPUs
>>      > 06/10/2011 00:05:13 | SETI@home <mailto:SETI@home> | Scheduler 
>> request
>>      > completed: got 0 new tasks
>>      > 06/10/2011 00:05:13 | SETI@home <mailto:SETI@home> | [sched_op] 
>> Server
>>     version 613
>>      > 06/10/2011 00:05:13 | SETI@home <mailto:SETI@home> | No tasks sent
>>      > 06/10/2011 00:05:13 | SETI@home <mailto:SETI@home> | No tasks are
>>     available for
>>      > SETI@home <mailto:SETI@home> Enhanced
>>      > 06/10/2011 00:05:13 | SETI@home <mailto:SETI@home> | Tasks for CPU 
>> are
>>      > available, but your preferences are set to not accept them
>>      > 06/10/2011 00:05:13 | SETI@home <mailto:SETI@home> | Project 
>> requested
>>     delay of
>>      > 303 seconds
>>      > 06/10/2011 00:05:13 | SETI@home <mailto:SETI@home> | [sched_op] 
>> Deferring
>>      > communication for 5 min 3 sec
>>      > 06/10/2011 00:05:13 | SETI@home <mailto:SETI@home> | [sched_op] 
>> Reason:
>>      > requested by project
>>      > 06/10/2011 00:05:15 | SETI@home <mailto:SETI@home> | Started 
>> download of
>>      > arecibo_181.png
>>      > This is
>>     http://setiathome.berkeley.edu/show_host_detail.php?hostid=3751792, 
>> if
>>      > you want to check logs. My event log is timed in UTC +1.
>>      >
>>      > --- On *Wed, 5/10/11, Stephen Maclagan 
>> /<[email protected]
>> 
>> <http://uk.mc865.mail.yahoo.com/mc/[email protected]>>/*
>>     wrote:
>>      >
>>      >
>>      > From: Stephen Maclagan <[email protected]
>> 
>> <http://uk.mc865.mail.yahoo.com/mc/[email protected]>>
>>      > Subject: Re: [boinc_dev] Seti@home scheduler inability to send out 
>> Wu's to
>>      > certain GPU's
>>      > To: "David Anderson" <[email protected]
>> 
>> <http://uk.mc865.mail.yahoo.com/mc/[email protected]>>,
>>     "[email protected]
>> 
>> <http://uk.mc865.mail.yahoo.com/mc/[email protected]>"
>>      > <[email protected]
>> 
>> <http://uk.mc865.mail.yahoo.com/mc/[email protected]>>
>>      > Date: Wednesday, 5 October, 2011, 23:52
>>      >
>>      > Thanks, that fixed work fetch for ATI Anonymous platform, But what
>>      > about Stock Nvidia Cuda work fetch?
>>      >
>>      > I've fired an old host of mine up, and set it at getting Stock 
>> work
>>      > from Seti,
>>      >
>>      >
>>      > http://setiathome.berkeley.edu/show_host_detail.php?hostid=5306154
>>      >
>>      >
>>      > it's managed to get a few CPU tasks, but keeps getting there's no 
>> tasks
>>      > available for Nvidia GPU work fetches,
>>      > i'd expect it to get 6.09 Cuda23 tasks:
>>      >
>>      > 05/10/2011 23:04:44 SETI@home [sched_op_debug] Starting scheduler
>>      > request
>>      >
>>      > 05/10/2011 23:04:44 SETI@home Sending scheduler request: To fetch
>>      > work.
>>      >
>>      > 05/10/2011 23:04:44 SETI@home Requesting new tasks for GPU
>>      >
>>      > 05/10/2011 23:04:44 SETI@home [sched_op_debug] CPU work request: 
>> 0.00
>>      > seconds; 0.00 CPUs
>>      >
>>      > 05/10/2011 23:04:44 SETI@home [sched_op_debug] NVIDIA GPU work 
>> request:
>>      > 55563.90 seconds; 1.00 GPUs
>>      >
>>      > 05/10/2011 23:04:44 SETI@home [sched_op_debug] ATI GPU work 
>> request:
>>      > 0.00 seconds; 0.00 GPUs
>>      >
>>      > 05/10/2011 23:04:56 SETI@home Scheduler request completed: got 0 
>> new
>>      > tasks
>>      >
>>      > 05/10/2011 23:04:56 SETI@home [sched_op_debug] Server version 613
>>      >
>>      > 05/10/2011 23:04:56 SETI@home Message from server: No tasks sent
>>      >
>>      > 05/10/2011 23:04:56 SETI@home Message from server: No tasks are
>>      > available for SETI@home Enhanced
>>      >
>>      > 05/10/2011 23:04:56 SETI@home Message from server: Tasks for CPU 
>> are
>>      > available, but your preferences are set to not accept them
>>      >
>>      > 05/10/2011 23:04:56 SETI@home Project requested delay of 303 
>> seconds
>>      >
>>      > 05/10/2011 23:04:56 SETI@home [sched_op_debug] Deferring 
>> communication
>>      > for 5 min 3 sec
>>      >
>>      > 05/10/2011 23:04:56 SETI@home [sched_op_debug] Reason: requested 
>> by
>>      > project
>>      >
>>      > 05/10/2011 23:10:01 SETI@home [sched_op_debug] Starting scheduler
>>      > request
>>      >
>>      > 05/10/2011 23:10:01 SETI@home Sending scheduler request: To fetch
>>      > work.
>>      >
>>      > 05/10/2011 23:10:01 SETI@home Requesting new tasks for GPU
>>      >
>>      > 05/10/2011 23:10:01 SETI@home [sched_op_debug] CPU work request: 
>> 0.00
>>      > seconds; 0.00 CPUs
>>      >
>>      > 05/10/2011 23:10:01 SETI@home [sched_op_debug] NVIDIA GPU work 
>> request:
>>      > 0.00 seconds; 0.00 GPUs
>>      >
>>      > 05/10/2011 23:10:01 SETI@home [sched_op_debug] ATI GPU work 
>> request:
>>      > 73877.28 seconds; 1.00 GPUs
>>      >
>>      > 05/10/2011 23:10:14 SETI@home Scheduler request completed: got 0 
>> new
>>      > tasks
>>      >
>>      > 05/10/2011 23:10:14 SETI@home [sched_op_debug] Server version 613
>>      >
>>      > 05/10/2011 23:10:14 SETI@home Message from server: No tasks sent
>>      >
>>      > 05/10/2011 23:10:14 SETI@home Project requested delay of 303 
>> seconds
>>      >
>>      > 05/10/2011 23:10:14 SETI@home [sched_op_debug] Deferring 
>> communication
>>      > for 5 min 3 sec
>>      >
>>      > 05/10/2011 23:10:14 SETI@home [sched_op_debug] Reason: requested 
>> by
>>      > project
>>      >
>>      >
>>      >
>>      > Since this host also has an ATI GPU and there's no Stock ATI app,
>>      > shouldn't the Server say so?
>>      >
>>      >
>>      >
>>      > sched_request_setiathome.berkeley.edu.xml attached.
>>      >
>>      >
>>      >
>>      > Claggy
>>      >
>>      >
>>      >
>>      >
>>      >
>>      > ----- Original Message -----
>>      >
>>      > From: "David Anderson" <[email protected]
>>     <http://uk.mc865.mail.yahoo.com/mc/[email protected]>
>>      > 
>> <http://uk.mc865.mail.yahoo.com/mc/[email protected]>>
>>      >
>>      > To: <[email protected]
>> 
>> <http://uk.mc865.mail.yahoo.com/mc/[email protected]>
>>      > 
>> <http://uk.mc865.mail.yahoo.com/mc/[email protected]>>
>>      >
>>      > Sent: Tuesday, October 04, 2011 12:46 AM
>>      >
>>      > Subject: Re: [boinc_dev] Seti@home scheduler inability to send out 
>> Wu's
>>      > to certain GPU's
>>      >
>>      >
>>      >
>>      >
>>      >
>>      > > This was due to a bug introduced into the BOINC scheduler.
>>      >
>>      > > I fixed this bug, and a new scheduler will be deployed soon.
>>      >
>>      > > -- David
>>      >
>>      > >
>>      >
>>      > > On 03-Oct-2011 3:06 PM, Stephen Maclagan wrote:
>>      >
>>      > >> Since the last Maintenance day there's been a lot of users
>>      > reporting
>>      >
>>      > >> problems getting GPU Wu's,
>>      >
>>      > >>
>>      >
>>      > >> Urs Echternacht has been trying to get ATI Linux work for 
>> testing
>>      > his
>>      >
>>      > >> ATI Linux apps, and failed,
>>      >
>>      > >>
>>      >
>>      > >>
>>      >
>>      > >>
>>      >
>>      > >> Anthony Arbuzoff reports his host getting the following 
>> message:
>>      > "To
>>      >
>>      > >> use all the applications of this project, working in the GP, 
>> update
>>      > the
>>      >
>>      > >> driver to the latest version" (Google translate from Russian),
>>      >
>>      > >>
>>      >
>>      > >> Basically his host was getting 6.08 Wu's earlier (because he's
>>      > running
>>      >
>>      > >> 186.80 drivers), now the scheduler isn't sending those, and 
>> reports
>>      > it
>>      >
>>      > >> hasn't got the 190.38 drivers required for the 6.09 app,
>>      >
>>      > >>
>>      >
>>      > >>
>>      >
>>      > >> http://setiathome.berkeley.edu/forum_thread.php?id=65658
>>      > >>
>>      >
>>      > >> 
>> http://setiathome.berkeley.edu/show_host_detail.php?hostid=5735602
>>      >
>>      > >>
>>      >
>>      > >>
>>      > >> I haven't managed to get Wu's for my HD5770 (using Anonymous
>>      > platform),
>>      > >> my GTX460 in the same host gets Wu's with little problem,
>>      > >> if i disable CPU& Nvidia work fetch in the project
>>      > preferences,
>>      >
>>      > >> and only ask for ATI work,
>>      >
>>      > >>
>>      >
>>      > >> all i get from the server is there's no work available or no 
>> work
>>      > sent,
>>      >
>>      > >> even if i snip Wu's out of my client_state.xml,
>>      >
>>      > >>
>>      >
>>      > >> the server won't resend those Wu's to my ATI (both Astropulse 
>> and
>>      >
>>      > >> Multibeam), same if i reset the project!!
>>      >
>>      > >>
>>      >
>>      > >>
>>      >
>>      > >> 
>> http://setiathome.berkeley.edu/show_host_detail.php?hostid=5427475
>>      >
>>      > >>
>>      >
>>      > >>
>>      > >> Jeff Bakle also reports he can't get work for his 8800GT
>>      > eithier:
>>      > >>
>>      > >> 
>> http://setiathome.berkeley.edu/show_host_detail.php?hostid=4694672
>>      >
>>      > >>
>>      >
>>      > >>
>>      > >> Zapiao can't get work for his HD5x00 (using Anonymous
>>      > platform)
>>      > >>
>>      > >> 
>> http://setiathome.berkeley.edu/show_host_detail.php?hostid=5934358
>>      >
>>      > >>
>>      >
>>      > >>
>>      > >> But other users like Mike can still get work for his HD5800 (as
>>      > of the
>>      > >> 2nd oct), but is now rebranding CPU work to his GPU:
>>      > >>
>>      > >> 
>> http://setiathome.berkeley.edu/show_host_detail.php?hostid=5735690
>>      >
>>      > >>
>>      >
>>      > >>
>>      > >> Claggy
>>      > >> _______________________________________________
>>      > >> boinc_dev mailing list
>>      > >> [email protected]
>> 
>> <http://uk.mc865.mail.yahoo.com/mc/[email protected]>
>>      > 
>> <http://uk.mc865.mail.yahoo.com/mc/[email protected]>
>>      > >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
>>      > >> To
>>      > unsubscribe, visit the above URL and
>>      >
>>      > >> (near bottom of page) enter your email address.
>>      > >
>>      > _______________________________________________
>>      >
>>      > > boinc_dev mailing list
>>      >
>>      > > [email protected]
>> 
>> <http://uk.mc865.mail.yahoo.com/mc/[email protected]>
>>      > 
>> <http://uk.mc865.mail.yahoo.com/mc/[email protected]>
>>      >
>>      > > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
>>      > > To
>>      > unsubscribe, visit the above URL and
>>      >
>>      > > (near bottom of page) enter your email address.
>>      >
>>      > -----Inline Attachment Follows-----
>>      >
>>      > _______________________________________________
>>      > boinc_dev mailing list
>>      > [email protected]
>> 
>> <http://uk.mc865.mail.yahoo.com/mc/[email protected]>
>>      > 
>> <http://uk.mc865.mail.yahoo.com/mc/[email protected]>
>>      > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
>>      > To unsubscribe, visit the above URL and
>>      > (near bottom of page) enter your email address.
>>      >
>> 

_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to