"Disabled CC6 power saving state due to AMD erratum 1474; to reenable it, do a hardware reset" alarm is triggered even after performing a hardware reset

Products

• VMware vSphere ESXi

Issue/Introduction

• After updating to ESXi 8.0U3 and above, the following alarm is triggered on the host within ~5 days :
  
  This email is to notify you that an alarm has been triggered in your vCenter:
  Alarm alarm.HostErrorAlarm on Host xxxx.xxx.xx
  because Issue detected on xxxx.xxx.xx in VTC-Datacenter: CPUAMD: 1436: Disabled CC6 power saving state due to AMD erratum 1474; to reenable it, do a hardware reset (MM/DD/YYYY HH:MM:SS cpu64:000000).

• We can see the following log entries -
  
  hostd.log
  MM-DD-YYYY HH:MM:SS In(166) Hostd[2099825]: [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 5602 : Issue detected on xxx.xxx.xxx in ha-datacenter: CPUAMD: 1436: Disabled CC6 power saving state due to AMD erratum 1474; to reenable it, do a hardware reset
  
  vmkernel.log
  MM-DD-YYYY HH:MM:SS Al(177) vmkalert: cpu64:2097984)ALERT: CPUAMD: 1436: Disabled CC6 power saving state due to AMD erratum 1474; to reenable it, do a hardware reset

• Despite following the alarm's recommendation and performing a proper hardware power cycle of the host, the issue persists, and the alarm continues to be triggered.

Environment

vSphere ESXi 8.0U3

Cause

This alarm and the automatic disabling of CC6 are intended to trigger after 1000 days of host uptime. However, due to a computation overflow, it occurs after approximately 5.79 days of uptime instead.

Resolution

This issue is resolved in ESXi 8.0 Update 3e.