tree f5f729adeae0163ef200ecc1cf303d73b21f3437
parent 2d5824720597309fe815c99b096ce0d7bff56cf1
author Jayaprakash Mutyala <mutyalax.jayaprakash@intel.com> 1643759289 +0000
committer Jayaprakash Mutyala <mutyalax.jayaprakash@intel.com> 1646713040 +0000

Memhot event monitor for MEMHOT pins

The MEM_THERM_EVENT pins are tied to the incorrect SGPIO, so
Memory Thermtrip is incorrectly logging based on the MEMHOT
pins.

Define MemhotMonitor. This changes the Memhot monitor to log
based on the MEMHOT pins.

Tested:
1. Booted and confirmed that host-error-monitor correctly starts
2. Verified using RedFish event log. ComponentOverTemperature event log
   generated successfully.
GET:
https:/<BMC-IP>/redfish/v1/Systems/system/LogServices/EventLog/Entries
{
   "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/
   Entries/1646193775",
   "@odata.type": "#LogEntry.v1_8_0.LogEntry",
   "Created": "2022-03-02T04:02:55+00:00",
   "EntryType": "Event",
   "Id": "1646193775",
   "Message": "CPU 1 memory over temperature and being throttled.",
   "MessageArgs": [
      "CPU 1 memory"
   ],
   "MessageId": "OpenBMC.0.1.ComponentOverTemperature",
   "Name": "System Event Log Entry",
   "Severity": "Critical"
}

Signed-off-by: Hardik Panchal <hardikx.panchal@intel.com>
Signed-off-by: Jayaprakash Mutyala <mutyalax.jayaprakash@intel.com>
Change-Id: I39c68155422ae2c9691f3701946a174a2caae463