You need to enable JavaScript to run this app.
Elastic Compute Service

Elastic Compute Service

Copy page
Download PDF
Linux operating system issue
What do I do if performance degradation occurs on ECS instances using AMD CPUs after I update the operating system or kernel?
Copy page
Download PDF
What do I do if performance degradation occurs on ECS instances using AMD CPUs after I update the operating system or kernel?
Causes​
The latest version of the operating system has the AMD SRSO vulnerability patches integrated and enabled by default. Enabling such patches may cause a significant performance degradation of the instance.​
Solutions​
  1. Execute the following command to check the currently active security mitigations.​
  • ​
    grep . /sys/devices/system/cpu/vulnerabilities/*​
    ​
  1. If "Safe RET" exists in the security mitigations for spec_rstack_overflow, the kernel has enabled security mitigations for SRSO. However, this may cause a significant performance degradation in some applications.​
  • If you trust user-space applications and want to avoid performance issues, follow these steps to add the spec_rstack_overflow=off kernel parameter to the kernel command line and restart the instance to forcefully disable SRSO security mitigations.​
tip​
AMD believes that the overall security risk associated with SRSO is low in common cloud environments. Therefore, AMD considers it reasonable for ECS users to disable SafeRET. Learn more.​
  • ​
    RHEL, CentOS, AlmaLinux, Rocky Linux, and Fedora operating systems
    veLinux, Debian, and Ubuntu operating systems
    ​
    1. Execute the following command to add the parameter for disabling SRSO to the grub file.​
    • ​
      sudo sed -i "/GRUB_CMDLINE_LINUX=\"/s/\"$/ ​
      spec_rstack_overflow=off\"/" /etc/default/grub​
      ​
    tip​
    To enable SRSO, execute the sudo sed -i "s/ spec_rstack_overflow=off//g" /etc/default/grub command.​
    1. Execute the following command to generate a new grub file.​
    • ​
      sudo grub2-mkconfig -o /boot/grub2/grub.cfg​
      ​
    1. Execute the following command to restart the instance for the configuration to take effect.​
    • ​
      sudo reboot​
      ​
    ​
    ​
  • ​
​
​
Last updated: 2026.04.13 16:50:03