No Exponents returned for TF to Low Limits
 

I have a machine the is doing TF-LMH (low limits).

It has been attempting to get new assignments and gets the following error message back.

[CODE]No data record of requested type[/CODE]

It seems that once the TF-LMH wave front went into the 600M range it is not working anymore. The recent results report does not seem to show anything being reported for the 600M range.

Grant.

I'm having a similar problem with two machines doing TF. For the past 24 hours (maybe longer), every 70 minutes when they go to obtain a new assignment, they've been getting a "CURL library error: Operation timed out after 180 seconds with 0 bytes received".

The highest exponent each machine has is at the 581xxxxxx level, so this jibes with gjmccrac's experience.

Rodrigo

Only one person seems to be working on and/or getting assignments in the 600M/800M ranges. LingUaan.

He does NOT have them all reserved.

Note: I am not suggesting or accusing anyone of anything; just stating observations.

[QUOTE=Rodrigo;285565]I'm having a similar problem with two machines doing TF. For the past 24 hours (maybe longer), every 70 minutes when they go to obtain a new assignment, they've been getting a "CURL library error: Operation timed out after 180 seconds with 0 bytes received".

The highest exponent each machine has is at the 581xxxxxx level, so this jibes with gjmccrac's experience.

Rodrigo[/QUOTE]
I experienced something similar, once, yesterday. It worked fine an hour afterwards.
[QUOTE=gjmccrac;285544]I have a machine the is doing TF-LMH (low limits).

It has been attempting to get new assignments and gets the following error message back.

[CODE]No data record of requested type[/CODE]

It seems that once the TF-LMH wave front went into the 600M range it is not working anymore. The recent results report does not seem to show anything being reported for the 600M range.

Grant.[/QUOTE]
This is definitely something wrong on PrimeNet's end. Perhaps try manually reserving some assignments? Both in the same range and in other ranges and see if that works.

[QUOTE=Dubslow;285597]I experienced something similar, once, yesterday. It worked fine an hour afterwards.

This is definitely something wrong on PrimeNet's end. Perhaps try manually reserving some assignments? Both in the same range and in other ranges and see if that works.[/QUOTE]

I did manually assign exponents in order to fill the work queue on the machine. I believe that there is a Primenet issue with TF-LMH.

Neither TF machine is still receiving any new assignments this afternoon.

None of my systems is having problems [U]reporting[/U] results.

Rodrigo

Maybe the constant

[CODE]
#define MAX_PRIME_SSE2 596000000L /* SSE2 bit limit */
[/CODE]

Is used and shouldn't?

Anyone has an old version of Prime95 (pre SSE2) an could test if the new version introduced the problem?

Couldn't find a version pre 25. Version 25 didn't work either

[QUOTE=diamonddave;285629]Maybe the constant

[CODE]
#define MAX_PRIME_SSE2 596000000L /* SSE2 bit limit */
[/CODE]

Is used and shouldn't?

Anyone has an old version of Prime95 (pre SSE2) an could test if the new version introduced the problem?

Couldn't find a version pre 25. Version 25 didn't work either[/QUOTE]

All I could add is that when TF-LMH completed 64 bits about 16 months ago it had no problem going all the way to 999M....well actually I can't for sure recall if this higher range wasn't done manually by CHALSALL, MONST, LINDEx, et al.

[QUOTE=diamonddave;285629]Maybe the constant

[CODE]
#define MAX_PRIME_SSE2 596000000L /* SSE2 bit limit */
[/CODE]

Is used and shouldn't?

Anyone has an old version of Prime95 (pre SSE2) an could test if the new version introduced the problem?

Couldn't find a version pre 25. Version 25 didn't work either[/QUOTE]

That's the limit for FFT size, as used for P-1 and LL. TF does not use FFTs, and in fact TF by Prime95 has been done on >999M exponents (with varying to little success). Either way, that's not the issue. PrimeNet refuses to assign work, not Prime95 refuses to do work.

[QUOTE=petrw1;285634]All I could add is that when TF-LMH completed 64 bits about 16 months ago it had no problem going all the way to 999M....well actually I can't for sure recall if this higher range wasn't done manually by CHALSALL, MONST, LINDEx, et al.[/QUOTE]

I could find an old v24 version and it didn't have TF-LMH worktype

I think there is more to it...

If there was something stopping TF-LMH from handing out over 599M then it would be handing out the next bit level back at 100M.

But there are none there either.