Ok I put up 2 or 3 files in 3 or 4 entries in the following thread:

Problem can't download cpu wu's, gpu's wu's are fine though

Maybe this will help?

42 4/12/2013 1:07:05 PM [wfd]: work fetch start
43 4/12/2013 1:07:05 PM [wfd] ------- start work fetch state -------
44 4/12/2013 1:07:05 PM [wfd] target work buffer: 345600.00 + 0.00 sec
45 4/12/2013 1:07:05 PM [wfd] CPU: shortfall 994090.56 nidle 0.00 saturated 9450.33 busy 0.00 RS fetchable 0.00 runnable 100.00
46 Einstein@Home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks)
47 SETI@home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
48 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: shortfall 333557.59 nidle 0.00 saturated 12009.79 busy 0.00 RS fetchable 0.00 runnable 100.00
49 Einstein@Home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks) (blocked by prefs)
50 SETI@home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
51 Einstein@Home 4/12/2013 1:07:05 PM [wfd] overall LTD 0.00
52 SETI@home 4/12/2013 1:07:05 PM [wfd] overall LTD -236995.78
53 4/12/2013 1:07:05 PM [wfd] ------- end work fetch state -------

Have you already tried the set Use NVIDIA GPU to no and do some requests trick yet?

Why can't I do both cpu and gpu work? Is it now forbidden to do both?

And no I haven't, I don't see that as a problem.

Maybe I should just detach...

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Why can't I do both cpu and gpu work? Is it now forbidden to do both?

And no I haven't, I don't see that as a problem.

Maybe I should just detach...

Oh, Jesus, Vic. Folks are just trying to help you sort things.
If you wanna go, just do it without fanfare.

Unless I misread you and you are just talking about a detach and reattach.

Sorry if I overreacted in that case.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Why can't I do both cpu and gpu work? Is it now forbidden to do both?

And no I haven't, I don't see that as a problem.

Maybe I should just detach...

Oh, Jesus, Vic. Folks are just trying to help you sort things.
If you wanna go, just do it without fanfare.

Unless I misread you and you are just talking about a detach and reattach.

Sorry if I overreacted in that case.

I'm a bit frustrated, I don't see anything on My end wrong, I mean we are allowed to download 100 wu's for the cpu and 100 wu's for the gpus aren't We?

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I put cc config back to it's normal unlogged state...

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Why can't I do both cpu and gpu work? Is it now forbidden to do both?

And no I haven't, I don't see that as a problem.

Maybe I should just detach...

Oh, Jesus, Vic. Folks are just trying to help you sort things.
If you wanna go, just do it without fanfare.

Unless I misread you and you are just talking about a detach and reattach.

Sorry if I overreacted in that case.

I'm a bit frustrated, I don't see anything on My end wrong, I mean we are allowed to download 100 wu's for the cpu and 100 wu's for the gpus aren't We?

Yes...and actually, now that I think about it, a detach and reattach might not be a bad thing to try.

Given that the download speed is so fast, and work availability is so good now, that might not be a bad gamble, Vic.

You have little to lose in trying, and your GPU will be full of work in no time at all. Whatcha think?

I really am on your side, my friend.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Why can't I do both cpu and gpu work? Is it now forbidden to do both?

And no I haven't, I don't see that as a problem.

Maybe I should just detach...

Oh, Jesus, Vic. Folks are just trying to help you sort things.
If you wanna go, just do it without fanfare.

Unless I misread you and you are just talking about a detach and reattach.

Sorry if I overreacted in that case.

I'm a bit frustrated, I don't see anything on My end wrong, I mean we are allowed to download 100 wu's for the cpu and 100 wu's for the gpus aren't We?

Yes...and actually, now that I think about it, a detach and reattach might not be a bad thing to try.

Given that the download speed is so fast, and work availability is so good now, that might not be a bad gamble, Vic.

You have little to lose in trying, and your GPU will be full of work in no time at all. Whatcha think?

I really am on your side, my friend.

Actually I don't think that will help any, I'm getting 94 cpu wu's now, I disabled the gpu(ati and nvidia) settings here on Seti and I'm getting/downloaded work.

