* IPMI SEL Parsing
@ 2021-03-25 12:49 rgrs
2021-03-25 22:16 ` Matt Spinler
0 siblings, 1 reply; 15+ messages in thread
From: rgrs @ 2021-03-25 12:49 UTC (permalink / raw)
To: openbmc
[-- Attachment #1: Type: text/plain, Size: 334 bytes --]
Hi All,
"ipmitool sel list" always shows the records as "Undetermined system hardware failure".
Logging/entry doesn't have the proper association. How do I add association for log entries and respective FRUs?
Which package creates Logging/entry object on sensor events? I don't see any call to SelAdd in phosphor-hwmon.
Thanks,
Raj
[-- Attachment #2: Type: text/html, Size: 442 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: IPMI SEL Parsing
2021-03-25 12:49 IPMI SEL Parsing rgrs
@ 2021-03-25 22:16 ` Matt Spinler
2021-03-25 22:29 ` Bruce Mitchell
0 siblings, 1 reply; 15+ messages in thread
From: Matt Spinler @ 2021-03-25 22:16 UTC (permalink / raw)
To: rgrs, openbmc
On 3/25/2021 7:49 AM, rgrs wrote:
> Hi All, "ipmitool sel list" always shows the records as "Undetermined
> system hardware failure". Logging/entry doesn't have the proper
> association. How do I add association for log entries and respective
> FRUs? Which package creates Logging/entry
> Hi All,
>
> "ipmitool sel list" always shows the records as "Undetermined system
> hardware failure".
> Logging/entry doesn't have the proper association. How do I add
> association for log entries and respective FRUs?
>
> Which package creates Logging/entry object on sensor events? I don't
> see any call to SelAdd in phosphor-hwmon.
What are the SELs for - threshold alarms, or some other sort of failures?
>
> Thanks,
> Raj
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: IPMI SEL Parsing
2021-03-25 22:16 ` Matt Spinler
@ 2021-03-25 22:29 ` Bruce Mitchell
2021-03-26 8:04 ` rgrs
0 siblings, 1 reply; 15+ messages in thread
From: Bruce Mitchell @ 2021-03-25 22:29 UTC (permalink / raw)
To: Matt Spinler, rgrs, openbmc
On 3/25/2021 15:16, Matt Spinler wrote:
>
>
> On 3/25/2021 7:49 AM, rgrs wrote:
>> Hi All, "ipmitool sel list" always shows the records as "Undetermined
>> system hardware failure". Logging/entry doesn't have the proper
>> association. How do I add association for log entries and respective
>> FRUs? Which package creates Logging/entry Hi All,
>>
>> "ipmitool sel list" always shows the records as "Undetermined system
>> hardware failure".
>> Logging/entry doesn't have the proper association. How do I add
>> association for log entries and respective FRUs?
>>
>> Which package creates Logging/entry object on sensor events? I don't
>> see any call to SelAdd in phosphor-hwmon.
>
> What are the SELs for - threshold alarms, or some other sort of failures?
>
>>
>> Thanks,
>> Raj
>
My assumption is that not everyone in the OpenBMC community has
extensive use with IPMI, thus this just to share information.
Sorry to those who already know this information and have been
using it for years.
This is share background as to the history or background of the
IPMI SEL; probably more information than you need. But I would
rather share 10% too much than be short by 0.1%.
From Intelligent Platform Management Interface Specification Second
Generation v2.0
Document Revision 1.1 October 1, 2013
31. System Event Log (SEL) Commands:
The System Event Log is a non-volatile repository for system events and
certain system configuration information. The device that fields the
commands to access the SEL is referred to as the System Event Log Device
or SEL Device.
Event Message information is normally written into the SEL after being
received by the Event Receiver functionality in the Event Receiver Device.
The SEL Device commands are structured in such a way that the SEL Device
could actually be separated from the Event Receiver Device. In which
case it would be the responsibility of the Event Receiver Device to send
the appropriate ‘Add SEL Entry’ message directly to the SEL Device, or
to pass the equivalent request through an intermediary.
SEL Entries have a unique ‘Record ID’ field. This field is used for
retrieving log entries from the SEL. SEL reading can be done in a
‘random access’ manner. That is, SEL Entries can be read in any order
assuming that the Record ID is known.
SEL Record IDs 0000h and FFFFh are reserved for functional use and are
not legal ID values. Record IDs are handles. They are not required to be
sequential or consecutive. Applications should not assume that SEL
Record IDs will follow any particular numeric ordering.
SEL Records are kept as an ordered list. That is, appending and deleting
individual entries does not change the access order of entries that
precede or follow the point of addition or deletion.
--
Bruce
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: IPMI SEL Parsing
2021-03-25 22:29 ` Bruce Mitchell
@ 2021-03-26 8:04 ` rgrs
2021-03-26 13:47 ` Bruce Mitchell
0 siblings, 1 reply; 15+ messages in thread
From: rgrs @ 2021-03-26 8:04 UTC (permalink / raw)
To: Bruce Mitchell; +Cc: openbmc, Matt Spinler
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).
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.)
2. Printing SELs: when I manually add logging/entry using busctl, ipmitool prints "Undetermined Hardware Failure".
(logging/entry/<number> is not having callout association to sensor/FRU)
Where/what should I configure so that SELs are generated and parsed properly?
Different pieces of IPMI functionality is scattered among various packages, I'm not able to stitch them together.
Thanks,
Raj
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, 26 March 2021 03:59, Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com> wrote:
> On 3/25/2021 15:16, Matt Spinler wrote:
>
> > On 3/25/2021 7:49 AM, rgrs wrote:
> >
> > > Hi All, "ipmitool sel list" always shows the records as "Undetermined
> > > system hardware failure". Logging/entry doesn't have the proper
> > > association. How do I add association for log entries and respective
> > > FRUs? Which package creates Logging/entry Hi All,
> > > "ipmitool sel list" always shows the records as "Undetermined system
> > > hardware failure".
> > > Logging/entry doesn't have the proper association. How do I add
> > > association for log entries and respective FRUs?
> > > Which package creates Logging/entry object on sensor events? I don't
> > > see any call to SelAdd in phosphor-hwmon.
> >
> > What are the SELs for - threshold alarms, or some other sort of failures?
> >
> > > Thanks,
> > > Raj
>
> My assumption is that not everyone in the OpenBMC community has
> extensive use with IPMI, thus this just to share information.
> Sorry to those who already know this information and have been
> using it for years.
>
> This is share background as to the history or background of the
> IPMI SEL; probably more information than you need. But I would
> rather share 10% too much than be short by 0.1%.
>
> From Intelligent Platform Management Interface Specification Second
> Generation v2.0
> Document Revision 1.1 October 1, 2013
>
> 31. System Event Log (SEL) Commands:
>
> The System Event Log is a non-volatile repository for system events and
> certain system configuration information. The device that fields the
> commands to access the SEL is referred to as the System Event Log Device
> or SEL Device.
>
> Event Message information is normally written into the SEL after being
> received by the Event Receiver functionality in the Event Receiver Device.
>
> The SEL Device commands are structured in such a way that the SEL Device
> could actually be separated from the Event Receiver Device. In which
> case it would be the responsibility of the Event Receiver Device to send
> the appropriate ‘Add SEL Entry’ message directly to the SEL Device, or
> to pass the equivalent request through an intermediary.
>
> SEL Entries have a unique ‘Record ID’ field. This field is used for
> retrieving log entries from the SEL. SEL reading can be done in a
> ‘random access’ manner. That is, SEL Entries can be read in any order
> assuming that the Record ID is known.
>
> SEL Record IDs 0000h and FFFFh are reserved for functional use and are
> not legal ID values. Record IDs are handles. They are not required to be
> sequential or consecutive. Applications should not assume that SEL
> Record IDs will follow any particular numeric ordering.
>
> SEL Records are kept as an ordered list. That is, appending and deleting
> individual entries does not change the access order of entries that
> precede or follow the point of addition or deletion.
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Bruce
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: IPMI SEL Parsing
2021-03-26 8:04 ` rgrs
@ 2021-03-26 13:47 ` Bruce Mitchell
2021-03-26 16:08 ` Bills, Jason M
0 siblings, 1 reply; 15+ messages in thread
From: Bruce Mitchell @ 2021-03-26 13:47 UTC (permalink / raw)
To: rgrs, Bills, Jason M; +Cc: openbmc, Matt Spinler
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).
>
>
> 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.)
>
> 2. Printing SELs: when I manually add logging/entry using busctl, ipmitool prints "Undetermined Hardware Failure".
> (logging/entry/<number> is not having callout association to sensor/FRU)
>
> Where/what should I configure so that SELs are generated and parsed properly?
> Different pieces of IPMI functionality is scattered among various packages, I'm not able to stitch them together.
>
> Thanks,
> Raj
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Friday, 26 March 2021 03:59, Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com> wrote:
>
>> On 3/25/2021 15:16, Matt Spinler wrote:
>>
>>> On 3/25/2021 7:49 AM, rgrs wrote:
>>>
>>>> Hi All, "ipmitool sel list" always shows the records as "Undetermined
>>>> system hardware failure". Logging/entry doesn't have the proper
>>>> association. How do I add association for log entries and respective
>>>> FRUs? Which package creates Logging/entry Hi All,
>>>> "ipmitool sel list" always shows the records as "Undetermined system
>>>> hardware failure".
>>>> Logging/entry doesn't have the proper association. How do I add
>>>> association for log entries and respective FRUs?
>>>> Which package creates Logging/entry object on sensor events? I don't
>>>> see any call to SelAdd in phosphor-hwmon.
>>>
>>> What are the SELs for - threshold alarms, or some other sort of failures?
>>>
>>>> Thanks,
>>>> Raj
>>
>> My assumption is that not everyone in the OpenBMC community has
>> extensive use with IPMI, thus this just to share information.
>> Sorry to those who already know this information and have been
>> using it for years.
>>
>> This is share background as to the history or background of the
>> IPMI SEL; probably more information than you need. But I would
>> rather share 10% too much than be short by 0.1%.
>>
>> From Intelligent Platform Management Interface Specification Second
>> Generation v2.0
>> Document Revision 1.1 October 1, 2013
>>
>> 31. System Event Log (SEL) Commands:
>>
>> The System Event Log is a non-volatile repository for system events and
>> certain system configuration information. The device that fields the
>> commands to access the SEL is referred to as the System Event Log Device
>> or SEL Device.
>>
>> Event Message information is normally written into the SEL after being
>> received by the Event Receiver functionality in the Event Receiver Device.
>>
>> The SEL Device commands are structured in such a way that the SEL Device
>> could actually be separated from the Event Receiver Device. In which
>> case it would be the responsibility of the Event Receiver Device to send
>> the appropriate ‘Add SEL Entry’ message directly to the SEL Device, or
>> to pass the equivalent request through an intermediary.
>>
>> SEL Entries have a unique ‘Record ID’ field. This field is used for
>> retrieving log entries from the SEL. SEL reading can be done in a
>> ‘random access’ manner. That is, SEL Entries can be read in any order
>> assuming that the Record ID is known.
>>
>> SEL Record IDs 0000h and FFFFh are reserved for functional use and are
>> not legal ID values. Record IDs are handles. They are not required to be
>> sequential or consecutive. Applications should not assume that SEL
>> Record IDs will follow any particular numeric ordering.
>>
>> SEL Records are kept as an ordered list. That is, appending and deleting
>> individual entries does not change the access order of entries that
>> precede or follow the point of addition or deletion.
>>
>> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>
>> Bruce
>
>
Adding Jason to the TO list. Any thoughts on this Jason?
--
Bruce
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: IPMI SEL Parsing
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
0 siblings, 2 replies; 15+ messages in thread
From: Bills, Jason M @ 2021-03-26 16:08 UTC (permalink / raw)
To: openbmc
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. We can use that thread to
resolve this signaling issue.
>>
>> 2. Printing SELs: when I manually add logging/entry using busctl,
>> ipmitool prints "Undetermined Hardware Failure".
>> (logging/entry/<number> is not having callout association to sensor/FRU)
>>
>> Where/what should I configure so that SELs are generated and parsed
>> properly?
>> Different pieces of IPMI functionality is scattered among various
>> packages, I'm not able to stitch them together.
>>
>> Thanks,
>> Raj
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> On Friday, 26 March 2021 03:59, Bruce Mitchell
>> <bruce.mitchell@linux.vnet.ibm.com> wrote:
>>
>>> On 3/25/2021 15:16, Matt Spinler wrote:
>>>
>>>> On 3/25/2021 7:49 AM, rgrs wrote:
>>>>
>>>>> Hi All, "ipmitool sel list" always shows the records as "Undetermined
>>>>> system hardware failure". Logging/entry doesn't have the proper
>>>>> association. How do I add association for log entries and respective
>>>>> FRUs? Which package creates Logging/entry Hi All,
>>>>> "ipmitool sel list" always shows the records as "Undetermined system
>>>>> hardware failure".
>>>>> Logging/entry doesn't have the proper association. How do I add
>>>>> association for log entries and respective FRUs?
>>>>> Which package creates Logging/entry object on sensor events? I don't
>>>>> see any call to SelAdd in phosphor-hwmon.
>>>>
>>>> What are the SELs for - threshold alarms, or some other sort of
>>>> failures?
>>>>
>>>>> Thanks,
>>>>> Raj
>>>
>>> My assumption is that not everyone in the OpenBMC community has
>>> extensive use with IPMI, thus this just to share information.
>>> Sorry to those who already know this information and have been
>>> using it for years.
>>>
>>> This is share background as to the history or background of the
>>> IPMI SEL; probably more information than you need. But I would
>>> rather share 10% too much than be short by 0.1%.
>>>
>>> From Intelligent Platform Management Interface Specification Second
>>> Generation v2.0
>>> Document Revision 1.1 October 1, 2013
>>>
>>> 31. System Event Log (SEL) Commands:
>>>
>>> The System Event Log is a non-volatile repository for system events and
>>> certain system configuration information. The device that fields the
>>> commands to access the SEL is referred to as the System Event Log Device
>>> or SEL Device.
>>>
>>> Event Message information is normally written into the SEL after being
>>> received by the Event Receiver functionality in the Event Receiver
>>> Device.
>>>
>>> The SEL Device commands are structured in such a way that the SEL Device
>>> could actually be separated from the Event Receiver Device. In which
>>> case it would be the responsibility of the Event Receiver Device to send
>>> the appropriate ‘Add SEL Entry’ message directly to the SEL Device, or
>>> to pass the equivalent request through an intermediary.
>>>
>>> SEL Entries have a unique ‘Record ID’ field. This field is used for
>>> retrieving log entries from the SEL. SEL reading can be done in a
>>> ‘random access’ manner. That is, SEL Entries can be read in any order
>>> assuming that the Record ID is known.
>>>
>>> SEL Record IDs 0000h and FFFFh are reserved for functional use and are
>>> not legal ID values. Record IDs are handles. They are not required to be
>>> sequential or consecutive. Applications should not assume that SEL
>>> Record IDs will follow any particular numeric ordering.
>>>
>>> SEL Records are kept as an ordered list. That is, appending and deleting
>>> individual entries does not change the access order of entries that
>>> precede or follow the point of addition or deletion.
>>>
>>> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>>
>>>
>>> Bruce
>>
>>
>
> Adding Jason to the TO list. Any thoughts on this Jason?
>
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: IPMI SEL Parsing
2021-03-26 16:08 ` Bills, Jason M
@ 2021-03-26 21:00 ` Andrew Jeffery
2021-03-28 2:51 ` Lei Yu
1 sibling, 0 replies; 15+ messages in thread
From: Andrew Jeffery @ 2021-03-26 21:00 UTC (permalink / raw)
To: openbmc
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
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: IPMI SEL Parsing
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
1 sibling, 1 reply; 15+ messages in thread
From: Lei Yu @ 2021-03-28 2:51 UTC (permalink / raw)
To: Bills, Jason M; +Cc: openbmc
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
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: IPMI SEL Parsing
2021-03-28 2:51 ` Lei Yu
@ 2021-03-29 15:36 ` rgrs
2021-03-30 2:08 ` Lei Yu
0 siblings, 1 reply; 15+ messages in thread
From: rgrs @ 2021-03-29 15:36 UTC (permalink / raw)
To: Lei Yu; +Cc: Bills, Jason M, openbmc
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>
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: IPMI SEL Parsing
2021-03-29 15:36 ` rgrs
@ 2021-03-30 2:08 ` Lei Yu
2021-04-01 12:56 ` rgrs
0 siblings, 1 reply; 15+ messages in thread
From: Lei Yu @ 2021-03-30 2:08 UTC (permalink / raw)
To: rgrs; +Cc: Bills, Jason M, openbmc
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
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: IPMI SEL Parsing
2021-03-30 2:08 ` Lei Yu
@ 2021-04-01 12:56 ` rgrs
2021-04-02 1:56 ` Lei Yu
0 siblings, 1 reply; 15+ messages in thread
From: rgrs @ 2021-04-01 12:56 UTC (permalink / raw)
To: Lei Yu; +Cc: Bills, Jason M, openbmc
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
My Config YAML files has only one sensor for now:
sp3-ipmi-inventory-sensors.yaml
-------------------------------
/xyz/openbmc_project/inventory/system:
eventReadingType: 111
offset: 2
sensorID: 144
sensorType: 18
/xyz/openbmc_project/inventory/system/chassis/motherboard:
eventReadingType: 3
offset: 0
sensorID: 140
sensorType: 199
/xyz/openbmc_project/inventory/system/chassis/motherboard/bmc:
eventReadingType: 0x01
offset: 0xFF
sensorID: 1
sensorType: 0x01
sp3-ipmi-sensors.yaml
---------------------
1:
sensorType: 0x01
entityID: 0x06
path: /xyz/openbmc_project/sensors/temperature/BMC_Temp
sensorReadingType: 0x01
unit: xyz.openbmc_project.Sensor.Value.Unit.DegreesC
scale: 0
offsetB: 0
bExp: 0
rExp: 0
mutability: Mutability::Write | Mutability::Read
serviceInterface: org.freedesktop.DBus.Properties
readingType: readingData
interfaces:
xyz.openbmc_project.Sensor.Value:
Value:
Offsets:
0xFF:
type: double
sp3-ipmi-fru.yaml
-----------------
0:
/system/chassis/motherboard/bmc:
entityID: 6
entityInstance: 1
interfaces:
xyz.openbmc_project.Inventory.Decorator.Asset:
BuildDate:
IPMIFruProperty: Mfg Date
IPMIFruSection: Board
SerialNumber:
IPMIFruProperty: Serial Number
IPMIFruSection: Board
PartNumber:
IPMIFruProperty: Part Number
IPMIFruSection: Board
Manufacturer:
IPMIFruProperty: Manufacturer
IPMIFruSection: Board
xyz.openbmc_project.Inventory.Item:
PrettyName:
IPMIFruProperty: Name
IPMIFruSection: Board
xyz.openbmc_project.Inventory.Decorator.Revision:
Version:
IPMIFruProperty: FRU File ID
IPMIFruSection: Board
associations.json – PIM recipe
------------------------------
[
{
"path": "system/chassis/motherboard",
"endpoints":
[
{
"types":
{
"rType": "inventory",
"fType": "sensors"
},
"paths":
[
"/xyz/openbmc_project/sensors/temperature/BMC_Temp"
]
}
]
},
{
"path": "system/chassis/motherboard/bmc",
"endpoints":
[
{
"types":
{
"rType": "inventory",
"fType": "sensors"
},
"paths":
[
"/xyz/openbmc_project/sensors/temperature/BMC_Temp"
]
}
]
},
{
"path": "system/chassis",
"endpoints":
[
{
"types":
{
"rType": "chassis",
"fType": "all_sensors"
},
"paths":
[
"/xyz/openbmc_project/sensors/temperature/BMC_Temp"
]
}
]
}
]
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, 30 March 2021 07:38, Lei Yu <yulei.sh@bytedance.com> wrote:
> 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
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: IPMI SEL Parsing
2021-04-01 12:56 ` rgrs
@ 2021-04-02 1:56 ` Lei Yu
2021-04-08 12:39 ` rgrs
0 siblings, 1 reply; 15+ messages in thread
From: Lei Yu @ 2021-04-02 1:56 UTC (permalink / raw)
To: rgrs; +Cc: Bills, Jason M, openbmc
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.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: IPMI SEL Parsing
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
0 siblings, 2 replies; 15+ messages in thread
From: rgrs @ 2021-04-08 12:39 UTC (permalink / raw)
To: Lei Yu; +Cc: Bills, Jason M, openbmc
Hi Lei,
I am still getting "undertermined system hardware failure" in ipmitool sel list. Do you have any platforms to refer to (in upstream)?
ipmitool sel also list only 10 logging entries and rotates after that. Is it expected?
-Raj
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, 2 April 2021 07:26, Lei Yu <yulei.sh@bytedance.com> wrote:
> 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.
^ permalink raw reply [flat|nested] 15+ messages in thread
* 回复:[External] Re: IPMI SEL Parsing
2021-04-08 12:39 ` rgrs
@ 2021-04-09 7:05 ` 许晓菡
2021-04-09 7:30 ` [External] " Lei Yu
1 sibling, 0 replies; 15+ messages in thread
From: 许晓菡 @ 2021-04-09 7:05 UTC (permalink / raw)
To: rgrs; +Cc: Bills, Jason M, Lei Yu, openbmc
[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]
You can set EXTRA_OECONF += "ERROR_INFO_CAP=1000" in
phpsphor-logging_%,bbappend file to modify the max sel num for ipmitool sel
list
于2021年4月8日 (周四) 20:39 <rgrs@protonmail.com> 写道:
Hi Lei, I am still getting "undertermined system hardware failure" in
ipmitool sel list. Do you have any platforms to refer to (in upstream)?
ipmitool sel also list only 10 logging entries and rotates after that. Is
it expected? -Raj ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, 2 April 2021
07:26, Lei Yu wrote: > 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.
[-- Attachment #2: Type: text/html, Size: 2744 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [External] Re: IPMI SEL Parsing
2021-04-08 12:39 ` rgrs
2021-04-09 7:05 ` 回复:[External] " 许晓菡
@ 2021-04-09 7:30 ` Lei Yu
1 sibling, 0 replies; 15+ messages in thread
From: Lei Yu @ 2021-04-09 7:30 UTC (permalink / raw)
To: rgrs; +Cc: Bills, Jason M, openbmc
On Thu, Apr 8, 2021 at 8:39 PM rgrs <rgrs@protonmail.com> wrote:
>
> Hi Lei,
>
> I am still getting "undertermined system hardware failure" in ipmitool sel list. Do you have any platforms to refer to (in upstream)?
We will try to upstream the related changed to
meta-bytedance/meta-g220a in the near future.
>
> ipmitool sel also list only 10 logging entries and rotates after that. Is it expected?
Please see Lotus Xu's reply, there is a configuration argument in
phpsphor-logging to set the max entries.
--
BRs,
Lei YU
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2021-04-09 7:31 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2021-04-08 12:39 ` rgrs
2021-04-09 7:05 ` 回复:[External] " 许晓菡
2021-04-09 7:30 ` [External] " Lei Yu
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).