From 945299f077adb1b138b6507d1a3943415d6c2079 Mon Sep 17 00:00:00 2001 From: Matt Spinler Date: Thu, 6 Feb 2020 14:16:09 -0600 Subject: PEL: Add ESEL event log keyword to README Explain how the ESEL keyword can be used in the Additional Data event log property to send in PEL data. Signed-off-by: Matt Spinler Change-Id: I47fd97c4ee5f756b7d0139a4041f1e395c2859b3 --- extensions/openpower-pels/README.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) (limited to 'extensions/openpower-pels') diff --git a/extensions/openpower-pels/README.md b/extensions/openpower-pels/README.md index eac30be..bf3e260 100644 --- a/extensions/openpower-pels/README.md +++ b/extensions/openpower-pels/README.md @@ -23,6 +23,21 @@ RAWPEL="/tmp/pels/pel.5" The code will assign its own error log ID to this PEL, and also update the commit timestamp field to the current time. +#### ESEL + +This keyword's data contains a full PEL in string format. This is how hostboot +sends down PELs when it is configured in IPMI communication mode. The PEL is +handled just like the PEL obtained using the RAWPEL keyword. + +The syntax is: + +``` +ESEL= +"00 00 df 00 00 00 00 20 00 04 12 01 6f aa 00 00 50 48 00 30 01 00 33 00 00..." +``` + +Note that there are 16 bytes of IPMI SEL data before the PEL data starts. + #### _PID This keyword that contains the application's PID is added automatically by the -- cgit v1.2.1