Thanks Mark, I do realize that, just frustrated and not over you guys.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Actually I don't think that will help any, I'm getting 94 cpu wu's now, I disabled the gpu(ati and nvidia) settings here on Seti and I'm getting/downloaded work.

Wonderful....
Hopefully you have broken the logjam then.

What's important to remember, Vic, is that there is no end of potential help here when you ask for it.

I KNOW how frustrating it can be when things are broken.

But, just look at how many posts there are to this thread since you first reported your problem 3 hours ago.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Ok I put up 2 or 3 files in 3 or 4 entries in the following thread:

Problem can't download cpu wu's, gpu's wu's are fine though

Maybe this will help?

42 4/12/2013 1:07:05 PM [wfd]: work fetch start
43 4/12/2013 1:07:05 PM [wfd] ------- start work fetch state -------
44 4/12/2013 1:07:05 PM [wfd] target work buffer: 345600.00 + 0.00 sec
45 4/12/2013 1:07:05 PM [wfd] CPU: shortfall 994090.56 nidle 0.00 saturated 9450.33 busy 0.00 RS fetchable 0.00 runnable 100.00
46 Einstein@Home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks)
47 SETI@home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
48 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: shortfall 333557.59 nidle 0.00 saturated 12009.79 busy 0.00 RS fetchable 0.00 runnable 100.00
49 Einstein@Home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks) (blocked by prefs)
50 SETI@home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
51 Einstein@Home 4/12/2013 1:07:05 PM [wfd] overall LTD 0.00
52 SETI@home 4/12/2013 1:07:05 PM [wfd] overall LTD -236995.78
53 4/12/2013 1:07:05 PM [wfd] ------- end work fetch state -------

Have you already tried the set Use NVIDIA GPU to no and do some requests trick yet?

Why can't I do both cpu and gpu work? Is it now forbidden to do both?

And no I haven't, I don't see that as a problem.

Maybe I should just detach...

It is a known issue with BOINC. Where it will fill the GPU cache over the CPU cache. I think there was some work done server side to try and correct this, but it may only be effective with newer versions of BOINC. Once you have CPU tasks again reenable GPU fetch and then see how it goes. With the 100 task limits you might have to lower your queue settings to prevent it from doing it again.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Ok I put up 2 or 3 files in 3 or 4 entries in the following thread:

Problem can't download cpu wu's, gpu's wu's are fine though

Maybe this will help?

42 4/12/2013 1:07:05 PM [wfd]: work fetch start
43 4/12/2013 1:07:05 PM [wfd] ------- start work fetch state -------
44 4/12/2013 1:07:05 PM [wfd] target work buffer: 345600.00 + 0.00 sec
45 4/12/2013 1:07:05 PM [wfd] CPU: shortfall 994090.56 nidle 0.00 saturated 9450.33 busy 0.00 RS fetchable 0.00 runnable 100.00
46 Einstein@Home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks)
47 SETI@home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
48 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: shortfall 333557.59 nidle 0.00 saturated 12009.79 busy 0.00 RS fetchable 0.00 runnable 100.00
49 Einstein@Home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks) (blocked by prefs)
50 SETI@home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
51 Einstein@Home 4/12/2013 1:07:05 PM [wfd] overall LTD 0.00
52 SETI@home 4/12/2013 1:07:05 PM [wfd] overall LTD -236995.78
53 4/12/2013 1:07:05 PM [wfd] ------- end work fetch state -------

Have you already tried the set Use NVIDIA GPU to no and do some requests trick yet?

Why can't I do both cpu and gpu work? Is it now forbidden to do both?

And no I haven't, I don't see that as a problem.

Maybe I should just detach...

It is a known issue with BOINC. Where it will fill the GPU cache over the CPU cache. I think there was some work done server side to try and correct this, but it may only be effective with newer versions of BOINC. Once you have CPU tasks again reenable GPU fetch and then see how it goes. With the 100 task limits you might have to lower your queue settings to prevent it from doing it again.

Well I run the anonymous platform which I think is still not supported under the beta v7 or am I wrong? Seems kind of unfair to Me, it's like no v7, no cpu work...

This sucks.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Also important to remember is that these forums
are not exactly real time. The person that might have been able to
correctly answer his first post may have been in bed and might not
see it for another couple of hours. I think it's best to wait a day
for all time zones to have time to read the forum before going into
antsy frustrated mode.

