Parse PELs sent by OpenPOWER host firmware

Stewart Smith stewart at
Thu Apr 12 15:32:17 AEST 2018

Alexander Amelkin <a.amelkin at> writes:
> 14.03.2018 03:36, Stewart Smith wrote:
>> Deepak Kodihalli <dkodihal at> writes:
>>> The SELs/eSELs (System Event Log) that OpenBMC receives from 
>>> hostboot/skiboot today are not interpreted, and are dumped as-is in a 
>>> property of the error log D-Bus object. This means that if there's a PEL 
>>> (Platform Event Log) hidden in the eSEL, admins/users of the error log 
>>> need to depend on external tools to parse the PEL to human readable
>>> text.
>> My lack of love for PELs is probably fairly well known, but even if we
>> replace them down the line, I think there's opportunity here for making
>> things better for users (including myself).
> Just my 2 cents. The IPMI-standardized SELs are good first of all
> because of IPMI-standardized PEFs and PETs.
> Being able to decode the OEM SEL records is not just convenient for the
> users, but will also let them easily attach PEFs to such events if they
> want to. That's of course when PEFs are supported in OpenBMC which is
> currently not true, AFAIK.
> As a maintainer of ipmitool I can promise to promptly include the
> OpenPOWER event record decoder into ipmitool upstream code. All I need
> is the information on how to decode those events. So far I'm planning to
> try and deduce this information from hostboot and opal sources.

(Adding in Tim from Raptor as we were talking about this yesterday)

There's opal-elog-parse, which is part of ppc64-diag, and there's which is a quite
bitrotted attempt to turn parsing it into a shared library rather than
just a binary.

there's also a (internal but in the process of being open sourced)
implementation called 'errl' which is what has shipped on IBM FSP
systems forever (but that for whatever reason we ended up doing
opal-elog-parse rather than open sourcing it back in 2014).

>From hostboot, ./src/build/debug/ is the script that extracts
things from the BMC IIRC.

Now, there *is* a spec for the Platfrom Error Log format, which I have
previously tried to get out into the open... so I encourage you to find
all your IBM contacts and bug them about it.

That being said, I'm not convinced PEL is the right thing to continue to
exist. It's Yet Another Custom Binary Format, and there's probably
enough of those in the world as it is.

Stewart Smith
OPAL Architect, IBM.

More information about the openbmc mailing list