Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Question: Is AMD processor + Intel compiler supported by SCHISM? #77

Open
SorooshMani-NOAA opened this issue Aug 19, 2022 · 8 comments
Open

Question: Is AMD processor + Intel compiler supported by SCHISM? #77

SorooshMani-NOAA opened this issue Aug 19, 2022 · 8 comments
Assignees
@pvelissariou1

Comments

@SorooshMani-NOAA
Copy link

I'm trying this combination on ParallelWorks platform where they have AWS HPC6a instances (AMD) and I'm using the same Intel compilers (2021.3.0) that I used on Intel to run it, but the run doesn't go through, I get a segfault. So I was wondering if there are any known issues with this combination?
@josephzhang8
Copy link
Member

josephzhang8 commented Aug 19, 2022 via email

@jamal919
Copy link
Member

Interesting! Any idea how the model performs in desktop grade AMD processors with GCC? To put it different way, is the performance is comparable between an Intel i7 and Ryzen 5 processors? Thanks.

@SorooshMani-NOAA
Copy link
Author

@josephzhang8, should setting UCX_UNIFIED_MODE=y at runtime fix the crash or there are other things I need to change as well?

@josephzhang8
Copy link
Member

josephzhang8 commented Aug 22, 2022 via email

@SorooshMani-NOAA
Copy link
Author

I see, thank you

@SorooshMani-NOAA
Copy link
Author

I still see the same issue on hpc6a platform with the

limit -s unlimited
export UCX_UNIFIED_MODE=y

environment. I get the following error in my run logs: first one of the following lines for each core:

MPI startup(): Warning: I_MPI_PMI_LIBRARY will be ignored since the hydra process manager was found

which I think is due to how the ParallelWorks environment is set up. And then one of these for each core

forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image              PC                Routine            Line        Source
pschism_PAHM_TVD-  00000000006F71DA  for__signal_handl     Unknown  Unknown
libpthread-2.17.s  00002AFBEEFD8630  Unknown               Unknown  Unknown
libshm-fi.so       00002AFCFA21A98A  Unknown               Unknown  Unknown
libshm-fi.so       00002AFCFA2078BE  Unknown               Unknown  Unknown
libshm-fi.so       00002AFCFA2026B9  Unknown               Unknown  Unknown
libshm-fi.so       00002AFCFA202F23  Unknown               Unknown  Unknown
libefa-fi.so       00002AFCFAA08E31  Unknown               Unknown  Unknown
libefa-fi.so       00002AFCFAA11945  Unknown               Unknown  Unknown
libefa-fi.so       00002AFCFAA077A9  Unknown               Unknown  Unknown
libefa-fi.so       00002AFCFAA07865  Unknown               Unknown  Unknown
libmpi.so.12.0.0   00002AFBEDB26E84  Unknown               Unknown  Unknown
libmpi.so.12.0.0   00002AFBEDE1117B  Unknown               Unknown  Unknown
libmpi.so.12.0.0   00002AFBEDE18094  Unknown               Unknown  Unknown
libmpi.so.12.0.0   00002AFBEDA0746A  Unknown               Unknown  Unknown
libmpi.so.12.0.0   00002AFBEDA7BAF0  Unknown               Unknown  Unknown
libmpi.so.12.0.0   00002AFBEDA6616B  Unknown               Unknown  Unknown
libmpi.so.12.0.0   00002AFBEDA54748  MPI_Comm_dup          Unknown  Unknown
libmpifort.so.12.  00002AFBED4F260B  pmpi_comm_dup_        Unknown  Unknown
pschism_PAHM_TVD-  0000000000448D6E  Unknown               Unknown  Unknown
pschism_PAHM_TVD-  0000000000410794  Unknown               Unknown  Unknown
pschism_PAHM_TVD-  00000000004106A2  Unknown               Unknown  Unknown
libc-2.17.so       00002AFBEF207555  __libc_start_main     Unknown  Unknown
pschism_PAHM_TVD-  00000000004105A9  Unknown               Unknown  Unknown

@josephzhang8
Copy link
Member

josephzhang8 commented Aug 22, 2022 via email

@josephzhang8
Copy link
Member

josephzhang8 commented Aug 22, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pvelissariou1 pvelissariou1

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jamal919 @josephzhang8 @pvelissariou1 @SorooshMani-NOAA