Ok I put up 2 or 3 files in 3 or 4 entries in the following thread:

Problem can't download cpu wu's, gpu's wu's are fine though

Maybe this will help?

42 4/12/2013 1:07:05 PM [wfd]: work fetch start
43 4/12/2013 1:07:05 PM [wfd] ------- start work fetch state -------
44 4/12/2013 1:07:05 PM [wfd] target work buffer: 345600.00 + 0.00 sec
45 4/12/2013 1:07:05 PM [wfd] CPU: shortfall 994090.56 nidle 0.00 saturated 9450.33 busy 0.00 RS fetchable 0.00 runnable 100.00
46 Einstein@Home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks)
47 SETI@home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
48 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: shortfall 333557.59 nidle 0.00 saturated 12009.79 busy 0.00 RS fetchable 0.00 runnable 100.00
49 Einstein@Home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks) (blocked by prefs)
50 SETI@home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
51 Einstein@Home 4/12/2013 1:07:05 PM [wfd] overall LTD 0.00
52 SETI@home 4/12/2013 1:07:05 PM [wfd] overall LTD -236995.78
53 4/12/2013 1:07:05 PM [wfd] ------- end work fetch state -------

Have you already tried the set Use NVIDIA GPU to no and do some requests trick yet?

Why can't I do both cpu and gpu work? Is it now forbidden to do both?

And no I haven't, I don't see that as a problem.

Maybe I should just detach...

It is a known issue with BOINC. Where it will fill the GPU cache over the CPU cache. I think there was some work done server side to try and correct this, but it may only be effective with newer versions of BOINC. Once you have CPU tasks again reenable GPU fetch and then see how it goes. With the 100 task limits you might have to lower your queue settings to prevent it from doing it again.

Well I run the anonymous platform which I think is still not supported under the beta v7 or am I wrong? Seems kind of unfair to Me, it's like no v7, no cpu work...

This sucks.

Anonymous/3rd party apps work with BOINC v7. I'm not sure where you might have gotten the idea they don't.
I don't know if the issue doesn't exist when using 6.12.xx or 7.0.xx, but I have not seen anyone talking about having this issue for quite a while.
I think it is suggested you run dry before switching to BOINC v7 if you are thinking about that.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Ok I put up 2 or 3 files in 3 or 4 entries in the following thread:

Problem can't download cpu wu's, gpu's wu's are fine though

Maybe this will help?

42 4/12/2013 1:07:05 PM [wfd]: work fetch start
43 4/12/2013 1:07:05 PM [wfd] ------- start work fetch state -------
44 4/12/2013 1:07:05 PM [wfd] target work buffer: 345600.00 + 0.00 sec
45 4/12/2013 1:07:05 PM [wfd] CPU: shortfall 994090.56 nidle 0.00 saturated 9450.33 busy 0.00 RS fetchable 0.00 runnable 100.00
46 Einstein@Home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks)
47 SETI@home 4/12/2013 1:07:05 PM [wfd] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
48 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: shortfall 333557.59 nidle 0.00 saturated 12009.79 busy 0.00 RS fetchable 0.00 runnable 100.00
49 Einstein@Home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (no new tasks) (blocked by prefs)
50 SETI@home 4/12/2013 1:07:05 PM [wfd] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
51 Einstein@Home 4/12/2013 1:07:05 PM [wfd] overall LTD 0.00
52 SETI@home 4/12/2013 1:07:05 PM [wfd] overall LTD -236995.78
53 4/12/2013 1:07:05 PM [wfd] ------- end work fetch state -------

Have you already tried the set Use NVIDIA GPU to no and do some requests trick yet?

Why can't I do both cpu and gpu work? Is it now forbidden to do both?

And no I haven't, I don't see that as a problem.

Maybe I should just detach...

It is a known issue with BOINC. Where it will fill the GPU cache over the CPU cache. I think there was some work done server side to try and correct this, but it may only be effective with newer versions of BOINC. Once you have CPU tasks again reenable GPU fetch and then see how it goes. With the 100 task limits you might have to lower your queue settings to prevent it from doing it again.

