From: rgrs <rgrs@protonmail.com>
To: Lei Yu <yulei.sh@bytedance.com>
Cc: "Bills, Jason M" <jason.m.bills@linux.intel.com>,
openbmc <openbmc@lists.ozlabs.org>
Subject: Re: IPMI SEL Parsing
Date: Mon, 29 Mar 2021 15:36:49 +0000 [thread overview]
Message-ID: <axfftQgj4Du8QvWHD4CHEuPSLSJGtLZZTzpZplCpN1Mu63yr4Xm1RiZTuewl3CNqPUZ8mrmZdJsEJUOQiL39Ft64mfW7DzBdLrkDLhylGiY=@protonmail.com> (raw)
In-Reply-To: <CAGm54UEc9DOGZS0LLhFMP4SNw_-sJ2oa146wXfYvmF3As4xXsQ@mail.gmail.com>
Hi Lei,
Thanks, phosphor-sel-logger logs to phosphor-logging after enabling SEL_LOGGER_SEND_TO_LOGGING_SERVICE.
The APIs IpmiSelAdd() adds entry to SELs (tested using busctl)
But, "ipmitool sel list" doesn't print correctly. It prints "Undetermined Hardware Failure" for these entries.
Thanks,
Raj
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, 28 March 2021 08:21, Lei Yu <yulei.sh@bytedance.com> wrote:
> On Sat, Mar 27, 2021 at 12:08 AM Bills, Jason M
> jason.m.bills@linux.intel.com wrote:
>
> > On 3/26/2021 6:47 AM, Bruce Mitchell wrote:
> >
> > > On 3/26/2021 01:04, rgrs wrote:
> > >
> > > > Hi Matt, Bruce,
> > > > Yes, SELs for sensor events, threshold alarms.
> > > > When a sensor value is beyond the range of thresholds, we need to log
> > > > the SEL.
> > > > My understanding of OpenBMC implementation:
> > > > dbus-sensors/phosphor-hwmon logs d-bus errors (logging/entry).
> > > > Each entry object has a "callout", that is used by phosphor-ipmi-host
> > > > to convert dbus-error logs to IPMI SEL (16 bytes).
> > > > Please note that there are two locations that SEL entries can be logged:
> >
> > 1. D-Bus
> > 2. Journal/syslog
> >
> > It looks like you are using D-Bus which I'm not familiar with.
>
> phosphor-sel-logger now supports either, by default it logs to syslog;
> With SEL_LOGGER_SEND_TO_LOGGING_SERVICE enabled, it logs to
> phosphor-logging which is on D-Bus.
>
> You could call the same APIs ("IpmiSelAdd", "IpmiSelAddOem") to create SEL logs.
>
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> BRs,
> Lei YU
</yulei.sh@bytedance.com>
next prev parent reply other threads:[~2021-03-29 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 12:49 IPMI SEL Parsing rgrs
2021-03-25 22:16 ` Matt Spinler
2021-03-25 22:29 ` Bruce Mitchell
2021-03-26 8:04 ` rgrs
2021-03-26 13:47 ` Bruce Mitchell
2021-03-26 16:08 ` Bills, Jason M
2021-03-26 21:00 ` Andrew Jeffery
2021-03-28 2:51 ` Lei Yu
2021-03-29 15:36 ` rgrs [this message]
2021-03-30 2:08 ` Lei Yu
2021-04-01 12:56 ` rgrs
2021-04-02 1:56 ` Lei Yu
2021-04-08 12:39 ` rgrs
2021-04-09 7:05 ` 回复：[External] " 许晓菡
2021-04-09 7:30 ` [External] " Lei Yu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='axfftQgj4Du8QvWHD4CHEuPSLSJGtLZZTzpZplCpN1Mu63yr4Xm1RiZTuewl3CNqPUZ8mrmZdJsEJUOQiL39Ft64mfW7DzBdLrkDLhylGiY=@protonmail.com' \
--to=rgrs@protonmail.com \
--cc=jason.m.bills@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=yulei.sh@bytedance.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.