Re: [Starpu-devel] Assert fail with 8659

[Sylvain HENRY <sylvain.henry@inria.fr>]

Hi,

Andra has the same bug so the problem is more likely in StarPU.

Cheers
Sylvain

Le 15/02/2013 09:54, Xavier Lacoste a écrit :

Hello,

I still have the assert() problem with my code on mirage001.
I'll check in my code that I really give correct inputs to StarPU, the error can come from one of my changes...

I runned make check :

1 of 113 tests failed
(2 tests were not run)

If I understood well this is the one which failed :
[starpu][starpu_init] Warning: StarPU was configured with --with-fxt, which slows down a bit
[starpu][initialize_eager_center_policy] Warning: you are running the default eager scheduler, which is not very smart. Make sure to read the StarPU documentation about adding perfo
rmance models in order to be able to use the dmda scheduler instead.
[starpu][starpu_init] Warning: StarPU was configured with --with-fxt, which slows down a bit
Warning: change output file name to /tmp/prof_file_lacoste_0, but some events have been saved in file /tmp/prof_file_lacoste_0
[starpu][initialize_eager_center_policy] Warning: you are running the default eager scheduler, which is not very smart. Make sure to read the StarPU documentation about adding perfo
rmance models in order to be able to use the dmda scheduler instead.
[starpu][starpu_init] Warning: StarPU was configured with --with-fxt, which slows down a bit
Warning: change output file name to /tmp/prof_file_lacoste_0, but some events have been saved in file /tmp/prof_file_lacoste_0
[starpu][initialize_eager_center_policy] Warning: you are running the default eager scheduler, which is not very smart. Make sure to read the StarPU documentation about adding perfo
rmance models in order to be able to use the dmda scheduler instead.
All CUDA-capable devices are busy or unavailable
oops in init_context (drivers/cuda/driver_cuda.c:240)... 29: unload of CUDA runtime failed
oops in init_context (drivers/cuda/driver_cuda.c:240)... 29: unload of CUDA runtime failed
[starpu][abort] drivers/cuda/driver_cuda.c:582 starpu_cuda_report_error
[starpu][abort] drivers/cuda/driver_cuda.c:582 starpu_cuda_report_error
[error] `./main/restart' killed with signal 6; test marked as failed
while looking for core file of ./main/restart: core: No such file or directory
#Execution_time_in_seconds 5.340971 ./main/restart
FAIL: main/restart

XL.


Le 14 févr. 2013 à 20:44, Nathalie Furmento a écrit :

I was not able to reproduce it running make check on StarPU on my laptop. If the problem is still there Xavier, please send us the output of config.log, and the configuration of your machine (namely which machine you are using on plafrim).

Cheers,

Nathalie

On Feb 14, 20:29, Samuel Thibault wrote:

Xavier Lacoste, le Thu 14 Feb 2013 18:07:31 +0100, a écrit :

The compilation passed with this configure line :

./configure --prefix=/home/lacoste/starpu-trunk-cuda --with-fxt --enable-maxcpus=160 --enable-max-sched-ctxs=30 CC=gcc CXX=g++ F77=gfortran --disable-opencl --with-cuda-dir=/opt/cluster/gpu/cuda/latest --with-cuda-lib-dir=/opt/cluster/gpu/cuda/latest/lib64/

And is the assertion failure gone away?

Samuel

_______________________________________________
Starpu-devel mailing list
Starpu-devel@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/starpu-devel