Well I run the anonymous platform which I think is still not supported under the beta v7 or am I wrong? Seems kind of unfair to Me, it's like no v7, no cpu work...

This sucks.

Anonymous/3rd party apps work with BOINC v7. I'm not sure where you might have gotten the idea they don't.
I don't know if the issue doesn't exist when using 6.12.xx or 7.0.xx, but I have not seen anyone talking about having this issue for quite a while.
I think it is suggested you run dry before switching to BOINC v7 if you are thinking about that.

Which is the one of the v7 that you like to run?

And why go dry to switch?

I thought that would be if one was going from v7 to v6.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

This is the reason to at least run down your GPU work

http://setiathome.berkeley.edu/forum_thread.php?id=71160

---

Which is the one of the v7 that you like to run?

And why go dry to switch?

I thought that would be if one was going from v7 to v6.

Claggy mentioned this is one of the BOINC v7 threads.

If you don't have flops values in your app_info, you'll want to run your GPU cache down first before upgrading,
otherwise existing GPU Wu's will be on the verge of going Maximum Time Exceeded, (because of a increased internal flops value for GPU Wu's)
New GPU Wu's will get revised <rsc_fpops_est> and <rsc_fpops_bound> values.

Or Reset the project once you're upgraded (only needed to be done at projects where you run an app_info that doesn't have a flops entry).

I think v7 also changes the client_state.xml so that if you want to go back to v6 you need to be sure to back up everything before hand.

After v7.0.40 app_config.xml was added to give easier control to running multiple instead of tasks on hardware. I'm planning to switch all of my 6.12.33 machines over once there is a newer recommended version, or I might just use the 7.0.42 I have been playing with on one machine. Since there have not been a lot of messages about newer versions of BOINC having major issues I would guess it is going well.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

This is the reason to at least run down your GPU work

http://setiathome.berkeley.edu/forum_thread.php?id=71160

Nice, but I don't supply a flops value, haven't for more than 6 months to 1 year in fact.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

This is the reason to at least run down your GPU work

http://setiathome.berkeley.edu/forum_thread.php?id=71160

It's only GPU work that is effected, so you only need to run your Cache down of GPU work.

Claggy

This is the reason to at least run down your GPU work

http://setiathome.berkeley.edu/forum_thread.php?id=71160

Nice, but I don't supply a flops value, haven't for more than 6 months to 1 year in fact.

Which means you WILL need to run down you GPU cache

---

Which is the one of the v7 that you like to run?

And why go dry to switch?

I thought that would be if one was going from v7 to v6.

Claggy mentioned this is one of the BOINC v7 threads.

If you don't have flops values in your app_info, you'll want to run your GPU cache down first before upgrading,
otherwise existing GPU Wu's will be on the verge of going Maximum Time Exceeded, (because of a increased internal flops value for GPU Wu's)
New GPU Wu's will get revised <rsc_fpops_est> and <rsc_fpops_bound> values.

Or Reset the project once you're upgraded (only needed to be done at projects where you run an app_info that doesn't have a flops entry).

I think v7 also changes the client_state.xml so that if you want to go back to v6 you need to be sure to back up everything before hand.

After v7.0.40 app_config.xml was added to give easier control to running multiple instead of tasks on hardware. I'm planning to switch all of my 6.12.33 machines over once there is a newer recommended version, or I might just use the 7.0.42 I have been playing with on one machine. Since there have not been a lot of messages about newer versions of BOINC having major issues I would guess it is going well.

I just downloaded 7.0.61 and no I've not installed that yet. So since I have no flops value which I've read wasn't a good idea, is now recommended practice?

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

This is the reason to at least run down your GPU work

http://setiathome.berkeley.edu/forum_thread.php?id=71160

Nice, but I don't supply a flops value, haven't for more than 6 months to 1 year in fact.

Which means you WILL need to run down you GPU cache

Well I can't see a way to run down the gpu work by themselves, all I can do is run both down to where I run out of gpu work and report all the gpu work after uploading them.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

This is the reason to at least run down your GPU work

http://setiathome.berkeley.edu/forum_thread.php?id=71160

Nice, but I don't supply a flops value, haven't for more than 6 months to 1 year in fact.

Which means you WILL need to run down you GPU cache

Lovely...

2:40:40(hh:mm:ss)...

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's