mfaktc: a CUDA program for Mersenne prefactoring - Page 145

flashjh · 2012-02-07, 00:27

Has anyone else noticed mfaktc locked up lately? My instances look like they're running and the CPU usage stays @ 100%, but they are not progressing. I just updated to a newer beta driver to see if the old driver was causing the problem, but I was curious if anyone has seen this?

Jerry

Dubslow · 2012-02-07, 00:48

I've experienced this from time to time since I first installed it however many months ago (it was at 0.17 at the time, I think) and I've had it where it just stops. Nothing appears wrong, except that nothing is output. When this happened in version 0.18, pressing ^C did nothing, because the current class never finished.

However, this happens rarely enough that it caused no problems. I think this only happens in Windows, but that could easily be wrong.

Chuck · 2012-02-07, 00:50

Quote:

Originally Posted by flashjh

Has anyone else noticed mfaktc locked up lately? My instances look like they're running and the CPU usage stays @ 100%, but they are not progressing. I just updated to a newer beta driver to see if the old driver was causing the problem, but I was curious if anyone has seen this?

Jerry

Nvidia 285.62 has been working fine for me since Oct 2011; I updated to the mfaktc compiled with CUDA 4.10 and my two instances of mfaktc have continued to run without incident.

Chuck

flashjh · 2012-02-07, 01:02

Quote:

Originally Posted by Dubslow

I've experienced this from time to time since I first installed it however many months ago (it was at 0.17 at the time, I think) and I've had it where it just stops. Nothing appears wrong, except that nothing is output. When this happened in version 0.18, pressing ^C did nothing, because the current class never finished.

However, this happens rarely enough that it caused no problems. I think this only happens in Windows, but that could easily be wrong.

Yes, this is exactly what I'm talking about... normally I wouldn't have mentioned it, but it's been happening several times a day lately. Since I have to *work*, I don't get a chance to fix it for several hours, which is a lot of lost TFing.

Quote:

Originally Posted by Chuck

Nvidia 285.62 has been working fine for me since Oct 2011; I updated to the mfaktc compiled with CUDA 4.10 and my two instances of mfaktc have continued to run without incident.

Chuck

I'm on 295.51 since just a bit ago. If the lockup occurs again, I'll revert to 285.62 and see if that fixes it.

Thanks

James Heinrich · 2012-02-07, 02:53

Quote:

Originally Posted by Chuck

Nvidia 285.62 has been working fine for me

Same here.

kladner · 2012-02-07, 05:12

I'm running 290.53 and mfaktc 0.18 (compiled with CUDA 4.10), and have not noticed any problems.

Radikalinsky · 2012-02-09, 00:23

Quote:

Originally Posted by flashjh

Has anyone else noticed mfaktc locked up lately? My instances look like they're running and the CPU usage stays @ 100%, but they are not progressing. I just updated to a newer beta driver to see if the old driver was causing the problem, but I was curious if anyone has seen this?

Jerry

I had this effect on two systems since about half a year, with different versions of mfaktc and NVidia drivers, but only with overclocked GPU and during some other activity (internet browsing). The GPU is probably overloaded and protects itself by a reset to a very slow clock speed, und mfaktc hangs completely, consuming 0 % of the GPU. Also the CPU consumption of mfaktc goes down to 0 %. This happens because I set AllowSleep=1 in the ini file, which works fine and saves some power and noise.

Rad

Dubslow · 2012-02-09, 02:24

Okay, i think them the only reason it crashed only in Windows is because in Windows I do overclock it, however I've never noticed instability except for this problem. While in the testing process for the OC, when it crashed, it crashed hard and Windows would complain about the video driver and that it had been restarted and the clock speed reset to stock (factory OC). no such thing occurred whenever mfaktc hanged. I also did not notice my cpu usage drop, although I don't have allow sleep enabled.

Batalov · 2012-02-09, 02:59

Did you test the stability of OC with, say, EVGA OC Scanner? (absense of artifacts in Furry and Tessy tests)

flashjh · 2012-02-09, 05:01

Thanks for all the replies. I downgraded to 285.62 and all seems to be fine now. Been running for a couple of days non-stop.

TheJudger · 2012-02-12, 00:27

I've just updated my box from openSUSE 11.1 (gcc 4.3.x) to openSUSE 12.1 (gcc 4.6.x).
The reason why I didn't update my machine earlier was the fact that CUDA officiall supports only gcc up to 4.4.

