[petsc-users] mat_type MATSEQAIJCUSPARSE not recognized

Mon Jan 28 13:36:27 CST 2019

Dear Matthew,

Please find attached configure.log

On Mon, Jan 28, 2019 at 10:32 PM Matthew Knepley <knepley at gmail.com> wrote:

> Send your configure.log
>
>   Thanks,
>
>     Matt
>
> On Mon, Jan 28, 2019 at 2:05 PM Najeeb Ahmad via petsc-users <
> petsc-users at mcs.anl.gov> wrote:
>
>>
>> Dear all,
>>
>> I am trying to use PETSc with GPU. I have followed instructions laid down
>> at https://www.mcs.anl.gov/petsc/features/gpus.html. When I run my code,
>> it doesn't recognize the mat_type MATSEQAIJCUSPARSE. Here is the log:
>>
>> mpiexec -n 1 ./GMRES_PETSc -fin ../MM2PETScMatConverter/HV15R.bin
>> -ksp_monitor -pc_type ilu -pc_factor_levels 0 -ksp_gmres_restart 200
>> -ksp_gmres_preallocate -vec_type VECSEQCUDA -mat_type MATSEQAIJCUSPARSE
>> Processes: 1
>> [0]PETSC ERROR: --------------------- Error Message
>> --------------------------------------------------------------
>> [0]PETSC ERROR: Unknown type. Check for miss-spelling or missing package:
>> http://www.mcs.anl.gov/petsc/documentation/installation.html#external
>> [0]PETSC ERROR: Unknown Mat type given: MATSEQAIJCUSPARSE
>> [0]PETSC ERROR: See http://www.mcs.anl.gov/petsc/documentation/faq.html
>> for trouble shooting.
>> [0]PETSC ERROR: Petsc Development GIT revision: v3.10.3-1369-g58fe69bfc8
>> GIT Date: 2019-01-25 22:25:25 -0600
>> [0]PETSC ERROR: ./GMRES_PETSc on a arch-linux2-c-debug named
>> ip-172-31-86-226 by ubuntu Mon Jan 28 18:10:34 2019
>> [0]PETSC ERROR: Configure options --with-cc=gcc --download-mpich
>> --with-cuda=1 --with-cuda-dir=/usr/local/cuda-10.0/ --download-fblaslapack=1
>> [0]PETSC ERROR: #1 MatSetType() line 61 in
>> /home/ubuntu/petsc/src/mat/interface/matreg.c
>> [0]PETSC ERROR: #2 MatSetFromOptions() line 230 in
>> /home/ubuntu/petsc/src/mat/utils/gcreate.c
>> [0]PETSC ERROR: #3 main() line 48 in
>> /home/ubuntu/koc-aramco/src_GPU/GMRES_PETSc/main.c
>> [0]PETSC ERROR: PETSc Option Table entries:
>> [0]PETSC ERROR: -fin ../MM2PETScMatConverter/HV15R.bin
>> [0]PETSC ERROR: -ksp_gmres_preallocate
>> [0]PETSC ERROR: -ksp_gmres_restart 200
>> [0]PETSC ERROR: -ksp_monitor
>> [0]PETSC ERROR: -mat_type MATSEQAIJCUSPARSE
>> [0]PETSC ERROR: -pc_factor_levels 0
>> [0]PETSC ERROR: -pc_type ilu
>> [0]PETSC ERROR: -vec_type VECSEQCUDA
>> [0]PETSC ERROR: ----------------End of Error Message -------send entire
>> error message to petsc-maint at mcs.anl.gov----------
>> application called MPI_Abort(MPI_COMM_WORLD, 86) - process 0
>> [cli_0]: readline failed
>> [0]PETSC ERROR:
>> ------------------------------------------------------------------------
>> [0]PETSC ERROR: Caught signal number 15 Terminate: Some process (or the
>> batch system) has told this process to end
>> [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
>> [0]PETSC ERROR: or see
>> http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
>> [0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS
>> X to find memory corruption errors
>> [0]PETSC ERROR: likely location of problem given in stack below
>> [0]PETSC ERROR: ---------------------  Stack Frames
>> ------------------------------------
>> [0]PETSC ERROR: Note: The EXACT line numbers in the stack are not
>> available,
>> [0]PETSC ERROR:       INSTEAD the line number of the start of the function
>> [0]PETSC ERROR:       is given.
>> [0]PETSC ERROR: [0] PetscError line 352
>> /home/ubuntu/petsc/src/sys/error/err.c
>> [0]PETSC ERROR: [0] MatSetType line 42
>> /home/ubuntu/petsc/src/mat/interface/matreg.c
>> [0]PETSC ERROR: [0] MatSetFromOptions line 214
>> /home/ubuntu/petsc/src/mat/utils/gcreate.c
>> [0]PETSC ERROR: --------------------- Error Message
>> --------------------------------------------------------------
>> [0]PETSC ERROR: Signal received
>> [0]PETSC ERROR: See http://www.mcs.anl.gov/petsc/documentation/faq.html
>> for trouble shooting.
>> [0]PETSC ERROR: Petsc Development GIT revision: v3.10.3-1369-g58fe69bfc8
>> GIT Date: 2019-01-25 22:25:25 -0600
>> [0]PETSC ERROR: ./GMRES_PETSc on a arch-linux2-c-debug named
>> ip-172-31-86-226 by ubuntu Mon Jan 28 18:10:34 2019
>> [0]PETSC ERROR: Configure options --with-cc=gcc --download-mpich
>> --with-cuda=1 --with-cuda-dir=/usr/local/cuda-10.0/ --download-fblaslapack=1
>> [0]PETSC ERROR: #4 User provided function() line 0 in  unknown file
>> application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0
>> [0]PETSC ERROR:
>> ------------------------------------------------------------------------
>> [0]PETSC ERROR: Caught signal number 13 Broken Pipe: Likely while reading
>> or writing to a socket
>> [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
>> [0]PETSC ERROR: or see
>> http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
>> [0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS
>> X to find memory corruption errors
>> [0]PETSC ERROR: likely location of problem given in stack below
>> [0]PETSC ERROR: ---------------------  Stack Frames
>> ------------------------------------
>> [0]PETSC ERROR: Note: The EXACT line numbers in the stack are not
>> available,
>> [0]PETSC ERROR:       INSTEAD the line number of the start of the function
>> [0]PETSC ERROR:       is given.
>> [0]PETSC ERROR: [0] PetscError line 352
>> /home/ubuntu/petsc/src/sys/error/err.c
>> [0]PETSC ERROR: [0] MatSetType line 42
>> /home/ubuntu/petsc/src/mat/interface/matreg.c
>> [0]PETSC ERROR: [0] MatSetFromOptions line 214
>> /home/ubuntu/petsc/src/mat/utils/gcreate.c
>> [0]PETSC ERROR: --------------------- Error Message
>> --------------------------------------------------------------
>> [0]PETSC ERROR: Signal received
>> [0]PETSC ERROR: See http://www.mcs.anl.gov/petsc/documentation/faq.html
>> for trouble shooting.
>> [0]PETSC ERROR: Petsc Development GIT revision: v3.10.3-1369-g58fe69bfc8
>> GIT Date: 2019-01-25 22:25:25 -0600
>> [0]PETSC ERROR: ./GMRES_PETSc on a arch-linux2-c-debug named
>> ip-172-31-86-226 by ubuntu Mon Jan 28 18:10:34 2019
>> [0]PETSC ERROR: Configure options --with-cc=gcc --download-mpich
>> --with-cuda=1 --with-cuda-dir=/usr/local/cuda-10.0/ --download-fblaslapack=1
>> [0]PETSC ERROR: #5 User provided function() line 0 in  unknown file
>> application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0
>> [cli_0]: write_line error; fd=9 buf=:cmd=abort exitcode=59
>> :
>> system msg for write_line failure : Broken pipe
>>
>>
>> Any help will be greatly appreciated.
>>
>> Regards,
>>
>> --
>> *Najeeb Ahmad*
>>
>>
>> *Research and Teaching Assistant*
>> *PARallel and MultiCORE Computing Laboratory (ParCoreLab) *
>>
>> *Computer Science and Engineering*
>> *Koç University, Istanbul, Turkey*
>>
>
>
> --
> What most experimenters take for granted before they begin their
> experiments is infinitely more interesting than any results to which their
> experiments lead.
> -- Norbert Wiener
>
> https://www.cse.buffalo.edu/~knepley/
> <http://www.cse.buffalo.edu/~knepley/>
>

-- 
*Najeeb Ahmad*

*Research and Teaching Assistant*
*PARallel and MultiCORE Computing Laboratory (ParCoreLab) *

*Computer Science and Engineering*
*Koç University, Istanbul, Turkey*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20190128/c4e0340f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: configure.log
Type: text/x-log
Size: 9204425 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20190128/c4e0340f/attachment-0001.bin>