From: Lei YU <mine260309@gmail.com>
To: "George Hung (洪忠敬)" <George.Hung@quantatw.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"yulei.sh@bytedance.com" <yulei.sh@bytedance.com>,
"Fran Hsu (徐誌謙)" <Fran.Hsu@quantatw.com>,
"Brandon Kim" <brandonkim@google.com>
Subject: Re: IPMI SEL logs from phosphor-logging
Date: Thu, 24 Jun 2021 16:50:31 +0800 [thread overview]
Message-ID: <CAARXrtmf2S+oma1_60=pkHCEMFBAxFP4dSVSnR6Nqurt1PFEgg@mail.gmail.com> (raw)
In-Reply-To: <HK0PR04MB23393424624A1F752D3BDAAB8F079@HK0PR04MB2339.apcprd04.prod.outlook.com>
On Thu, Jun 24, 2021 at 1:21 PM George Hung (洪忠敬)
<George.Hung@quantatw.com> wrote:
>
> Hi Lei,
>
> I enable SEL_LOGGER_SEND_TO_LOGGING_SERVICE option for phosphor-sel-logger and then would generate IPMI SEL logs from phosphor-logging successfully.
>
> But the phosphor-logging still has other events issued from elog function and also put them in the "/var/lib/phosphor-logging/errors" directory.
>
> For example:
>
> 00000000 03 00 00 00 03 00 00 00 03 00 00 00 67 ff e6 38 |............g..8|
> 00000010 7a 01 00 00 32 00 00 00 00 00 00 00 78 79 7a 2e |z...2.......xyz.|
> 00000020 6f 70 65 6e 62 6d 63 5f 70 72 6f 6a 65 63 74 2e |openbmc_project.|
> 00000030 43 65 72 74 73 2e 45 72 72 6f 72 2e 49 6e 76 61 |Certs.Error.Inva|
> 00000040 6c 69 64 43 65 72 74 69 66 69 63 61 74 65 01 00 |lidCertificate..|
> 00000050 00 00 00 00 00 00 09 00 00 00 00 00 00 00 5f 50 |.............._P|
> 00000060 49 44 3d 38 37 35 34 00 00 00 00 00 00 00 00 00 |ID=8754.........|
> 00000070 19 00 00 00 00 00 00 00 76 33 2e 37 2e 30 2d 34 |........v3.7.0-4|
> 00000080 2d 67 66 32 36 39 36 39 66 64 34 2d 64 69 72 74 |-gf26969fd4-dirt|
> 00000090 79 67 ff e6 38 7a 01 00 00 |yg..8z...|
> 00000099
>
> This event type is not IPMI System/OEM SEL, so "ipmitool sel elist" would result in the unspecified error:
>
> # ipmitool sel elist
> Get SEL Entry 0 command failed: Unspecified error
> Get SEL Entry 0 command failed: Unspecified error
>
> How do you deal with these events that not belong to IPMI SEL logs ?
Such logs are mapped to the system sensor as "Undetermined system
hardware failure".
e.g.
23 | 06/21/2021 | 06:26:35 | System Event #0xf0 | Undetermined
system hardware failure | Asserted
See https://github.com/openbmc/phosphor-host-ipmid/blob/master/selutility.cpp#L365
for details.
So you need to define the inventory sensor of
"/xyz/openbmc_project/inventory/system" in the system's
ipmi-inventory-sensors.yaml, then such events could be mapped to this
inventory if there is no CALLOUT or no SEL metadata in the logging
entry.
next prev parent reply other threads:[~2021-06-24 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 5:20 IPMI SEL logs from phosphor-logging George Hung (洪忠敬)
2021-06-24 8:50 ` Lei YU [this message]
2021-06-24 10:32 ` George Hung (洪忠敬)
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='CAARXrtmf2S+oma1_60=pkHCEMFBAxFP4dSVSnR6Nqurt1PFEgg@mail.gmail.com' \
--to=mine260309@gmail.com \
--cc=Fran.Hsu@quantatw.com \
--cc=George.Hung@quantatw.com \
--cc=brandonkim@google.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 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).