I did the upgrade now because openSUSE 11.1 doesn't support AVX (e.g. Sandy Bridge).
So I've installed openSUSE 12.1 with gcc 4.6 and gcc 4.3 (packages from openSUSE 11.2 repo), setting gcc 4.3 to the default compiler (using the alternatives framework).
Now I can compile and run mfaktc on openSUSE 12.1.

Now the interesting part: I've compiled all mfaktc source files with gcc 4.3 expect the sieve code (sieve.c). For sieve.c I've used gcc 4.6. Result: 20% faster sieving (SievePrimes=5000). This needs further testing but it looks promising.

Yes, no code changes, just an updated compiler!

Oliver

2012-02-07, 05:12	#1590
kladner "Kieren" Jul 2011 In My Own Galaxy! 2×3×1,693 Posts	I'm running 290.53 and mfaktc 0.18 (compiled with CUDA 4.10), and have not noticed any problems. Last fiddled with by kladner on 2012-02-07 at 05:13

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
mfakto: an OpenCL program for Mersenne prefactoring	Bdot	GPU Computing	1676	2021-06-30 21:23
The P-1 factoring CUDA program	firejuggler	GPU Computing	753	2020-12-12 18:07
gr-mfaktc: a CUDA program for generalized repunits prefactoring	MrRepunit	GPU Computing	32	2020-11-11 19:56
mfaktc 0.21 - CUDA runtime wrong	keisentraut	Software	2	2020-08-18 07:03
World's second-dumbest CUDA program	fivemack	Programming	112	2015-02-12 22:51

2012-02-07, 00:27	#1585
flashjh "Jerry" Nov 2011 Vancouver, WA 1,123 Posts	Has anyone else noticed mfaktc locked up lately? My instances look like they're running and the CPU usage stays @ 100%, but they are not progressing. I just updated to a newer beta driver to see if the old driver was causing the problem, but I was curious if anyone has seen this? Jerry

2012-02-07, 00:48	#1586
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 16065₈ Posts	I've experienced this from time to time since I first installed it however many months ago (it was at 0.17 at the time, I think) and I've had it where it just stops. Nothing appears wrong, except that nothing is output. When this happened in version 0.18, pressing ^C did nothing, because the current class never finished. However, this happens rarely enough that it caused no problems. I think this only happens in Windows, but that could easily be wrong.

2012-02-09, 02:24	#1592
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 7221₁₀ Posts	Okay, i think them the only reason it crashed only in Windows is because in Windows I do overclock it, however I've never noticed instability except for this problem. While in the testing process for the OC, when it crashed, it crashed hard and Windows would complain about the video driver and that it had been restarted and the clock speed reset to stock (factory OC). no such thing occurred whenever mfaktc hanged. I also did not notice my cpu usage drop, although I don't have allow sleep enabled.

2012-02-09, 02:59	#1593
Batalov "Serge" Mar 2008 Phi(4,2^7658614+1)/2 2516₁₆ Posts	Did you test the stability of OC with, say, EVGA OC Scanner? (absense of artifacts in Furry and Tessy tests)

2012-02-09, 05:01	#1594
flashjh "Jerry" Nov 2011 Vancouver, WA 1,123 Posts	Thanks for all the replies. I downgraded to 285.62 and all seems to be fine now. Been running for a couple of days non-stop.

2012-02-12, 00:27	#1595
TheJudger "Oliver" Mar 2005 Germany 11×101 Posts	I've just updated my box from openSUSE 11.1 (gcc 4.3.x) to openSUSE 12.1 (gcc 4.6.x). The reason why I didn't update my machine earlier was the fact that CUDA officiall supports only gcc up to 4.4. I did the upgrade now because openSUSE 11.1 doesn't support AVX (e.g. Sandy Bridge). So I've installed openSUSE 12.1 with gcc 4.6 and gcc 4.3 (packages from openSUSE 11.2 repo), setting gcc 4.3 to the default compiler (using the alternatives framework). Now I can compile and run mfaktc on openSUSE 12.1. Now the interesting part: I've compiled all mfaktc source files with gcc 4.3 expect the sieve code (sieve.c). For sieve.c I've used gcc 4.6. Result: 20% faster sieving (SievePrimes=5000). This needs further testing but it looks promising. Yes, no code changes, just an updated compiler! Oliver