dreport will replace ffdc tool starting from Feb-2018.

dreport will replace ffdc tool starting from Feb-2018.

[Jayanth Othayoth]

[-- Attachment #1: Type: text/plain, Size: 2235 bytes --]

Starting feb-2018 ffdc tool will be removed from openbmc builds. dreport
will replace ffdc tool with support for additional features.  dreport is
already available in openbmc builds.

Users of ffdc tool must plan to migrate to dreport.

dreport is  a drop-in replacement for ffdc.  ie run dreport instead of
ffdc.

Usage info is as follows.

        dreport creates an archive(xz compressed) consisting of the
following:
                * Configuration information
                * Debug information
                * A summary report
        The type parameter controls the content of the data. The generated
        archive is stored in the user specified location.

usage: dreport [OPTION]

Options:
        -n, —-name <name>     Name to be used for the archive.
                              Default name format obmcdump_<id>_<epochtime>
        -d, —-dir <directory> Archive directory to copy the compressed
report.
                              Default output directory is /tmp
        -i, —-id <id>         Dump identifier to associate with the archive.
                              Identifiers include numeric characters.
                              Default dump identifier is 0
        -t, —-type <type>     Data collection type. Valid types are
                              user, core, elog.
                              Default type is user initiated.
        -p, —-path <path>     Optional contents to be included in the
archive.
                              Valid paths are absolute file path or d-bus
path
                              based on type parameter.
                                 -Absolute file path for core type.
                                 -elog d-bus object for elog type.
        -s, --size <size>     Maximum allowed size(in KB) of the archive.
                              Report will be truncated in case size exceeds
                              this limit. Default size is unlimited.
        -v, —-verbose         Increase logging verbosity.
        -V, --version         Output version information.
        -q, —-quiet           Only log fatal errors to stderr
        -h, —-help            Display this help and exit.

[-- Attachment #2: Type: text/html, Size: 2943 bytes --]

Re: dreport will replace ffdc tool starting from Feb-2018.

[Stewart Smith]

Jayanth Othayoth <ojayanth@gmail.com> writes:
> Starting feb-2018 ffdc tool will be removed from openbmc builds. dreport
> will replace ffdc tool with support for additional features.  dreport is
> already available in openbmc builds.
>
> Users of ffdc tool must plan to migrate to dreport.
>
> dreport is  a drop-in replacement for ffdc.  ie run dreport instead of
> ffdc.

For ease of use, a shell alias would be appreciated. Old habits die hard :)

-- 
Stewart Smith
OPAL Architect, IBM.

Re: dreport will replace ffdc tool starting from Feb-2018.

[Jayanth Othayoth]

[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]

FFDC tool in the OpenBMC builds is already modified to use dreport as the
back-end for capturing debug data.

dreport can be invoked directly with various switches for additional
options.

As you mentioned FFDC tool can be made to be a shell alias or a soft link
to dreport. This would enable to invoke FFDC tool in a same way as dreport
with all switches.

Jayanth Othayoth
Firmware Developer, IBM.


On Fri, Dec 15, 2017 at 10:05 AM, Stewart Smith <stewart@linux.vnet.ibm.com>
wrote:

> Jayanth Othayoth <ojayanth@gmail.com> writes:
> > Starting feb-2018 ffdc tool will be removed from openbmc builds. dreport
> > will replace ffdc tool with support for additional features.  dreport is
> > already available in openbmc builds.
> >
> > Users of ffdc tool must plan to migrate to dreport.
> >
> > dreport is  a drop-in replacement for ffdc.  ie run dreport instead of
> > ffdc.
>
> For ease of use, a shell alias would be appreciated. Old habits die hard :)
>
> --
> Stewart Smith
> OPAL Architect, IBM.
>
>

[-- Attachment #2: Type: text/html, Size: 1598 bytes --]

Re: dreport will replace ffdc tool starting from Feb-2018.

[Joel Stanley]

On Thu, Dec 14, 2017 at 7:53 PM, Jayanth Othayoth <ojayanth@gmail.com> wrote:
> Starting feb-2018 ffdc tool will be removed from openbmc builds. dreport
> will replace ffdc tool with support for additional features.  dreport is
> already available in openbmc builds.
>
> Users of ffdc tool must plan to migrate to dreport.
>
> dreport is  a drop-in replacement for ffdc.  ie run dreport instead of ffdc.
>
> Usage info is as follows.
>
>         dreport creates an archive(xz compressed) consisting of the
> following:
>                 * Configuration information
>                 * Debug information

Cool. What information is currently included? Is there a list or
configuration I can view?

Is the list fixed at build time, or can the user configure their BMC
to collect additional (or less!) data from specified sources?

How do we get include extra information included?

>                 * A summary report
>         The type parameter controls the content of the data. The generated
>         archive is stored in the user specified location.
>
> usage: dreport [OPTION]
>
> Options:
>         -n, —-name <name>     Name to be used for the archive.
>                               Default name format obmcdump_<id>_<epochtime>

Can we change this to include the hostname?

Cheers,

Joel

>         -d, —-dir <directory> Archive directory to copy the compressed
> report.
>                               Default output directory is /tmp
>         -i, —-id <id>         Dump identifier to associate with the archive.
>                               Identifiers include numeric characters.
>                               Default dump identifier is 0
>         -t, —-type <type>     Data collection type. Valid types are
>                               user, core, elog.
>                               Default type is user initiated.
>         -p, —-path <path>     Optional contents to be included in the
> archive.
>                               Valid paths are absolute file path or d-bus
> path
>                               based on type parameter.
>                                  -Absolute file path for core type.
>                                  -elog d-bus object for elog type.
>         -s, --size <size>     Maximum allowed size(in KB) of the archive.
>                               Report will be truncated in case size exceeds
>                               this limit. Default size is unlimited.
>         -v, —-verbose         Increase logging verbosity.
>         -V, --version         Output version information.
>         -q, —-quiet           Only log fatal errors to stderr
>         -h, —-help            Display this help and exit.