Msieve 1.53 feedback
 

Hitting problems with polynomial finding on a Tesla C1060 (cc=1.3) with msieve 1.53.SVN 967. The card has 2GB of memory and appears to work reliably on other tasks.

The search crashes after a period somewhere between seconds and days with the message "error (line 734): unexpected error". It is not clear which line 734 is appropriate but in stage1_sieve_gpu.c it reads "CUDA_TRY(cuEventSynchronize(t->end_event))"

This is a 64-bit Gentoo machine with driver 337.25. All other installed software is current as of a couple of days ago.

Another system with a GTX 460 (cc=2.1) but otherwise identical appears to work reliably as long as it is given the gpu_mem_mb=384 parameter because it only has 512M memory and msieve seems to want to grab all of it if given the chance.

A more elderly 64-bit Windoze version has run for many weeks (over several sessions of course) without any issues whatsoever.

Paul

Having a small issue as well--compiling in VS2012 without GMP-ECM and with CUDA. I get an unresolved external symbol mul_mod_64. The only reference to it I can find is from an asm file. What am I forgetting?

Compiling with MPIR 2.7.0 and CUDA 6.0 (CC 2.0).

Thanks!

[QUOTE=wombatman;379658]Having a small issue as well--compiling in VS2012 without GMP-ECM and with CUDA. I get an unresolved external symbol mul_mod_64. The only reference to it I can find is from an asm file. What am I forgetting?

Compiling with MPIR 2.7.0 and CUDA 6.0 (CC 2.0).

Thanks![/QUOTE]

This symbol comes from the file x64_support_masm.asm and is a part of the Windows x64 build. It is included in the Visual Studio as a part of the gnfs/poly sub-project. It requires MASM, the Microsoft assembler.

Brian

I'm leaving GMP-ECM out completely by removing the .props file. The mul_mod_64 thing (per a quick and dirty googling) used to be able to be found in an asm: [url]https://github.com/radii/msieve/blob/master/build.vc9/x64_support.asm[/url]

I'm guessing that's not where it is anymore? The error is from gnfs.lib (relation.obj), but I can't find mul_mod_64 in it.

[QUOTE=wombatman;379697]I'm leaving GMP-ECM out completely by removing the .props file. The mul_mod_64 thing (per a quick and dirty googling) used to be able to be found in an asm: [url]https://github.com/radii/msieve/blob/master/build.vc9/x64_support.asm[/url]

I'm guessing that's not where it is anymore? The error is from gnfs.lib (relation.obj), but I can't find mul_mod_64 in it.[/QUOTE]

Sorry - I updated my earlier comment, which was wrong.

Thanks. That did get it to compile without issue. On running it, however, I get the following (running a quick test to make I could do the poly search):

[CODE][c:\dorkdom\svn_checkout\msieve-code\trunk\b40c\b40c\radix_sort\../radix_sort/tex_ref.cuh, 71] cudaBindTexture failed (CUDA error 20: invalid channel descriptor)
[C:/Dorkdom/SVN_Checkout/msieve-code/trunk/b40c/sort_engine.cu, 95] sort engine: (CUDA error 20: invalid channel descriptor)[/CODE]

Compilation is with CUDA 6.0.

How odd. Rebuilding with CUDA 5.5 and it works fine now, at least for poly selection. I know MSieve isn't really being actively worked on, but this seems to be a bug of some kind?

:max::max::max::max::max::max::max::max:

This is me with a CUDA-enabled 64-bit version of MSieve for Windows that can handle the large data sets. Thanks again for your help!

I don't have 6.0 right now; the 5.0 toolkit required some makefile fixes (its windows environment variables did not have an ending slash like previous versions did) but otherwise it worked out of the box.

Wombatman, am I correct that your post above means you got it working?

I did indeed (they were celebratory emoticons). Only with CUDA 5.5 though. Compiling with 6.0 gave the error I posted previously. If I can provide any more information to try and nail down what causes it, please let me know.

[QUOTE=wombatman;379726]:max::max::max::max::max::max::max::max:

This is me with a CUDA-enabled 64-bit version of MSieve for Windows that can handle the large data sets. Thanks again for your help![/QUOTE]

Are you going to make it available generally, so that we can all enjoy the fruits of your labours? :banana::banana::banana::banana::banana::banana: