mersenneforum.org  

Go Back   mersenneforum.org > Great Internet Mersenne Prime Search > Hardware > GPU Computing

Reply
 
Thread Tools
Old 2014-07-20, 19:34   #1
patrik
 
patrik's Avatar
 
"Patrik Johansson"
Aug 2002
Uppsala, Sweden

52×17 Posts
Default CUDALucas writing binary data to screen

I had a disc crash a few months ago and had to install CUDA again. The old SuSE repositories were gone, so I had to do it in another way (don't remember--I did it in April--probably some .run file), but I didn't get CUDALucas to work, and left it off.

A few days ago--on vacation--I gave it another try, logged in remotely to my linux computer at home, and everything worked. Today I got home, and as soon as I tried to move the mouse, CUDALucas crashed (terminated with an error). Trying to restart it, I can see it write binary data to the screen, which gets updated. But as soon as I do "tail -f log.txt" (of the file to which the output is redirected) it stops again.

Is it a driver (or driver configuration) problem? Or is it a CUDALucas configuration problem? Or is it a bug? How can I check what settings I have for whatever can be configured?

I have an ASUS GTX 560 DirectCU 1 GB and I am using CUDALucas-2.05-Beta-r64-Linux-x86-64.

Last fiddled with by patrik on 2014-07-20 at 19:36 Reason: Tried to change "data" in the title to "binary data", without success.
patrik is offline   Reply With Quote
Old 2014-07-20, 20:19   #2
owftheevil
 
owftheevil's Avatar
 
"Carl Darby"
Oct 2012
Spring Mountains, Nevada

31510 Posts
Default

That's wierd. What error did it terminate with?
owftheevil is offline   Reply With Quote
Old 2014-07-20, 21:46   #3
patrik
 
patrik's Avatar
 
"Patrik Johansson"
Aug 2002
Uppsala, Sweden

52×17 Posts
Default

Let me first say that even when it has been working (these last days), it starts with the following error messages. Then it continued until I moved the mouse.

Code:
Warning: Couldn't parse ini file option ResultsFile; using default "results.txt"
Warning: Couldn't parse ini file option OutputString; using default "0"
Warning: Couldn't parse ini file option OutputHeader; using default "0"
/usr/bin/nvidia-modprobe: unrecognized option: "-u"

ERROR: Invalid commandline, please run `/usr/bin/nvidia-modprobe --help`
       for usage information.


Using threads: square 256, splice 128.
Starting M55144241 fft length = 3024K
Iteration 10000 / 55144241, 0x789ad7cfbf93e625, 3024K, CUDALucas v2.05 Beta, error = 0.14844, real: 1:47, 10.6609 ms/iter, ETA: 163:16:20,  0.02%
Iteration 20000 / 55144241, 0x7e41a26ca6eb8d6e, 3024K, CUDALucas v2.05 Beta, error = 0.14844, real: 1:47, 10.6685 ms/iter, ETA: 163:18:03,  0.04%
I probably tried to start the program again a few times here. (I can't see where/when I gave the commands.)

Code:
Iteration 10800000 / 55144241, 0xf718a0b9aeaf1635, 3024K, CUDALucas v2.05 Beta, error = 0.15234, real: 1:47, 10.6738 ms/iter, ETA: 131:24:04, 19.59%
Iteration 10810000 / 55144241, 0x4190ceb38802dfca, 3024K, CUDALucas v2.05 Beta, error = 0.13867, real: 1:47, 10.6724 ms/iter, ETA: 131:22:17, 19.60%
CUDALucas.cu(1885) : cudaDeviceSynchronize() Runtime API error 30: unknown error.
Resetting device and restarting from last checkpoint.

CUDALucas.cu(1187) : cufftSafeCall() CUFFT error 9999: CUFFT Unknown error code
Using threads: square 256, splice 128.
Warning: Couldn't parse ini file option ResultsFile; using default "results.txt"
Warning: Couldn't parse ini file option OutputString; using default "0"
Warning: Couldn't parse ini file option OutputHeader; using default "0"
/usr/bin/nvidia-modprobe: unrecognized option: "-u"

ERROR: Invalid commandline, please run `/usr/bin/nvidia-modprobe --help`
       for usage information.


Using threads: square 256, splice 128.

Continuing M55144241 @ iteration 10810001 with fft length 3024K, 19.60% done

CUDALucas.cu(1885) : cudaDeviceSynchronize() Runtime API error 30: unknown error.
Resetting device and restarting from last checkpoint.

Using threads: square 256, splice 128.

Continuing M55144241 @ iteration 10810001 with fft length 3024K, 19.60% done

CUDALucas.cu(1885) : cudaDeviceSynchronize() Runtime API error 30: unknown error.
Resetting device and restarting from last checkpoint.

CUDALucas.cu(1187) : cufftSafeCall() CUFFT error 9999: CUFFT Unknown error code
Using threads: square 256, splice 128.
Warning: Couldn't parse ini file option ResultsFile; using default "results.txt"
Warning: Couldn't parse ini file option OutputString; using default "0"
Warning: Couldn't parse ini file option OutputHeader; using default "0"
/usr/bin/nvidia-modprobe: unrecognized option: "-u"

ERROR: Invalid commandline, please run `/usr/bin/nvidia-modprobe --help`
       for usage information.


Using threads: square 256, splice 128.

Continuing M55144241 @ iteration 10810001 with fft length 3024K, 19.60% done

CUDALucas.cu(1885) : cudaDeviceSynchronize() Runtime API error 30: unknown error.
Resetting device and restarting from last checkpoint.

Using threads: square 256, splice 128.

Continuing M55144241 @ iteration 10810001 with fft length 3024K, 19.60% done

CUDALucas.cu(1885) : cudaDeviceSynchronize() Runtime API error 30: unknown error.
Resetting device and restarting from last checkpoint.

CUDALucas.cu(1187) : cufftSafeCall() CUFFT error 9999: CUFFT Unknown error code
Using threads: square 256, splice 128.
Warning: Couldn't parse ini file option ResultsFile; using default "results.txt"
Warning: Couldn't parse ini file option OutputString; using default "0"
Warning: Couldn't parse ini file option OutputHeader; using default "0"
/usr/bin/nvidia-modprobe: unrecognized option: "-u"

ERROR: Invalid commandline, please run `/usr/bin/nvidia-modprobe --help`
       for usage information.


The backup appears to be corrupt. Restarting test.

Using threads: square 256, splice 128.

Continuing M55144241 @ iteration 10800001 with fft length 3024K, 19.59% done

Iteration 10810000 / 55144241, 0x4190ceb38802dfca, 3024K, CUDALucas v2.05 Beta, error = 0.14209, real: 1:46, 10.6676 ms/iter, ETA: 131:22:17, 19.60%
Iteration 10820000 / 55144241, 0xbc83d0a880a6282b, 3024K, CUDALucas v2.05 Beta, error = 0.15234, real: 1:47, 10.6765 ms/iter, ETA: 131:20:31, 19.62%
(The exponent is not reserved by me, but it is one of three exponents returned by anonymous users the day the possible new prime was reported. Still, perhaps the reported one is concealed in another way than just changing the residue, like it was in the v4 primenet server.)

Last fiddled with by patrik on 2014-07-20 at 21:48
patrik is offline   Reply With Quote
Old 2014-07-20, 23:56   #4
owftheevil
 
owftheevil's Avatar
 
"Carl Darby"
Oct 2012
Spring Mountains, Nevada

32×5×7 Posts
Default

It acting as if the nvidia kernel module is not loaded. The warnings are from mismatched ini files.

Last fiddled with by owftheevil on 2014-07-20 at 23:57
owftheevil is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
How does writing affect your job? jvang Homework Help 1 2018-03-11 20:32
CUDALucas: which binary to use? Karl M Johnson GPU Computing 15 2015-10-13 04:44
some short passage / some essay writing Raman Game 1 - ♚♛♝♞♜♟ - Shaolin Pirates 1 2013-03-10 11:59
Error Writing Intermediate File jinydu Lounge 6 2010-09-10 05:47
No disk writing Max Software 22 2006-10-27 21:26

All times are UTC. The time now is 23:05.


Mon Nov 29 23:05:36 UTC 2021 up 129 days, 17:34, 0 users, load averages: 1.11, 1.32, 1.33

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.