My DC mismatched - how to doublecheck?
 

Hi!



I just completed a double check that mismatched:


[URL]https://www.mersenne.org/report_exponent/?exp_lo=50866657&full=1[/URL]


The machine has been quite solid and has ECC memory, but maybe hard drives got corrupted? Or the earlier check was invalid.


How do I re-test this on another machine? I have never requested a manual assignment, is that the way to go?



Perhaps someone else could double check this number?


/Simon

Wow, that was one of mine from ages ago!

Hmm, the machine that did the first time test was very reliable and not overclocked. Interesting to see which one is correct.

You can't double check your own work, but somebody will pick that exponent up soon.

There is a thread for requesting triple checks : [url=https://www.mersenneforum.org/showthread.php?t=24148]Strategic double and triple checks (PRP's and P-1's too)[/url].

It is true that it is difficult to find :

mersenneforum.org > Great Internet Mersenne Prime Search > Data > Marin's Mersenne-aries > Strategic double and triple checks (PRP's and P-1's too)

One level up would be more logical, but its place in the folder hierarchy is historical.

Jacob

I started a triple check: [url]https://mersenne.org/M50866657[/url]

[QUOTE=jas;540211]Hi!
I just completed a double check that mismatched:
[/QUOTE]It happens. About 2% of LL tests are bad. Do another on a different exponent and see how it goes. Or do a PRP with GEC and see how many errors it detects. Some hardware can be very reliable on ordinary computing and yet not reliable enough for Mersenne primality testing. The well tuned code of a good primality test software puts extraordinary stress on the hardware. So much so that chip manufacturers use them for chip testing.

[QUOTE=ATH;540225]I started a triple check: [URL]https://mersenne.org/M50866657[/URL][/QUOTE]


Yay, thank you!



The disk is non-RAID ext4 so disk corruption may happen, however the program was never halted during the test of that number so I'm not sure how relevant disk corruption could be.


/Simon

[QUOTE=kriesel;540231]It happens. About 2% of LL tests are bad. Do another on a different exponent and see how it goes. Or do a PRP with GEC and see how many errors it detects. Some hardware can be very reliable on ordinary computing and yet not reliable enough for Mersenne primality testing. The well tuned code of a good primality test software puts extraordinary stress on the hardware. So much so that chip manufacturers use them for chip testing.[/QUOTE]


The machine has completed 12 tests before -- 2 DC, 4 LL, 4 PRP -- since I started it on february 12th. It is a Dell R620 server (not overclocked) with 2xE5-2650v1, hosted at a co-location facility with good cooling. I monitor temperature (CPU, IPMI etc) and it looks stable.


I bought the machine cheap on ebay though :) I never visually inspected the CPUs, but 'cpuid' says 'GenuineIntel' -- is that guarantee enough that it isn't a ES/QS CPU?


Let's see what the triple check says...



/Simon

Hi, just to chip in about CPU issues. The GenuineIntel doesn't matter, all CPU's are genuine. Nobody makes "counterfeit Intel CPUs", well not working ones at least. To know if it's an ES you can look at the markings on the CPU heatspreader. Though I would assume any utility capable of giving out CPU details would work also. I don't know what cat /proc/cpuinfo would say about an ES. But most likely you have a functional CPU, it just might not like the workload:


I have a Ryzen CPU running LLR that crashed with BSOD before a BIOS update. Now the same CPU just overheats the motherboard VRM's so I have to clock down the CPU. And I have another Intel CPU that gave me bad LLR residues - occasionally. I detected the error when it started to tell me that it found 10 primes almost sequentially. Of course doublechecking on another CPU found no primes. I ran LLR for Riesel primes, but the tightly optimized CPU instructions are mostly the same - they are both based on the gwnum library. Both CPUs work completely normally and without crashes otherwise.

[QUOTE=kuratkull;540239]Nobody makes "counterfeit Intel CPUs"[/QUOTE]
You seems to be pretty sure about that :razz:
We may have posted here long time ago a story from the time we were working in the far east, and not far away from our factory was an obscure 4-storied building, looking more like a villa, about which we never knew what they do, until once, when their "guilao customers" came, tested the "products", chose the best xx% of them, and scrapped the others, by burning them in a big oven. There, local people have a very good entrepreneurial skills, we have no idea what was burning in the ovens, but the following weeks they sold us 80486 processors for a very cheap price, which we used for long time, or resold back home. On them, it was printed something about genuine intel parts being made in USA....

[QUOTE=jas;540211]Hi!



I just completed a double check that mismatched:


[URL]https://www.mersenne.org/report_exponent/?exp_lo=50866657&full=1[/URL][/QUOTE]

Your result is correct: [url]https://mersenne.org/M50866657[/url]

These are the closest results (time-wise) from the bad computer:

[CODE]51167521 Amy Pond 3570K-blu 74E6AFBCA445EF__ 2013-06-11 20:31
51247087 Amy Pond 3570K-blu 080CD993FECE53__ 2013-06-24 06:38
51258113 Amy Pond 3570K-blu 22639D22B33C1E__ 2013-06-05 09:18
51415153 Amy Pond 3570K-blu 0D29D283D6D99D__ 2013-06-08 15:07
[/CODE]

In case any of these are unassigned, someone might want to grab them.