From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Rob Lippert <rlippert@google.com>
Cc: "Tanous\, Ed" <ed.tanous@intel.com>,
Brad Bishop <bradleyb@fuzziesquirrel.com>,
Patrick Venture <venture@google.com>,
"Mohit Gupta \(QDT\)" <guptam@qti.qualcomm.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Exposing POST codes
Date: Tue, 13 Mar 2018 17:48:19 +1100 [thread overview]
Message-ID: <87y3iwo4i4.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAFRv3ww59TrnRBWAKZu4LEc5V2iaSW03MEZQgQw6Yrymqt9Meg@mail.gmail.com>
Rob Lippert <rlippert@google.com> writes:
> I implemented port 80h POST codes for POWER9 hostboot a while back:
> https://github.com/open-power/hostboot/blob/c93bef31ae6ce781f9e0a11bb9224b6728ff120f/src/usr/initservice/istepdispatcher/istepdispatcher.C#L2312
>
> On Zaius machines we are using that support with Patrick's snoop daemon and
> a separate daemon that receives the code via dbus and outputs it over the
> front 7seg debug display.
> It has proven useful for getting early error/debug reports from technicians
> at scale e.g. "5 machines stopped at code 35h, 2 at 72h" provides a quick
> overview of what the problems are for me to debug further (since I have the
> decoder ring, and the istep names would be useless to them anyways).
Neat!
Anything we should add to skiboot or petitboot environment for this? Or
do we not fail in IPL enough to warrant it?
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2018-03-13 6:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 18:56 Exposing POST codes Patrick Venture
2018-03-01 17:31 ` Patrick Venture
2018-03-05 5:19 ` Brad Bishop
2018-03-05 21:34 ` Tanous, Ed
2018-03-05 21:35 ` Patrick Venture
2018-03-06 1:05 ` Stewart Smith
2018-03-07 1:05 ` Rob Lippert
2018-03-13 6:48 ` Stewart Smith [this message]
2018-03-26 22:57 ` Rob Lippert
2018-04-03 6:08 ` Stewart Smith
2018-03-06 1:06 ` Brad Bishop
2018-04-14 0:47 ` Timothy Pearson
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=87y3iwo4i4.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=ed.tanous@intel.com \
--cc=guptam@qti.qualcomm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=rlippert@google.com \
--cc=venture@google.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.