| commit | d067a6bc2977b0535284f17f86fcac40f095cbc5 | [log] [tgz] |
|---|---|---|
| author | Konstantin Aladyshev <aladyshev22@gmail.com> | Fri Mar 31 09:22:49 2023 +0000 |
| committer | Konstantin Aladyshev <aladyshev22@gmail.com> | Thu May 25 11:21:01 2023 +0000 |
| tree | 9594d956128c71fe4e08b1a8a0b6758968d86f0d | |
| parent | 56ccc249f3f45bcb7486c93a19ab271173c64c68 [diff] |
Correct message for threshold events Thresholds can be deasserted not only because of the actual sensor data, but also because of the change in the general system state. For example some sensors can be configured to be measured only when the system is powered on. In such cases current messages can be confusing: "PVPP_ABCD_CPU2 sensor crossed a critical low threshold going high. Reading=0.033000 Threshold=2.410000". Replace message template to be more generic to cover discussed cases: "PVPP_ABCD_CPU2 critical low threshold deassert. Reading=0.033000 Threshold=2.410000". Change-Id: I875056c04bb2ff5e5dbcef10042a82c1ca06de5f Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
The SEL Logger daemon handles all requests to add new IPMI SEL records to the journal. SEL records stored in the journal are identified by the standard MESSAGE_ID metadata. Other metadata fields are used to store event-specific information for each record.
SEL records are identified in the journal using the MESSAGE_ID field.
The MESSAGE_ID for SEL records is "b370836ccf2f4850ac5bee185b77893a".
The additional metadata fields for a SEL record are
IPMI_SEL_RECORD_ID = Two byte unique SEL Record ID
IPMI_SEL_RECORD_TYPE = The type of SEL entry (system or OEM)
which determines the definition of the
remaining bytes
IPMI_SEL_GENERATOR_ID = The IPMI Generator ID (usually the
IPMB Slave Address) of the requester
IPMI_SEL_SENSOR_PATH = D-Bus path of the sensor in the event
IPMI_SEL_EVENT_DIR = Direction of the event (assert or deassert)
IPMI_SEL_DATA = Raw binary data included in the SEL record
The SEL Logger daemon exposes an interface for manually adding System and OEM type SEL events, and provides the capability to monitor for types of events and log them automatically.
The interface for System type events requires
The interface for OEM type events requires
The MESSAGE_ID and IPMI_SEL_RECORD_ID metadata fields are added by the daemon.
The SEL Logger daemon can be configured to watch for specific types of events and automatically log SEL records for them.
As an example, the SEL Logger has a "threshold event monitor" which implements a D-Bus match for any "PropertiesChanged" event on the xyz.openbmc_project.Sensor.Threshold interface. The handler then checks for any new threshold events and logs SEL records accordingly.