Add CPU and voltage regulator thermal messages
Tested:
Used a heat gun to heat the CPU and voltage regulator and checked
that the message is logged correctly.
Change-Id: I4d73a9ad12691b364a33faf036a60f36bab0ac93
Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
diff --git a/redfish-core/include/registries/openbmc_message_registry.hpp b/redfish-core/include/registries/openbmc_message_registry.hpp
index 5f8fef2..0e923f0 100644
--- a/redfish-core/include/registries/openbmc_message_registry.hpp
+++ b/redfish-core/include/registries/openbmc_message_registry.hpp
@@ -96,6 +96,16 @@
.paramTypes = {"string"},
.resolution = "None.",
}},
+ MessageEntry{"CPUThermalTrip",
+ {
+ .description = "Indicates that the specified CPU thermal "
+ "trip has been asserted.",
+ .message = "CPU %1 Thermal Trip.",
+ .severity = "Critical",
+ .numberOfArgs = 1,
+ .paramTypes = {"number"},
+ .resolution = "None.",
+ }},
MessageEntry{
"DCPowerOff",
{
@@ -1366,5 +1376,16 @@
.paramTypes = {},
.resolution = "None.",
}},
+ MessageEntry{
+ "VoltageRegulatorOverheated",
+ {
+ .description =
+ "Indicates that the specified voltage regulator overheated.",
+ .message = "%1 Voltage Regulator Overheated.",
+ .severity = "Critical",
+ .numberOfArgs = 1,
+ .paramTypes = {"string"},
+ .resolution = "None.",
+ }},
};
} // namespace redfish::message_registries::openbmc