All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lei Yu <yulei.sh@bytedance.com>
To: rgrs <rgrs@protonmail.com>
Cc: "Bills, Jason M" <jason.m.bills@linux.intel.com>,
	openbmc <openbmc@lists.ozlabs.org>
Subject: Re: IPMI SEL Parsing
Date: Tue, 30 Mar 2021 10:08:59 +0800	[thread overview]
Message-ID: <CAGm54UHGr+F-vnO69PLr0MN699BDEDsZiHYoX1WPmF1DZnQLVw@mail.gmail.com> (raw)
In-Reply-To: <axfftQgj4Du8QvWHD4CHEuPSLSJGtLZZTzpZplCpN1Mu63yr4Xm1RiZTuewl3CNqPUZ8mrmZdJsEJUOQiL39Ft64mfW7DzBdLrkDLhylGiY=@protonmail.com>

On Mon, Mar 29, 2021 at 11:37 PM rgrs <rgrs@protonmail.com> wrote:
>
> 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.

You need to define the inventory-sensor yaml for ipmid so that it
knows how to map the sensor id to inventories.
Then ipmid will construct the expected sel data.
See details in https://github.com/openbmc/phosphor-host-ipmid/blob/master/selutility.cpp#L149

-- 
BRs,
Lei YU

  reply	other threads:[~2021-03-30  2:09 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
2021-03-30  2:08               ` Lei Yu [this message]
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=CAGm54UHGr+F-vnO69PLr0MN699BDEDsZiHYoX1WPmF1DZnQLVw@mail.gmail.com \
    --to=yulei.sh@bytedance.com \
    --cc=jason.m.bills@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=rgrs@protonmail.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.