All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com>
To: Matt Spinler <mspinler@linux.ibm.com>, rgrs <rgrs@protonmail.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: IPMI SEL Parsing
Date: Thu, 25 Mar 2021 15:29:14 -0700	[thread overview]
Message-ID: <5197cbe7-1a8b-80ab-2712-9a8f07457432@linux.vnet.ibm.com> (raw)
In-Reply-To: <0a6dd101-fbea-7fdf-b9a6-3895b48a7f47@linux.ibm.com>

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

  reply	other threads:[~2021-03-25 22:29 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 [this message]
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

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=5197cbe7-1a8b-80ab-2712-9a8f07457432@linux.vnet.ibm.com \
    --to=bruce.mitchell@linux.vnet.ibm.com \
    --cc=mspinler@linux.ibm.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.