Prime95 version 27.7 / 27.9

[Xyzzy]

We noticed, while setting up a few boxes, that Mprime embeds a weird "^F" character into prime.txt if you use a proxy.

We do not know if this causes any problems or anything. It is easy to delete with vim.

[Dubslow]

Hm... didn't do that for me.

[chalsall]

Originally Posted by Xyzzy

We do not know if this causes any problems or anything. It is easy to delete with vim.

I've seen that myself in the past. Don't know why. It won't cause any problems.

As an aside, it's a good thing the proxy is smart about handling the case where a user isn't known yet....

[Xyzzy]

As an aside, it's a good thing the proxy is smart about handling the case where a user isn't known yet....

We edited our username out of the image.

Would it have worked without a username? If so, that is cool!

[chalsall]

Originally Posted by Xyzzy

Would it have worked without a username? If so, that is cool!

No... The Primenet username is needed. However, the GPU72 proxy isn't supposed to be publicly known yet....

[Xyzzy]

No... The Primenet username is needed. However, the GPU72 proxy isn't supposed to be publicly known yet....

[Laurent]

Hi,

I have some specific problems with the 3200K FFT test running on my Sandy Bridge Core i7 2600K.
I think it is Hyper-threading related on Windows XP (32-bit) platform (http://www.mersenneforum.org/showthread.php?t=17036).

Memory is OK (8 GB physical tested with Memtest > 48h)
CPU temperature is OK : about 60°C running Prime with a Noctua NH-U12P SE2

Other Self-tests (other than 3200K FFT) can run for hours. 3200K test crashes within some minutes: No rounding error in Prime95 console but OS memory access error.

Running my SB 2600K with Hyper-threading enabled overclocked at 4400 or 4500MHz on Linux 64-bit gives a similar error :

/var/log/kern.log:Aug  6 21:09:47 Gigabyte-linux kernel: [ 1549.289956] mprime[2877] general protection ip:9db289 sp:7fe3f32506d0 error:0 in mprime[400000+1d0b000]
  /var/log/kern.log:Aug  6 23:32:46 Gigabyte-linux kernel: [ 4804.983166] mprime[2525] general protection ip:99c28c sp:7f342f949270 error:0 in mprime[400000+1d0b000]
  /var/log/kern.log:Aug  7 06:54:40 Gigabyte-linux kernel: [31293.049624] mprime[2857] general protection ip:99a80c sp:7f7293b296c0 error:0 in mprime[400000+1d0b000]
  /var/log/kern.log:Aug  7 22:29:36 Gigabyte-linux kernel: [  415.393643] mprime[2542] general protection ip:99c28c sp:7fe9c6edd6c0 error:0 in mprime[400000+1d0b000]

It is as if Prime95 tries to use an invalid pointer variable (memory not in process pool or invalid R/W rights).


Today I am benching Hyper-threading at 4300MHz on Linux 64-bit to see if 3200K test is stable…

[Prime95]

Originally Posted by Laurent

Other Self-tests (other than 3200K FFT) can run for hours. 3200K test crashes within some minutes:

Does it also crash if you use less memory or in-place 3200K FFTs?

[Laurent]

I mande some new tests (Sandy Bridge i7 2600K, Hyper-threading enabled) :

CPU overclocked @ 4300MHz, Linux 64-bit, Prime95 4224MB tested -> Pass (running > 11h)

CPU base clock, Windows XP 32-bit, Prime95 In-place large FFT -> Pass (running > 3h)
CPU base clock, Windows XP 32-bit, Prime95 1600MB tested -> Pass
CPU base clock, Windows XP 32-bit, Prime95 2926MB tested -> Crash after 2 min

[Xyzzy]

We noticed, while setting up a few boxes, that Mprime embeds a weird "^F" character into prime.txt if you use a proxy.

We do not know if this causes any problems or anything. It is easy to delete with vim.

FWIW, the 32-bit version of Mprime does not do this.

[Dubslow]

Multithreaded, not hyper-threaded.

[Work thread Aug 8 19:15:25] Setting affinity to run helper thread 1 on logical CPU #2
[Work thread Aug 8 19:15:25] Starting primality test of M... using AVX FFT length 2240K, Pass1=448, Pass2=5K, 2 threads
[Work thread Aug 8 19:15:25] Iteration: 2/..., ERROR: ROUND OFF (1.770880676e+21) > 0.40

It took 15 minutes to get to iteration 642 before I noticed, and the round-off never changed from the ridiculous value there. It happened more than once for each iteration, and around 1/6 of the errors gave the reproducible/not hardware message.

Linux64,Prime95,v27.7,build 2

I'll upgrade to the most recent build.