Gitiles
Code Review Sign In
gerrit.openbmc.org / CharlesHsu0511 / phosphor-sel-logger / 6afe9560852c6431c43c8e79a28e2b7cb498e355
commit6afe9560852c6431c43c8e79a28e2b7cb498e355[log] [tgz]
authorJason M. Bills <jason.m.bills@linux.intel.com>Thu Aug 29 16:33:55 2019 -0700
committerJason M. Bills <jason.m.bills@linux.intel.com>Thu Aug 29 16:33:55 2019 -0700
tree871384269b34a108acb9cd7a07bdc4d238ab8a2d
parent3d300fca24b30864b3e9a4f5768cfe5e769458ae [diff]
Restart at record ID 1 after clearing the SEL

Since the record IDs are incremented only based on the last ID,
when the SEL is cleared, the next ID continues from where it was
before being cleared.

This change checks if the SEL has been cleared and resets the
stored ID so the next ID will start from 1 again.

Tested:
Added a SEL entry and checked the ID. Cleared the SEL and added
another SEL entry and confirmed that the ID restarted at 1.

Change-Id: I192441515e7502a9751db8023c06df0ba852ebac
Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
1 file changed
tree: 871384269b34a108acb9cd7a07bdc4d238ab8a2d
  1. include/
  2. service_files/
  3. src/
  4. .clang-format
  5. cmake-format.json
  6. CMakeLists.txt
  7. LICENSE
  8. MAINTAINERS
  9. README.md
README.md

phosphor-sel-logger

Overview

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.

Metadata

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

Interface

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

  • A text message to include in the journal entry
  • The sensor path
  • Up to three bytes of SEL data
  • The direction of the event (assertion or deassertion)
  • The generator ID of the requester

The interface for OEM type events requires

  • A text message to include in the journal entry
  • Up to thirteen bytes of SEL data (depending on the record type)
  • The record type

The MESSAGE_ID and IPMI_SEL_RECORD_ID metadata fields are added by the daemon.

Event Monitoring

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.