<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Hao,<div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div dir="ltr" class="" style="font-family: Menlo-Regular;"><div dir="ltr" class=""><div dir="ltr" class=""><div class="">Any luck reproducing the CUDA problem?</div></div></div></div></blockquote><br class=""></div><div class="">Sorry for the long radio silence, I still have not been able to reproduce the problem unfortunately. I have tried on a local machine, and a few larger clusters and all return without errors both with and without cuda…</div><div class=""><br class=""></div><div class="">Can you try pulling the latest version of main, reconfiguring and trying again?</div><div class=""><br class=""></div><div class="">BTW, your configure arguments are a little wonky:</div><div class=""><br class=""></div><div class="">1. --with-clanguage=c - this isn’t needed, PETSc will default to C</div><div class="">2. --with-cxx-dialect=cxx14 --with-cuda-dialect=cxx14 - use <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">--with-cxx-dialect=14 instead, PETSc will detect that you have gnu compilers and enable gnu extensions</span></div><div class="">3. -with-debugging=1 - this is missing an extra dash, but you also have optimization flags set so maybe just leave this one out</div><div class=""><br class=""><div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div>Best regards,<br class=""><br class="">Jacob Faibussowitsch<br class="">(Jacob Fai - booss - oh - vitch)<br class=""></div></div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Jan 23, 2022, at 21:29, Hao DONG <<a href="mailto:dong-hao@outlook.com" class="">dong-hao@outlook.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta charset="UTF-8" class=""><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div dir="ltr" class=""><div dir="ltr" class="">Dear Jacob, <div class=""><br class=""></div><div class="">Any luck reproducing the CUDA problem? - just write to check in, in case somehow the response did not reach me (this happens to my colleagues abroad sometimes, probably due to the Wall). </div><div class=""><br class=""></div><div class="">All the best,</div><div class="">Hao<br class=""><div dir="ltr" class=""><br class=""><blockquote type="cite" class="">On Jan 19, 2022, at 3:01 PM, Hao DONG <<a href="mailto:dong-hao@outlook.com" class="">dong-hao@outlook.com</a>> wrote:<br class=""><br class=""></blockquote></div><blockquote type="cite" class=""><div dir="ltr" class=""><div class="WordSection1" style="page: WordSection1;"><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Thanks Jacob for looking into this –<span class="Apple-converted-space"> </span></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">You can see the updated source code of ex11fc in the attachment – although there is not much that I modified (except for the jabbers I outputted). I also attached the full output (ex11fc.log) along with the configure.log file. It’s an old dual Xeon workstation (one of my “production” machines) with Linux kernel 5.4.0 and gcc 9.3.</div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I simply ran the code with<span class="Apple-converted-space"> </span></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">mpiexec -np 2 ex11fc -usecuda<span class="Apple-converted-space"> </span></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">for GPU test. And as stated before, calling without the “-usecuda” option shows no errors.</div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Please let me know if you find anything wrong with the configure/code. </div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Cheers,<span class="Apple-converted-space"> </span></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Hao</div><p class="MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"></p><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif; border: none; padding: 0in;" class=""><b class="">From:<span class="Apple-converted-space"> </span></b><a href="mailto:jacob.fai@gmail.com" style="color: blue; text-decoration: underline;" class="">Jacob Faibussowitsch</a><br class=""><b class="">Sent:<span class="Apple-converted-space"> </span></b>Wednesday, January 19, 2022 3:38 AM<br class=""><b class="">To:<span class="Apple-converted-space"> </span></b><a href="mailto:dong-hao@outlook.com" style="color: blue; text-decoration: underline;" class="">Hao DONG</a><br class=""><b class="">Cc:<span class="Apple-converted-space"> </span></b><a href="mailto:junchao.zhang@gmail.com" style="color: blue; text-decoration: underline;" class="">Junchao Zhang</a>;<span class="Apple-converted-space"> </span><a href="mailto:petsc-users@mcs.anl.gov" style="color: blue; text-decoration: underline;" class="">petsc-users</a><br class=""><b class="">Subject:<span class="Apple-converted-space"> </span></b>Re: [petsc-users] Strange CUDA failure with a second petscfinalize with PETSc 3.16</div></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Apologies, forgot to mention in my previous email but can you also include a copy of the full printout of the error message that you get? It will include all the command-line flags that you ran with (if any) so I can exactly mirror your environment.<o:p class=""></o:p></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div class=""><div class=""><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">Best regards,<br class=""><br class="">Jacob Faibussowitsch<br class="">(Jacob Fai - booss - oh - vitch)<o:p class=""></o:p></span></div></div></div></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><br class=""><br class=""><o:p class=""></o:p></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">On Jan 18, 2022, at 14:06, Jacob Faibussowitsch <<a href="mailto:jacob.fai@gmail.com" style="color: blue; text-decoration: underline;" class="">jacob.fai@gmail.com</a>> wrote:<o:p class=""></o:p></div></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div class=""><div class=""><p class="MsoNormal" style="margin: 0in 0in 12pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 9pt; font-family: Menlo-Regular, serif;" class="">Can you send your updated source file as well as your configure.log (should be $PETSC_DIR/configure.log). I will see if I can reproduce the error on my end.<o:p class=""></o:p></span></p><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Menlo-Regular, serif;" class="">Best regards,<br class=""><br class="">Jacob Faibussowitsch<br class="">(Jacob Fai - booss - oh - vitch)<o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt; font-family: Menlo-Regular, serif;" class=""><br class=""><br class=""><o:p class=""></o:p></span></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class=""><p class="MsoNormal" style="margin: 0in 0in 12pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="font-size: 9pt; font-family: Menlo-Regular, serif;" class="">On Jan 17, 2022, at 23:06, Hao DONG <<a href="mailto:dong-hao@outlook.com" style="color: blue; text-decoration: underline;" class="">dong-hao@outlook.com</a>> wrote:<o:p class=""></o:p></span></p></blockquote></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 9pt;" class=""></span><span style="font-size: 9pt; font-family: Menlo-Regular, serif;" class=""><o:p class=""></o:p></span></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Dear Junchao and Jacob,<span class="apple-converted-space"> </span><o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Thanks a lot for the response – I also don’t understand why this is related to the device, especially on why the procedure can be successfully finished for *<b class="">once</b>* – As instructed, I tried to add a CHKERRA() macro after (almost) every petsc line – such as the initialization, mat assemble, ksp create, solve, mat destroy, etc. However, all other petsc commands returns with error code 0. It only gives me a similar (still not very informative) error after I call the petscfinalize (again for the second time), with error code 97: <span class="apple-converted-space"> </span><o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[0]PETSC ERROR: --------------------- Error Message --------------------------------------------------------------<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[0]PETSC ERROR: GPU error<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[0]PETSC ERROR: cuda error 709 (cudaErrorContextIsDestroyed) : context is destroyed<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[0]PETSC ERROR: See<span class="Apple-converted-space"> </span><a href="https://petsc.org/release/faq/" style="color: blue; text-decoration: underline;" class="">https://petsc.org/release/faq/</a><span class="Apple-converted-space"> </span>for trouble shooting.<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[0]PETSC ERROR: Petsc Release Version 3.16.3, unknown<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[0]PETSC ERROR: ./ex11f on a named stratosphere by donghao Tue Jan 18 11:39:43 2022<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[0]PETSC ERROR: Configure options --prefix=/opt/petsc/complex-double-with-cuda --with-cc=mpicc --with-cxx=mpicxx --with-fc=mpif90 COPTFLAGS="-O3 -mavx2" CXXOPTFLAGS="-O3 -mavx2" FOPTFLAGS="-O3 -ffree-line-length-none -mavx2" CUDAOPTFLAGS=-O3 --with-cxx-dialect=cxx14 --with-cuda-dialect=cxx14 --with-scalar-type=complex --with-precision=double --with-cuda-dir=/usr/local/cuda --with-debugging=1<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[0]PETSC ERROR: #1 PetscFinalize() at /home/donghao/packages/petsc-current/src/sys/objects/pinit.c:1638<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[0]PETSC ERROR: #2 User provided function() at User file:0<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I can also confirm that rolling back to petsc 3.15 will *<b class="">not</b>* see the problem, even with the new nvidia driver. And petsc 3.16.3 with an old nvidia driver (470.42) also get this same error. So it’s probably not connected to the nvidia driver.<span class="apple-converted-space"> </span><o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Any idea on where I should look at next?<span class="apple-converted-space"> </span><o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Thanks a lot in advance, and all the best,<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Hao<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div></div><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">From:<span class="apple-converted-space"> </span></b><a href="mailto:jacob.fai@gmail.com" style="color: blue; text-decoration: underline;" class="">Jacob Faibussowitsch</a><br class=""><b class="">Sent:<span class="apple-converted-space"> </span></b>Sunday, January 16, 2022 12:12 AM<br class=""><b class="">To:<span class="apple-converted-space"> </span></b><a href="mailto:junchao.zhang@gmail.com" style="color: blue; text-decoration: underline;" class="">Junchao Zhang</a><br class=""><b class="">Cc:<span class="apple-converted-space"> </span></b><a href="mailto:petsc-users@mcs.anl.gov" style="color: blue; text-decoration: underline;" class="">petsc-users</a>;<span class="apple-converted-space"> </span><a href="mailto:dong-hao@outlook.com" style="color: blue; text-decoration: underline;" class="">Hao DONG</a><br class=""><b class="">Subject:<span class="apple-converted-space"> </span></b>Re: [petsc-users] Strange CUDA failure with a second petscfinalize with PETSc 3.16<o:p class=""></o:p></div></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I don’t quite understand how it is getting to the CUDA error to be honest. None of the code in the stack trace is anywhere near the device code. Reading the error message carefully, it first chokes on PetscLogGetStageLog() from a call to PetscClassIdRegister():<o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div></div></div><div class=""><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">PetscErrorCode PetscLogGetStageLog(PetscStageLog *stageLog)<o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">{<o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> PetscFunctionBegin;<o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> PetscValidPointer(stageLog,1);<o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> if (!petsc_stageLog) {<o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> fprintf(stderr, "PETSC ERROR: Logging has not been enabled.\nYou might have forgotten to call PetscInitialize().\n");<o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> PETSCABORT(MPI_COMM_WORLD, PETSC_ERR_SUP); // Here<o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> }<o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> ...<o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">But then jumps to PetscFinalize(). You can also see the "You might have forgotten to call PetscInitialize().” message in the error message, just under the topmost level of the stack trace.<o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Can you check the value of ierr of each function call (use the CHKERRA() macro to do so)? I suspect the problem here that errors occurring previously in the program are being ignored, leading to the garbled stack trace.<o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div></div><div class=""><div class=""><div class=""><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Best regards,<br class=""><br class="">Jacob Faibussowitsch<br class="">(Jacob Fai - booss - oh - vitch)<o:p class=""></o:p></div></div></div></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><br class=""><br class=""><br class=""><o:p class=""></o:p></div></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class=""><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">On Jan 14, 2022, at 20:58, Junchao Zhang <<a href="mailto:junchao.zhang@gmail.com" style="color: blue; text-decoration: underline;" class="">junchao.zhang@gmail.com</a>> wrote:<o:p class=""></o:p></div></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div></div><div class=""><div class=""><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Jacob, <o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> Could you have a look as it seems the "invalid device context" is in your newly added module?<o:p class=""></o:p></div></div></div><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> Thanks<o:p class=""></o:p></div></div></div><div class=""><div class=""><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">--Junchao Zhang<o:p class=""></o:p></div></div></div></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div></div><div class=""><div class=""><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">On Fri, Jan 14, 2022 at 12:49 AM Hao DONG <<a href="mailto:dong-hao@outlook.com" style="color: blue; text-decoration: underline;" class="">dong-hao@outlook.com</a>> wrote:<o:p class=""></o:p></div></div></div><blockquote style="border-style: none none none solid; border-left-width: 1pt; border-left-color: rgb(204, 204, 204); padding: 0in 0in 0in 6pt; margin: 5pt 0in 5pt 4.8pt;" class=""><div class=""><div class=""><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Dear All, <o:p class=""></o:p></div></div><div class=""><p class="MsoNormal" style="margin: 0in 0in 0in 40.8pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </p></div><div class=""><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I have encountered a peculiar problem when fiddling with a code with PETSC 3.16.3 (which worked fine with PETSc 3.15). It is a very straight forward PDE-based optimization code which repeatedly solves a linearized PDE problem with KSP in a subroutine (the rest of the code does not contain any PETSc related content). The main program provides the subroutine with an MPI comm. Then I set the comm as PETSC_COMM_WORLD to tell PETSC to attach to it (and detach with it when the solving is finished each time).<o:p class=""></o:p></div></div></div><div class=""><p class="MsoNormal" style="margin: 0in 0in 0in 40.8pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </p></div><div class=""><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Strangely, I observe a CUDA failure whenever the petscfinalize is called for a *second* time. In other words, the first and second PDE calculations with GPU are fine (with correct solutions). The petsc code just fails after the SECOND petscfinalize command is called. You can also see the PETSC config in the error message:<span class="apple-converted-space"> </span><o:p class=""></o:p></div></div><p class="MsoNormal" style="margin: 0in 0in 0in 40.8pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </p></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1]PETSC ERROR: --------------------- Error Message --------------------------------------------------------------<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1]PETSC ERROR: GPU error<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1]PETSC ERROR: cuda error 201 (cudaErrorDeviceUninitialized) : invalid device context<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1]PETSC ERROR: See<span class="apple-converted-space"> </span><a href="https://petsc.org/release/faq/" target="_blank" style="color: blue; text-decoration: underline;" class="">https://petsc.org/release/faq/</a><span class="apple-converted-space"> </span>for trouble shooting.<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1]PETSC ERROR: Petsc Release Version 3.16.3, unknown<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1]PETSC ERROR: maxwell.gpu on a named stratosphere by hao Fri Jan 14 10:21:05 2022<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1]PETSC ERROR: Configure options --prefix=/opt/petsc/complex-double-with-cuda --with-cc=mpicc --with-cxx=mpicxx --with-fc=mpif90 COPTFLAGS="-O3 -mavx2" CXXOPTFLAGS="-O3 -mavx2" FOPTFLAGS="-O3 -ffree-line-length-none -mavx2" CUDAOPTFLAGS=-O3 --with-cxx-dialect=cxx14 --with-cuda-dialect=cxx14 --with-scalar-type=complex --with-precision=double --with-cuda-dir=/usr/local/cuda --with-debugging=1<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1]PETSC ERROR: #1 PetscFinalize() at /home/hao/packages/petsc-current/src/sys/objects/pinit.c:1638<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">You might have forgotten to call PetscInitialize().<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">The EXACT line numbers in the error traceback are not available.<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Instead the line number of the start of the function is given.<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1] #1 PetscAbortFindSourceFile_Private() at /home/hao/packages/petsc-current/src/sys/error/err.c:35<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1] #2 PetscLogGetStageLog() at /home/hao/packages/petsc-current/src/sys/logging/utils/stagelog.c:29<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1] #3 PetscClassIdRegister() at /home/hao/packages/petsc-current/src/sys/logging/plog.c:2376<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1] #4 MatMFFDInitializePackage() at /home/hao/packages/petsc-current/src/mat/impls/mffd/mffd.c:45<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1] #5 MatInitializePackage() at /home/hao/packages/petsc-current/src/mat/interface/dlregismat.c:163<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1] #6 MatCreate() at /home/hao/packages/petsc-current/src/mat/utils/gcreate.c:77<o:p class=""></o:p></div></div><p class="MsoNormal" style="margin: 0in 0in 0in 40.8pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </p><div class=""><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">However, it doesn’t seem to affect the other part of my code, so the code can continue running until it gets to the petsc part again (the *<b class="">third</b>* time). Unfortunately, it doesn’t give me any further information even if I set the debugging to yes in the configure file. It also worth noting that PETSC without CUDA (i.e. with simple MATMPIAIJ) works perfectly fine. <o:p class=""></o:p></div></div></div><div class=""><p class="MsoNormal" style="margin: 0in 0in 0in 40.8pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </p></div><div class=""><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I am able to re-produce the problem with a toy code modified from ex11f. Please see the attached file (ex11fc.F90) for details. Essentially the code does the same thing as ex11f, but three times with a do loop. To do that I added an extra MPI_INIT/MPI_FINALIZE to ensure that the MPI communicator is not destroyed when PETSC_FINALIZE is called. I used the PetscOptionsHasName utility to check if you have “-usecuda” in the options. So running the code with and without that option can give you a comparison w/o CUDA. I can see that the code also fails after the second loop of the KSP operation. Could you kindly shed some lights on this problem?<o:p class=""></o:p></div></div></div><div class=""><p class="MsoNormal" style="margin: 0in 0in 0in 40.8pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </p></div><div class=""><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I should say that I am not even sure if the problem is from PETSc, as I also accidentally updated the NVIDIA driver (for now it is 510.06 with cuda 11.6). And it is well known that NVIDIA can give you some surprise in the updates (yes, I know I shouldn’t have touched that if it’s not broken). But my CUDA code without PETSC (which basically does the same PDE thing, but with cusparse/cublas directly) seems to work just fine after the update. It is also possible that my petsc code related to CUDA was not quite “legitimate” – I just use:<span class="apple-converted-space"> </span><o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> MatSetType(A, MATMPIAIJCUSPARSE, ierr)<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">and<span class="apple-converted-space"> </span><o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> MatCreateVecs(A, u, PETSC_NULL_VEC, ierr)<o:p class=""></o:p></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">to make the data onto GPU. I would very much appreciate it if you could show me the “right” way to do that. <o:p class=""></o:p></div></div><p class="MsoNormal" style="margin: 0in 0in 0in 40.8pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </p><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Thanks a lot in advance, and all the best,<o:p class=""></o:p></div></div></div><div style="margin-left: 40.8pt;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Hao<o:p class=""></o:p></div></div></div></div></blockquote></div></div></blockquote></div></div></div></div></blockquote></div></div></blockquote></div></div></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div></div></blockquote></div></div><div dir="ltr" class=""><div class=""><blockquote type="cite" class=""><div dir="ltr" class=""></div></blockquote></div></div><div dir="ltr" class=""><div class=""><blockquote type="cite" class=""><div dir="ltr" class=""></div></blockquote></div></div><div dir="ltr" class=""><div class=""><blockquote type="cite" class=""><div dir="ltr" class=""></div></blockquote></div></div></div><div dir="ltr" class=""></div><div dir="ltr" class=""></div><div dir="ltr" class=""></div><div dir="ltr" class=""></div><div dir="ltr" class=""></div><div dir="ltr" class=""></div></div><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""></div><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""></div><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""></div><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""></div><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""></div><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""></div><span id="cid:96CC8098DFCA154BA6355C47A025F4AE@sct-15-20-4755-11-msonline-outlook-5fbaf.templateTenant"><configure.log></span><span id="cid:4C4A6D2993E66844BC71D65F275B815B@sct-15-20-4755-11-msonline-outlook-5fbaf.templateTenant"><ex11fc.F90></span><span id="cid:59B8513CD614B84F9C0F24BAEA1BBC7D@sct-15-20-4755-11-msonline-outlook-5fbaf.templateTenant"><ex11fc.log></span></div></blockquote></div><br class=""></div></body></html>