Forum > Discussion Forum

7.0.28 Boinc problems

(1/2) > >>

Fredericx51:
After upgrading to BOINC 7.0.28,  I noticed the same situation when pauzed/restarted after a
change in cmd-line settings,  running High Priority inmediatly after this.  :-\

This also happens when doing a few hundred MW WUs, taking about an hour.

Don't know if anyone noticed this too, but it looks like the very same behavior as BOINC
7.0.25 !
Not only on my ATI rig, also on 2 CUDA rigs.

Claggy:
What are your cache settings?

Claggy

Richard Haselgrove:

--- Quote from: Fredericx51 on 23 Jul 2012, 01:47:45 pm ---After upgrading to BOINC 7.0.28,  I noticed the same situation when pauzed/restarted after a
change in cmd-line settings,  running High Priority inmediatly after this.  :-\

This also happens when doing a few hundred MW WUs, taking about an hour.

Don't know if anyone noticed this too, but it looks like the very same behavior as BOINC
7.0.25 !
Not only on my ATI rig, also on 2 CUDA rigs.
--- End quote ---

Whatever your issue may be, it has nothing to do with the subject of this thread.

As of two minutes ago, dont_use_dcf was still not active at SETI main.

Richard Haselgrove:

--- Quote from: Richard Haselgrove on 23 Jul 2012, 02:42:06 pm ---Whatever your issue may be, it has nothing to do with the subject of this thread.

As of two minutes ago, dont_use_dcf was still not active at SETI main.

--- End quote ---

Er - that was when these posts were muddled up in a different thread, with a completely different title.

But to be honest, I don't think it has anything to do with BOINC v7.0.28 either (nor its successor v7.0.31)

There are rumours afoot (see SETI Main message 1263237) that graphics cards may downclock when they are close to overheating.

And a downclock, not quite severe enough to cause the tasks to fail with EXIT_TIME_LIMIT_EXCEEDED, would still boost DCF to a level where high priority running might be invoked.

Can anyone stand up this rumour with an authoritative source, please?


--- Quote from: Lee Gresham ---Oh, and the rumor I heard about the downclock was that it was caused by the 301 driver and related to card temperature. It apparently triggers the downclock at too low a temperature. After a reboot to reset it it runs fine untill the next event.
--- End quote ---

William:
Fred, what is the problem, what are the symptoms, which of your rigs do you mean and why do you think it's a BOINC problem?

Navigation

[0] Message Index

[#] Next page