Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

forrtl: severe (174): SIGSEGV, segmentation fault occurred

Status
Not open for further replies.
K

K-H Gong

Kanghua Gong
New Member
Hello, I meet a error when I run BHIST CASE. I use CESM2.2.0 version and create_newcase( -- res f19_g17 --compset BHIST ). I use hybrid run from a B1850 control run. All processes are successful. case.setup case.build successful. But I meet the error (forrtl: severe (174): SIGSEGV, segmentation fault occurred) when I submit the case. Blow is cesm.log file. I search the error in google and it says my stack_size is too small. I set ulimit -s unlimited and vim config_machines.xml (stacksize). the error is not sovled. Unfortunately, I can not find where is wrong( inputdata or somthing else). I really need your help. thank you
 

Attachments

  • cesm.log.txt
    73.3 KB · Views: 12
D

dbailey

CSEG and Liaisons
Staff member
This logfile looks like it is from the ice sheet model (CISM2.0). Is this on your own machine?
 
K

K-H Gong

Kanghua Gong
New Member
dbailey said:
This logfile looks like it is from the ice sheet model (CISM2.0). Is this on your own machine?
Click to expand...
I run the model on HPC centos7 system. I have run the B1850 successfully. I don't konw why I can't run BHIST. In my opinion, BHIST and B1850 are the same from the config, just have different external forcing.
 
slevis

slevis

Moderator
Staff member
Just to be clear:
Did you repeat the exact same steps for BHIST as for B1850 and BHIST failed? In that case, I would try a second time (possibly starting from the beginning if necessary), in case the failure is due to a glitch.
 
slevis

slevis

Moderator
Staff member
...or you may need to consider a different PE layout or (more likely) additional memory for BHIST.
 
K

K-H Gong

Kanghua Gong
New Member
slevis said:
...or you may need to consider a different PE layout or (more likely) additional memory for BHIST.
Click to expand...
Thank you Slevis, I have checked inputdata completely. I think BHIST need more memory. So, maybe I need to change the batch queue more large memory. I try it.
 
K

K-H Gong

Kanghua Gong
New Member
Hello slevis, I tried more cores but it still meets error. I also run B1850 successfully. Each core has 192G memory and have 36 cores. I use 12 cores to run BHIST. But it is wrong the same. So I guess it maybe somgthing wrong elsewhere.
 
D

dbailey

CSEG and Liaisons
Staff member
This was sent to me in a conversation. It is blowing memory in the land. I am going to move this thread.

MCT::m_Router::initp_: GSMap indices not increasing...Will correct
MCT::m_Router::initp_: RGSMap indices not increasing...Will correct
MCT::m_Router::initp_: RGSMap indices not increasing...Will correct
MCT::m_Router::initp_: GSMap indices not increasing...Will correct
MCT::m_Router::initp_: GSMap indices not increasing...Will correct
MCT::m_Router::initp_: RGSMap indices not increasing...Will correct
MCT::m_Router::initp_: RGSMap indices not increasing...Will correct
MCT::m_Router::initp_: GSMap indices not increasing...Will correct
(seq_domain_areafactinit) : min/max mdl2drv 0.999565346641447 1.00000000000000 areafact_o_OCN
(seq_domain_areafactinit) : min/max drv2mdl 1.00000000000000 1.00043484236425 areafact_o_OCN
(seq_domain_areafactinit) : min/max mdl2drv 0.999565346641447 1.00000000000000 areafact_i_ICE
(seq_domain_areafactinit) : min/max drv2mdl 1.00000000000000 1.00043484236425 areafact_i_ICE
calcsize j,iq,jac, lsfrm,lstoo 1 1 1 26 21
calcsize j,iq,jac, lsfrm,lstoo 1 1 2 26 21
calcsize j,iq,jac, lsfrm,lstoo 1 2 1 22 15
calcsize j,iq,jac, lsfrm,lstoo 1 2 2 22 15
calcsize j,iq,jac, lsfrm,lstoo 1 3 1 24 17
calcsize j,iq,jac, lsfrm,lstoo 1 3 2 24 17
calcsize j,iq,jac, lsfrm,lstoo 1 4 1 25 20
calcsize j,iq,jac, lsfrm,lstoo 1 4 2 25 20
calcsize j,iq,jac, lsfrm,lstoo 1 5 1 23 19
calcsize j,iq,jac, lsfrm,lstoo 1 5 2 23 19
calcsize j,iq,jac, lsfrm,lstoo 2 1 1 21 26
calcsize j,iq,jac, lsfrm,lstoo 2 1 2 21 26
calcsize j,iq,jac, lsfrm,lstoo 2 2 1 15 22
calcsize j,iq,jac, lsfrm,lstoo 2 2 2 15 22
calcsize j,iq,jac, lsfrm,lstoo 2 3 1 17 24
calcsize j,iq,jac, lsfrm,lstoo 2 3 2 17 24
calcsize j,iq,jac, lsfrm,lstoo 2 4 1 20 25
calcsize j,iq,jac, lsfrm,lstoo 2 4 2 20 25
calcsize j,iq,jac, lsfrm,lstoo 2 5 1 19 23
calcsize j,iq,jac, lsfrm,lstoo 2 5 2 19 23
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
cesm.exe 000000000357591D Unknown Unknown Unknown
cesm.exe 00000000035737B7 Unknown Unknown Unknown
cesm.exe 0000000003500134 Unknown Unknown Unknown
cesm.exe 00000000034FFF46 Unknown Unknown Unknown
cesm.exe 0000000003480F66 Unknown Unknown Unknown
cesm.exe 000000000348BA90 Unknown Unknown Unknown
Unknown 00007F1EFE7CB6D0 Unknown Unknown Unknown
cesm.exe 0000000001DFD189 cnfunmod_mp_cnfun 725 CNFUNMod.F90
cesm.exe 00000000020B7FC7 soilbiogeochemcom 737 SoilBiogeochemCompetitionMod.F90
cesm.exe 0000000002347A87 cndrivermod_mp_cn 393 CNDriverMod.F90
cesm.exe 0000000001E654D7 cnvegetationfacad 939 CNVegetationFacade.F90
cesm.exe 0000000001C67AFB clm_driver_mp_clm 967 clm_driver.F90
cesm.exe 0000000001C51BB7 lnd_comp_mct_mp_l 457 lnd_comp_mct.F90
cesm.exe 0000000000434981 component_mod_mp_ 737 component_mod.F90
cesm.exe 00000000004179F5 cime_comp_mod_mp_ 2626 cime_comp_mod.F90
cesm.exe 0000000000434617 MAIN__ 133 cime_driver.F90
cesm.exe 000000000041591E Unknown Unknown Unknown
libc.so.6 00007F1EFE10F445 Unknown Unknown Unknown
 
Status
Not open for further replies.
Top