On installing my GTX 480 a couple of weeks back I noticed errors too.
test_math.py works fine
test_gpuarray.py has soft errors - it looks like the precision of some
of the results breaks the assertions
test_driver.py has hard erros - the equivalent of a seg fault followed
by instability for me requiring a reboot.
I'm using WinXP SP3 32 bit, CUDA 3.1, the latest WHQL drivers (257.21)
last week and the latest beta (258.96) this week. My pyCUDA is latest
as of yesterday.
With a GT220 (9th generation) and 9800GT (8th generation) with CUDA
3.1 I don't see these problems.
I confess I've ignored them so far so I could push on with my client's
problems. I had awful instability issues a few weeks back, I think
whenever I hit memory badly (e.g. sending a double but receiving a
float) then the system with a GTX 480 becomes very unstable, it locks
up a few minutes later requiring a hard reset.
For me all the CUDA demos work fine and the pyCUDA examples are fine
(I've been using my mandelbrot.py [see wiki] as the main testing point
as I'm using complex<double> for my physics code).
This is an example of the error I see in test_driver.py that leads to
a locked system:
----
c:\python26\lib\site-packages\pycuda-0.94rc-py2.6-win32.egg\pycuda\tools.py:217:
RuntimeError
==================================== 18 failed in 0.61 seconds
====================================
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File "c:\python26\lib\atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
LogicError: cuCtxPopCurrent failed: invalid context
Error in sys.exitfunc:
Traceback (most recent call last):
File "c:\python26\lib\atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
pycuda._driver.LogicError: cuCtxPopCurrent failed: invalid context
-------------------------------------------------------------------
PyCUDA ERROR: The context stack was not empty upon module cleanup.
-------------------------------------------------------------------
A context was still active when the context stack was being
cleaned up. At this point in our execution, CUDA may already
have been deinitialized, so there is no way we can finish
cleanly. The program will be aborted now.
Use Context.pop() to avoid this problem.
----
i.
On 14 July 2010 20:17, Julien Cornebise <[email protected]> wrote:
> Thank you very much for the suggestion.
> However, I am using drivers 256.35, with which CUDA 3.1 seems to work
> fine: all of the tests coming with the Toolktit runs flawlessly, both
> those based on CudaRT and those based on driver-mode, as well as the
> test_math.py pyCuda test.
> Any other idea please ?
>
> Julien
>
>
> On Wed, Jul 14, 2010 at 2:58 PM, Tomasz Rybak <[email protected]> wrote:
>> Dnia 2010-07-13, wto o godzinie 11:22 -0400, Julien Cornebise pisze:
>>> Dear all,
>>> I have been trying with pycuda 0.94rc (instead of latest GIT commit),
>>> and the problem stays the same :( And correction: I'm using python
>>> 2.6.4 (not 2.6.5)
>>> Would anybody have an idea, please ? Any help much appreciated !
>>> Thanks
>>>
>>
>> Which version of drivers are you using?
>> I have noticed on Debian that when I am on drivers
>> 195.36.24, CUDA 3.1 does not work, returning library errors.
>> I had to go back to CUDA toolkit 3.0 to get working programs.
>>
>> Maybe this is your problem?
>>
>> Regards.
>>
>> --
>> Tomasz Rybak <[email protected]> GPG/PGP key ID: 2AD5 9860
>> Fingerprint A481 824E 7DD3 9C0E C40A 488E C654 FB33 2AD5 9860
>> http://member.acm.org/~tomaszrybak
>>
>
> _______________________________________________
> PyCUDA mailing list
> [email protected]
> http://lists.tiker.net/listinfo/pycuda
>
--
Ian Ozsvald (A.I. researcher, screencaster)
[email protected]
http://IanOzsvald.com
http://MorConsulting.com/
http://blog.AICookbook.com/
http://TheScreencastingHandbook.com
http://FivePoundApp.com/
http://twitter.com/IanOzsvald
_______________________________________________
PyCUDA mailing list
[email protected]
http://lists.tiker.net/listinfo/pycuda
