Re: [petsc-users] build pets with 64 bit indices

Just use -bv_type mat and the error will go away. Note: you are highly advised to update to a new PETSc/SLEPc version. Thanks, Pierre > On 30 Apr 2025, at 7:58 AM, hexioafeng wrote: > > Dear Sir, > > Thank you for your kind reply. Bellow are the full backtrace: > > [0]PETSC ERROR: --

Re: [petsc-users] build pets with 64 bit indices

Dear Sir, Thank you for your kind reply. Bellow are the full backtrace: [0]PETSC ERROR: - Error Message -- [0]PETSC ERROR: No support for this operation for this object type [0]PETSC ERROR: Product of

Re: [petsc-users] build pets with 64 bit indices

Could you please provide the full back trace? Depending on your set of options, it may be as simple as switching -bv_type to make your code run (if you are using svec, this would explain such an error but could be circumvented with something else, like mat). Thanks, Pierre > On 30 Apr 2025, at

Re: [petsc-users] build pets with 64 bit indices

On Wed, 30 Apr 2025, hexioafeng via petsc-users wrote: > Dear PETSc developers, > > I use PETSc and SLEPC to solve generalized eigen problems. When solving an > interval eigen problem with matrix size about 5 million, i got the error > message: "product of two integer xx xx overflow, you must

[petsc-users] build pets with 64 bit indices

Dear PETSc developers, I use PETSc and SLEPC to solve generalized eigen problems. When solving an interval eigen problem with matrix size about 5 million, i got the error message: "product of two integer xx xx overflow, you must ./configure PETSc with --with-64-bit-indices for the case you are

Re: [petsc-users] problem with nested logging

Can you try using -log_sync ? This should check every entry/exit points of logged Events and complain if something is not collectively called Stefano On Tue, Apr 29, 2025, 18:21 Randall Mackie wrote: > ah okay, I missed that this was found using openmpi. > > then it’s probably not the same issu

Re: [petsc-users] problem with nested logging

ah okay, I missed that this was found using openmpi. then it’s probably not the same issue we had. I can’t remember in which version it was fixed (I’m away from my work computer)….I do know in our case openmpi and the latest Intel One API work fine. Randy > On Apr 29, 2025, at 8:58 AM, Klaij,

Re: [petsc-users] problem with nested logging

Well, the error below only shows-up thanks to openmpi and gnu compilers. With the intel mpi and compilers it just hangs (tried oneapi 2023.1.0). In which version was that bug fixed? Chris _ dr. ir. Christiaan Klaij | senior researcher | Research & Development | CFD Development T +31 317 49

Re: [petsc-users] problem with nested logging

We had a similar issue last year that we eventually tracked down to a bug in Intel MPI AllReduce, which was around the same version you are using. Can you try a different MPI or the latest Intel One API and see if your error clears? Randy On Tue, Apr 29, 2025 at 8:17 AM Klaij, Christiaan via pet

Re: [petsc-users] problem with nested logging

I don't think so, we have tracing in place to detect mismatches. But as soon as I switch the tracing on, the error disappears... Same if I add a counter or print statements before and after EventBegin/End. Looks like a memory corruption problem, maybe nothing to do with petsc despite the error m

Re: [petsc-users] problem with nested logging

On Tue, Apr 29, 2025 at 6:50 AM Klaij, Christiaan wrote: > Here's a slightly better error message, obtained --with-debugging=1 > Is it possible that you have a mismatched EventBegin()/EventEnd() in your code? That could be why we cannot reproduce it here. Thanks, Matt > [0]PETSC ERRO

Re: [petsc-users] problem with nested logging

Here's a slightly better error message, obtained --with-debugging=1 [0]PETSC ERROR: - Error Message -- [0]PETSC ERROR: Petsc has generated inconsistent data [0]PETSC ERROR: MPIU_Allreduce() called in different locatio