RESOLVED: 10/14/2024 - We have applied a fix that we believe has solved the issue. If you are still experiencing problems, please contact contact ICER support with a description and steps to reproduce the issue.

UPDATED: 10/11/2024 - We believe that we have found the issue and will apply a fix on Monday, 10/14. In the meantime, please use the workarounds below.

UPDATED: 9/27/2024 - We are receiving reports that some user code inside of jobs is continuing to receive “Illegal instruction (core dumped)” errors. ICER is investigating, but in the meantime, please try the following workarounds (one at a time):

  • Add the line #SBATCH --export=NONE to your job script.
  • Ensure you are submitting from the same development node as the node your job will run on. You can use constraints to do so, like the line #SBATCH --constraint=<insert_here> where <insert_here> is one of intel14, intel16, intel18, or amd20. Or, if you are using a buy-in node of a specific type, make sure to use the corresponding development node to submit.
  • Submit jobs from dev-intel14.

UPDATED: 9/26/2024 - This issue has been patched and should no longer affect salloc commands. If you find that you are still getting these errors, please contact ICER support with a description of the commands you ran and what node you ran them on.

Due to recent changes allowing for better-optimized software, users may notice “Illegal instruction (core dumped)” errors. For example:

srun: error: hostname: task 0: Illegal instruction (core dumped)

These errors have been reported using salloc and sbatch on dev-intel-18, especially when the job runs on a different generation of node, like intel16.