CESM1.0.5 stuck at Initialize atm component

[xlong@ncsu_edu]

the model is frozen at the step of " Initialize atm component"the ccsm log shows :Opened existing file /gpfs_backup/stormtrack_data/xlong/cesmdata/input/atm/cam/inic/fv/cami-mam3_000 0-01-01_0.9x1.25_L30_c100618.nc       65536 Opened existing file /gpfs_backup/stormtrack_data/xlong/cesmdata/input/atm/cam/topo/USGS-gtopo30_0.9 x1.25_remap_c051027.nc      131072 Any possible reason for this issue? Thanks

 

[xlong@ncsu_edu]

update,I reconfigure the model in a lower res, f45_g37the model abort at the 'Initialize atm component' step, and a 'forrtl: severe (174): SIGSEGV, segmentation fault occurred'  error shows up.Attached is the f45_g37 run log file

 

[xlong@ncsu_edu]

update,I reconfigure the model in a lower res, f45_g37the model abort at the 'Initialize atm component' step, and a 'forrtl: severe (174): SIGSEGV, segmentation fault occurred'  error shows up.Attached is the f45_g37 run log file

 

[xlong@ncsu_edu]

Fixed.It is the Intel 1.4.x issue.I reduced the optimization level to -O1, problem solved

 

[xlong@ncsu_edu]

Fixed.It is the Intel 1.4.x issue.I reduced the optimization level to -O1, problem solved

 

[chensheng@scsio_ac_cn]

I am troubled by the same problem.
Could you explain your method in detail? Thanks

 

[chensheng@scsio_ac_cn]

I am troubled by the same problem.
Could you explain your method in detail? Thanks

 

[xlong@ncsu_edu]

Hi,I had this issue when I tried to port cesm1.0.5 to my local computer.I finnally found that it is a compiler related issue.The solution is to lower the optimization level in the compiler setting, in the macro file. You can test whether your compiling error is due to this reason, by compiling the model with DEBUG option on.If you can compile the model successfully with the DEBUG ON, but fail with DEBUG OFF, then my solution might work for you.Otherwise, it might be due to something else.   

 

[xlong@ncsu_edu]

Hi,I had this issue when I tried to port cesm1.0.5 to my local computer.I finnally found that it is a compiler related issue.The solution is to lower the optimization level in the compiler setting, in the macro file. You can test whether your compiling error is due to this reason, by compiling the model with DEBUG option on.If you can compile the model successfully with the DEBUG ON, but fail with DEBUG OFF, then my solution might work for you.Otherwise, it might be due to something else.