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

Revert index commit #100

Closed

Conversation

deepakala-k
Copy link
Contributor

No description provided.

devenrao and others added 5 commits September 18, 2024 04:58
Revert change done to avoid double memory allocation for ffdc
data.

Earlier test was done with single proc which worked as expected
but with multiple proc and multiple fork processes trying to
read the ffdc data it is causing double free error and core dump.

Tested:
root@p10bmc:/tmp# busctl tree xyz.openbmc_project.Dump.Manager
`- /xyz
  `- /xyz/openbmc_project
    `- /xyz/openbmc_project/dump
      |- /xyz/openbmc_project/dump/hostboot
      | `- /xyz/openbmc_project/dump/hostboot/entry
      |   |- /xyz/openbmc_project/dump/hostboot/entry/20000001
      |   |- /xyz/openbmc_project/dump/hostboot/entry/20000002
      |   |- /xyz/openbmc_project/dump/hostboot/entry/20000003

Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
Change-Id: If38be58d9938b476ab39f35e69583fda28522cd4
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
Fixing CI error Conditional jump or move depends on uninitialised value

Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
In contains_substring_ignoring_case method, if the string that we are
looking for is longer than the source string, return with string not
found.  Earlier the char array index went out of bounds due to invalid
arthimetic operation on the index.

Tested and found the method working as expected.

Signed-off-by: deepakala-k <deepakala.karthikeyan@ibm.com>
The index values of pdbg targets are updated to match the physical
device path. So using the index value for getting the scoms shall fail.
The fapi position is still connected to the OMI index. So using the fapi
position to calculate the instance id in case of DDR4 system.

Tested Results:
root@p10bmc:/tmp# getscom explorer 08012400 -all
explorer        k0:n0:s0:p00       0x0000000000000000
explorer        k0:n0:s0:p01       0x0000000000000000
explorer        k0:n0:s0:p24       0x0000000000000000
explorer        k0:n0:s0:p25       0x0000000000000000
explorer        k0:n0:s0:p32       0x0000000000000000
explorer        k0:n0:s0:p33       0x0000000000000000
explorer        k0:n0:s0:p56       0x0000000000000000
explorer        k0:n0:s0:p57       0x0000000000000000
/usr/bin/edbg getscom explorer 08012400 -all

root@p10bmc:/tmp# getscom explorer 8012810 -all
explorer        k0:n0:s0:p00       0x8122640700112820
explorer        k0:n0:s0:p01       0x8122640700112820
explorer        k0:n0:s0:p24       0x8122640700112820
explorer        k0:n0:s0:p25       0x8122640700112820
explorer        k0:n0:s0:p32       0x8122640700112820
explorer        k0:n0:s0:p33       0x8122640700112820
explorer        k0:n0:s0:p56       0x8122640700112820
explorer        k0:n0:s0:p57       0x8122640700112820
/usr/bin/edbg getscom explorer 8012810 -all
@deepakala-k
Copy link
Contributor Author

Not needed anymore. Using git revert raised another PR

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.

3 participants