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: Fri, 2 Apr 2021 09:56:11 +0800 [thread overview]
Message-ID: <CAGm54UFX9LPHArj-2q=w2pNtwgpkjZJE_0Dgd3_8cXB9z3L2vQ@mail.gmail.com> (raw)
In-Reply-To: <2FVxBtO4gLzVYqZqGL8XwOcI2a_r6x0CaPGmGozxe_VeNp3Y3y05vSntyZPvfn4EDRsHsLjWJnrVSzbeeVDKhPvLILmFKB3hw-MFaEvepAw=@protonmail.com>
On Thu, Apr 1, 2021 at 8:56 PM rgrs <rgrs@protonmail.com> wrote:
>
> Hi Lei,
>
>
>
> Is FRU EEPROM required for inventory to work? My board has unprogrammed EEPROM.
>
> I constructed the busctl command according as below, I still get “Undetermined Hardware Failure”. Please can you let me know if my config YAML has any issues?
>
>
> # busctl call "xyz.openbmc_project.Logging.IPMI" "/xyz/openbmc_project/Logging/IPMI" xyz.openbmc_project.Logging.IPMI IpmiSelAdd ssaybq "Sensor message" /xyz/openbmc_project/sensors/temperature/BMC_Temp 3 0x01 0xFF 0xFF true 0x20
You need to put /xyz/openbmc_project/sensors/temperature/BMC_Temp into
sp3-ipmi-inventory-sensors.yaml as well to make ipmid to know how to
map the dbus path to the sensor id in the sel.
next prev parent reply other threads:[~2021-04-02 1:56 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
2021-04-01 12:56 ` rgrs
2021-04-02 1:56 ` Lei Yu [this message]
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='CAGm54UFX9LPHArj-2q=w2pNtwgpkjZJE_0Dgd3_8cXB9z3L2vQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).