From: "Andrew Jeffery" <andrew@aj.id.au>
To: openbmc@lists.ozlabs.org
Subject: Re: IPMI SEL Parsing
Date: Sat, 27 Mar 2021 07:30:47 +1030 [thread overview]
Message-ID: <7cce5f73-e7f5-4d3a-8b79-c8dc65059813@beta.fastmail.com> (raw)
In-Reply-To: <36bafa0b-5dd3-6da5-b18d-847ee4a46459@linux.intel.com>
On Sat, 27 Mar 2021, at 02:38, Bills, Jason M 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.
>
> >>
> >>
> >> The issue I am facing:
> >> 1. SEL creation: when I change sensor thresholds, I don't see a log
> >> generated for that sensor.
> >> (phosphor-sel-logger has the capability to monitor threshold events
> >> and log SEL. But phosphor-hwmon doesn't generate the signal that
> >> phosphor-sel-logger is looking for.)
> There is another thread on the mailing list that is discussing this
> issue: Question of phosphor-sel-logger.
Note that we have the list archived on https://lore.kernel.org/ at https://lore.kernel.org/openbmc and this is a great way to identify other posts :)
> We can use that thread to
> resolve this signaling issue.
Looks like it's
https://lore.kernel.org/openbmc/TY2PR04MB3712DCE11C578706F5F6401F88639@TY2PR04MB3712.apcprd04.prod.outlook.com/
Andrew
next prev parent reply other threads:[~2021-03-26 21:01 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 [this message]
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
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=7cce5f73-e7f5-4d3a-8b79-c8dc65059813@beta.fastmail.com \
--to=andrew@aj.id.au \
--cc=openbmc@lists.ozlabs.org \
/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).