From: Patrick Williams <patrick@stwcx.xyz>
To: Stewart Smith <stewart@linux.vnet.ibm.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: FFDC tool?
Date: Wed, 26 Jul 2017 22:45:42 -0500 [thread overview]
Message-ID: <20170727034542.GA14987@asimov> (raw)
In-Reply-To: <87bmo6sp6k.fsf@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
On Thu, Jul 27, 2017 at 10:23:31AM +1000, Stewart Smith wrote:
> So, I spotted https://gerrit.openbmc-project.xyz/#/c/4881/ (well, an
> associated internal bug report), and it appears there is a FFDC tool in
> existence?
>
> (FFDC seems like a bit of an IBM specific term, First Failure Data
> Capture - i.e. gather all the things when something goes wrong and
> attach it to a bug report)
>
> I'm wondering where I missed any announce/info on its availability and
> use?
It has been around since January. Not sure we announced it specifically
anywhere. It was something quickly thrown together by one of the
members of the automated test team to help them facilitate gathering
some data for automated test failures.
Jayanth is working on a fairly large revamp of this so we can handle
capturing different data for both core dumps and user-initiated data
collection.
He started a discussion on it back in May but did not get any feedback:
https://lists.ozlabs.org/pipermail/openbmc/2017-May/007654.html
>
> Perhaps an idea would be to put it in the motd and/or /etc/issue(.net)
> so that it's prominently documented (we do this for petitboot for
> OpenPOWER host firmware, and I think that helps)?
We should probably revisit this after the new API is complete.
--
Patrick Williams
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-07-27 3:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 0:23 FFDC tool? Stewart Smith
2017-07-27 3:45 ` Patrick Williams [this message]
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=20170727034542.GA14987@asimov \
--to=patrick@stwcx.xyz \
--cc=openbmc@lists.ozlabs.org \
--cc=stewart@linux.vnet.ibm.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.