I've just about finished one project with this new set up, took most of 4 dsys, and now I have a msg "suspended - cpu benchmarks". What is this? Is this something related to amd processors?
This project has become a poor use of my resources. My computers are spending too much time doing debugging work on the new work units, if I want to do beta testing I'll sign up for it.
Well, ya' know, this is a volunteer effort. If the computer time that I volunteer can help debug the app, that's fine with me.
I don't have a problem in debugging an app, but I'm not going to use 8 computer doing it, if an app is beta call it beta. Einstein screwed up on this one and rush the app, it isn't ready for prime time. There's a number of beta and alpha projects out there and they tell you up front the app is in testing, they failed to be up front with us here at Einstein.
I don't know how long I'll continue to do so, but I'm using using this time of trials and tribulations, alphas and betas, to add a few points to my Rosetta account. It's not nearly as picky regarding what brand of CPU I may have in use.
Gary
In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move.....Douglas Adams
I've just about finished one project with this new set up, took most of 4 dsys, and now I have a msg "suspended - cpu benchmarks". What is this? Is this something related to amd processors?
Every project gets this message, it is done by the Boinc manager and has nothing to do with the processor. Boinc has to stop (suspend) all processors in order to run the benchmarks.
I've just about finished one project with this new set up, took most of 4 dsys, and now I have a msg "suspended - cpu benchmarks". What is this? Is this something related to amd processors?
The Boinc-Client does a new benchmark every 5 days. This ist normal.
I've just about finished one project with this new set up, took most of 4 dsys, and now I have a msg "suspended - cpu benchmarks". What is this? Is this something related to amd processors?
Just normal behaviour for BOINC. Give it a few minutes to complete, and you'll be fine.
There is an inication that the SIGABRT problem still is not fixed. This host is producing errors even with the new app.
cu,
Michael
Yes Michael, looks like. My AMD host, running the 4.18 app, just got the first client error, too: http://einsteinathome.org/task/83723773. Pity about the 50k CPU secs but well, it had to happen one day. I really got lucky so far. Still, I'm somewhat surprised it happened with the new app, of all things...
There is an inication that the SIGABRT problem still is not fixed. This host is producing errors even with the new app.
cu,
Michael
Yes Michael, looks like. My AMD host, running the 4.18 app, just got the first client error, too: http://einsteinathome.org/task/83723773. Pity about the 50k CPU secs but well, it had to happen one day. I really got lucky so far. Still, I'm somewhat surprised it happened with the new app, of all things...
I'm knocking on wood as I write this, but ever since I tricked the app not to load the OpenGL lib (libGL), I haven't experienced any more "signal 11" failures on the two hosts that experienced these problems before (one other host was immune and happened not to have openGL installed in the first place).
Hmmm....why am I thinking that all my hosts will suddenly fail once I press the submit button for this post.... :-) ?
ok....I give up. I've just
)
ok....I give up.
I've just about finished one project with this new set up, took most of 4 dsys, and now I have a msg "suspended - cpu benchmarks". What is this? Is this something related to amd processors?
RE: RE: RE: This
)
I don't know how long I'll continue to do so, but I'm using using this time of trials and tribulations, alphas and betas, to add a few points to my Rosetta account. It's not nearly as picky regarding what brand of CPU I may have in use.
Gary
In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move.....Douglas Adams
RE: ok....I give up. I've
)
Every project gets this message, it is done by the Boinc manager and has nothing to do with the processor. Boinc has to stop (suspend) all processors in order to run the benchmarks.
RE: ok....I give up. I've
)
The Boinc-Client does a new benchmark every 5 days. This ist normal.
cu,
Michael
ok thanks....hanging in
)
ok thanks....hanging in there.
There is an inication that
)
There is an inication that the SIGABRT problem still is not fixed. This host is producing errors even with the new app.
cu,
Michael
RE: ok....I give up. I've
)
Just normal behaviour for BOINC. Give it a few minutes to complete, and you'll be fine.
Server status: Already done:
)
Server status: Already done: 11.403%
RE: There is an inication
)
Yes Michael, looks like. My AMD host, running the 4.18 app, just got the first client error, too: http://einsteinathome.org/task/83723773. Pity about the 50k CPU secs but well, it had to happen one day. I really got lucky so far. Still, I'm somewhat surprised it happened with the new app, of all things...
RE: RE: There is an
)
I'm knocking on wood as I write this, but ever since I tricked the app not to load the OpenGL lib (libGL), I haven't experienced any more "signal 11" failures on the two hosts that experienced these problems before (one other host was immune and happened not to have openGL installed in the first place).
Hmmm....why am I thinking that all my hosts will suddenly fail once I press the submit button for this post.... :-) ?
No risk, no fun ...