pHAL SCOM ( BMC native) failure handling

ibm-openbmc / dev

Product Development Project Mgmt and Tracking

16 stars 2 forks source link

pHAL SCOM ( BMC native) failure handling #692

Closed ojayanth closed 1 year ago

ojayanth commented 5 years ago

BMC native scom failure Debug data info in the error log.

ojayanth commented 3 years ago

BMC Native SCOM ( SBE Dump use case only)
- Callout end point and bus path
- SCOM should fail if Clock’s are off.
  - SBE Dump procedure need to include pre-check
    - Check SBE pervasive clock’s are on and SBE CBS engine started.
    - Return appropriate error rc’s based on type of pre-check failures
    - Callout details need to update based on the error type.

ojayanth commented 3 years ago

SBE HWP team agreed to get required pr-check support in the SBE dump specific hwp's . Out look is May end 2021.

ojayanth commented 3 years ago

@rsnair is going to update issue owner. required for dec-15.

ojayanth commented 2 years ago

BMC native scom is only used by sbe dump hardware procedure. Since sump is taken onlly in error path also existing dump flow ignores the errors and collects data with best available approach. Considering this use the best approch is to keep log file to capture all failures and package as part of sbe dump. This approch will help dump users to know the failure reason.s @dhruvibm

ojayanth commented 2 years ago

Since this is considering as double failure moving milestone to cec-management advaned functions and backlog #3382

rfrandse commented 1 year ago

tracking in jira