I have been getting the same sort of errors within seconds of starting execution, both on 3.07 and 3.10:
[10:31:00][9612][ERROR] Error creating CUDA FFT plan (error code: 2)
[10:31:00][9612][ERROR] Demodulation failed (error: 3)!
called boinc_finish
Am I missing something really obvious? The host runs SETI CUDA WUs okay. I am not complaining, just reporting - I know improvements can't be made without reports from testers.
Sorry, not enough memory.
Our final release (scheduler instead of app_info.xml) will contain proper checks that no WU is shipped to you unless your system meets all hardware requirements. FYI, this error is typically caused by on-board devices and/or when your device's global memory is still loaded with (e.g.) textures left by previous 3D apps...
I've found how to run 4 S5R5 tasks while working on ABP1 on CUDA device.
It's simple. Just freeze all the ABP tasks, then restart BOINC. And after that unfreeze one of ABP tasks and have fun ;)
It seems to run smoothly (but before that I killed some WU's with old driver). Will keep eye on it and report after a while.
Thanks Stranger,
It's simple and it's works fine. That I didn't find this myself...
Our final release (scheduler instead of app_info.xml) will contain proper checks that no WU is shipped to you unless your system meets all hardware requirements. FYI, this error is typically caused by on-board devices and/or when your device's global memory is still loaded with (e.g.) textures left by previous 3D apps...
Thank you for taking the time to answer, this explanation is really helpful.
I just wish BOINC wouldn't try to keep asking for GPU work on Einstein, though. The server keeps telling me to remove the app_info.xml, but I'm using the 3.09 ABP beta application since it appears to be show a speed improvement over the current 3.08 release, and it's taking a long time for BOINC to ask for CPU work instead (since there's a four-hour delay after each GPU work request).
I just wish BOINC wouldn't try to keep asking for GPU work on Einstein, though. The server keeps telling me to remove the app_info.xml, but I'm using the 3.09 ABP beta application since it appears to be show a speed improvement over the current 3.08 release, and it's taking a long time for BOINC to ask for CPU work instead (since there's a four-hour delay after each GPU work request).
It is simple. You should increase your WU buffer by changing time interval for which you want BOINC to keep up running and after next connection to server you should start slowly decreasing this buffer to an apropriate value. It is in BOINC settings - Client configuration - Network settings.
Ugh, really? I don't like keeping huge buffers. Unlike some other people, I don't like hogging WUs by having a 10 day cache. ):
Well, I'll keep it in mind for next time, then.
givin the recent streek of downtime i dont think anyone would mind it. i personally used to keep a 1 day cache. untill the intermitant downtimes. now i keep a 7 day cache "just in case"
and no, i dont blame anyone at the project for the downtime. stuff happens.
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
I rarely visit some machines and have to set cache to 10 days and more in case of server failure. Of cause I don't use unstable machines for this.
But for fast machines near me I use a smaller cache - it is easier to change something or even reinstall BOINC if needed without loss of data.
I have been getting the same sort of errors within seconds of starting execution, both on 3.07 and 3.10:
[10:31:00][9612][ERROR] Error creating CUDA FFT plan (error code: 2)
[10:31:00][9612][ERROR] Demodulation failed (error: 3)!
called boinc_finish
Am I missing something really obvious? The host runs SETI CUDA WUs okay. I am not complaining, just reporting - I know improvements can't be made without reports from testers.
Sorry, not enough memory.
Our final release (scheduler instead of app_info.xml) will contain proper checks that no WU is shipped to you unless your system meets all hardware requirements. FYI, this error is typically caused by on-board devices and/or when your device's global memory is still loaded with (e.g.) textures left by previous 3D apps...
Cheers,
Oliver
Hi Oliver
I wonder if you someone would be kind enough to state what the system requirements are which are planned to go into the scheduler. I just wasted a few hours getting setup to "Play" with the Beta on my 8400GS to get the same error on 2 WU's
I have been getting the same sort of errors within seconds of starting execution, both on 3.07 and 3.10:
[10:31:00][9612][ERROR] Error creating CUDA FFT plan (error code: 2)
[10:31:00][9612][ERROR] Demodulation failed (error: 3)!
called boinc_finish
Am I missing something really obvious? The host runs SETI CUDA WUs okay. I am not complaining, just reporting - I know improvements can't be made without reports from testers.
Sorry, not enough memory.
Our final release (scheduler instead of app_info.xml) will contain proper checks that no WU is shipped to you unless your system meets all hardware requirements. FYI, this error is typically caused by on-board devices and/or when your device's global memory is still loaded with (e.g.) textures left by previous 3D apps...
Cheers,
Oliver
Hi Oliver
I wonder if you someone would be kind enough to state what the system requirements are which are planned to go into the scheduler. I just wasted a few hours getting setup to "Play" with the Beta on my 8400GS to get the same error on 2 WU's
Regards
I don't suppose my 128Mb 8400M GS will work eithier then?, is there a CPU fallback mode? :D
My first WU just completed in 9 hours with no problems.
The power draw of my PC whilst crunching this unit is around 160 Watts, as opposed to around 200 Watts when crunching CUDA SETI or GPUGRID units.
System info:
Windows Vista Home Premium SP1 64-bit
BOINC version 6.6.36
NVIDIA driver version 190.38
GeForce GTX 280
AMD Athlon 64 3200+
4GB RAM
Hi Wedge009, RE: I
)
Hi Wedge009,
Sorry, not enough memory.
Our final release (scheduler instead of app_info.xml) will contain proper checks that no WU is shipped to you unless your system meets all hardware requirements. FYI, this error is typically caused by on-board devices and/or when your device's global memory is still loaded with (e.g.) textures left by previous 3D apps...
Cheers,
Oliver
Einstein@Home Project
RE: I've found how to run 4
)
Thanks Stranger,
It's simple and it's works fine. That I didn't find this myself...
Greetings from
TJ
RE: Sorry, not enough
)
Thank you for taking the time to answer, this explanation is really helpful.
I just wish BOINC wouldn't try to keep asking for GPU work on Einstein, though. The server keeps telling me to remove the app_info.xml, but I'm using the 3.09 ABP beta application since it appears to be show a speed improvement over the current 3.08 release, and it's taking a long time for BOINC to ask for CPU work instead (since there's a four-hour delay after each GPU work request).
Soli Deo Gloria
RE: I just wish BOINC
)
It is simple. You should increase your WU buffer by changing time interval for which you want BOINC to keep up running and after next connection to server you should start slowly decreasing this buffer to an apropriate value. It is in BOINC settings - Client configuration - Network settings.
Ugh, really? I don't like
)
Ugh, really? I don't like keeping huge buffers. Unlike some other people, I don't like hogging WUs by having a 10 day cache. ):
Well, I'll keep it in mind for next time, then.
Soli Deo Gloria
RE: Ugh, really? I don't
)
givin the recent streek of downtime i dont think anyone would mind it. i personally used to keep a 1 day cache. untill the intermitant downtimes. now i keep a 7 day cache "just in case"
and no, i dont blame anyone at the project for the downtime. stuff happens.
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
I rarely visit some machines
)
I rarely visit some machines and have to set cache to 10 days and more in case of server failure. Of cause I don't use unstable machines for this.
But for fast machines near me I use a smaller cache - it is easier to change something or even reinstall BOINC if needed without loss of data.
RE: Hi Wedge009, RE: I
)
Hi Oliver
I wonder if you someone would be kind enough to state what the system requirements are which are planned to go into the scheduler. I just wasted a few hours getting setup to "Play" with the Beta on my 8400GS to get the same error on 2 WU's
Regards
RE: RE: Hi
)
I don't suppose my 128Mb 8400M GS will work eithier then?, is there a CPU fallback mode? :D
Claggy
My first WU just completed in
)
My first WU just completed in 9 hours with no problems.
The power draw of my PC whilst crunching this unit is around 160 Watts, as opposed to around 200 Watts when crunching CUDA SETI or GPUGRID units.
System info:
Windows Vista Home Premium SP1 64-bit
BOINC version 6.6.36
NVIDIA driver version 190.38
GeForce GTX 280
AMD Athlon 64 3200+
4GB RAM