Message boards : Number crunching : HIVPR_n1 stopps and need to be manually restartet again
Author | Message |
---|---|
Hello all, | |
ID: 9847 | Rating: 0 | rate: / Reply Quote | |
I think you're reporting something new: I can't remember any post, which said that the troublesome WUs hang when BOINC switches apps (or if one finished). That may give us a clue as to why it happens and where to start searching for a solution. It also does not tolerate another second WU on the CPU (dual core), but this has been described before. Not sure what you mean. I don't like this behaviour and are going to abort those WU's in the future, as long as nobody posts a solution. Of course, noone likes this and it's not intional behaviour. Since you're running 6.4.7 don't hold your breath for a quick solution :/ MrS ____________ Scanning for our furry friends since Jan 2002 | |
ID: 9850 | Rating: 0 | rate: / Reply Quote | |
Glad if it turns out my post is of any use... not sure what you mean. Ok, here is a more precise try: Assume I am running an IBUCH job: simulataneously I can also crunch any one or two of the below mentioned projects (climateprediction, Einstein, Spinhenge and SHA1) or any combination of them. In total I am running two CPU and 1 GPU. THis does not work with the HIVPR on my machine. If I try to do this, always one CPU job gets pushed aside and is on hold. I can restart it by manually stop and restart it again. But then: HIVPR is unpredictable "on strike". There has been one or the other thread down this catgegory which I understood this way. Ahh, btw I forgot to mention: 8800GTS512 (62.92.16.00.39 - driver 6.14.11.8120) happy crunching ! abakus | |
ID: 9864 | Rating: 0 | rate: / Reply Quote | |
@abakus | |
ID: 9868 | Rating: 0 | rate: / Reply Quote | |
As I wrote, the "problem" only occurs when crunching HIV... | |
ID: 9870 | Rating: 0 | rate: / Reply Quote | |
As I wrote, the "problem" only occurs when crunching HIV... If you are running into an old bug that already has been addressed, then we can be of no help at all. There were problems with older versions and work starting and like you describe. Sadly, whatever research you could do for us on this is negated by the fact that significant changes have been made to this area of code. We think we caught most of this issue, but, if you won't upgrade BOINC to find out if that helps ... well, then you have to live with fiddling with BOINC all the time. 6.4.x had a number of issues with CUDA as these were the first versions issued to enable the capabiity. Our collective experience here at GPU Grid says that the first "good" version of BOINC that used the GPU capabilities was 6.5.0 ... now, the newly minted 6.6.28 as recommended by UCB is also recommended by some of us as having addressed a number of issues with running the GPU and CPU and keeping they loaded with work ... That does not mean that this version is bug free ... there are still significant issues that remain ... and some of us are nagging at UCB to get them addressed ... please reconsider upgrading, and if it does not help your problem we can look into it more for you ... | |
ID: 9873 | Rating: 0 | rate: / Reply Quote | |
Paul, Dieter, | |
ID: 9876 | Rating: 0 | rate: / Reply Quote | |
Paul, Dieter, No. | |
ID: 9877 | Rating: 0 | rate: / Reply Quote | |
You could dodge the problems of 6.6.28 (not sure how serious, I think long term debts are still out of whack) by testing 6.5.0 first. It doesn't have the cpu scheduling issues 6.4.x have. | |
ID: 9882 | Rating: 0 | rate: / Reply Quote | |
Message boards : Number crunching : HIVPR_n1 stopps and need to be manually restartet again