Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

POZ: To cater for additional requirements to parse SBE FFDC data #92

Merged
merged 2 commits into from
Apr 16, 2024

Conversation

devenrao
Copy link
Contributor

  1. Modify sbe chip-op operation to read FFDC data for chip-op success case so as to get FFDC data from SBE for any earlier or internal SBE failure

  2. As SBE now caters for multiple FFDC packets increase the size of the memory allocated by pdbg to read the FFDC data to 32KB.

Copy link
Contributor

@Swarnendu-R-C Swarnendu-R-C left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the first commit message the description text should start with capital T i.e.; to cater for... to To cater for... (A typo only I guess). Otherwise looks good to me

libsbefifo/operation.c Outdated Show resolved Hide resolved
@devenrao devenrao force-pushed the oper branch 2 times, most recently from f386c5e to 297676e Compare March 27, 2024 08:23
Copy link
Contributor

@Swarnendu-R-C Swarnendu-R-C left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A small suggestion

libsbefifo/operation.c Show resolved Hide resolved
@devenrao devenrao changed the title POZ: cater for additional requirements to parse SBE FFDC data POZ: To cater for additional requirements to parse SBE FFDC data Apr 8, 2024
To cater for new requirement where ffdc data is queried
even after chip-op success, this is to fetch any traces
or non critical sbe internal failures queued by SBE.

modified ffdc method to not to dereference ffdc pointer
if there is no data set rather simply return length as zero.

caller upon receiving ffdc length as zero for success case
will not create any PEL's

Tested
ENTER OPER: sbefifo_parse_output buflen 0x00004EE4
OPER: reply: cmd=0000aa01, len=20196, status=00000000
buflen=00004ee4, offset00004ee0 *out_len00004ed8
buflen=00004ee4, *out_len00004ed8
EXIT OPER: sbefifo_parse_output buflen 0x00004EE4
EXIT OPER: sbefifo_operation
collectdump[1209]: Collect dump from (ocmb)(2) path(/tmp) id(1) type(1) clock(1) failingUnit(2)
phosphor-log-manager[364]: SBE FFDC processing requested
phosphor-log-manager[364]: SBE FFDC file fd:(8), parsing started
phosphor-log-manager[364]: P0Z FFDC magic: 64429 length in words:151 Fapirc:33554433
phosphor-log-manager[364]: SBE FFDC: Internal FFDC packet
phosphor-log-manager[364]: Created PEL 0x50005d00 (BMC ID 1356) with SRC BD20F401

Signed-off-by: Marri Devender Rao <[email protected]>
Change-Id: I1ba80a35e174935560b9ba6232394cea2644b8d7
For POZ SBE can queue n number of FFDC packets till the
maximum size is reached, modified to read upto 32KB of data.

Change-Id: I3a73a605119968645e87154e91bfff0d3c4842d5
Signed-off-by: Marri Devender Rao <[email protected]>
@aravynd aravynd merged commit dd4d428 into open-power:master Apr 16, 2024
1 check passed
@devenrao devenrao deleted the oper branch November 28, 2024 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants