search

ibm-openbmc / dev

Product Development Project Mgmt and Tracking
16 stars 2 forks source link

Checkstop Management #218

Closed ojayanth closed 5 years ago

ojayanth commented 5 years ago

BMC need to provide checkstop monitor and analysis functions also need to support log error and service action related to this. Checkstop Flow:    - BMC monitors the checkstop via fsi attention pin ( combined TI checkstop pin).    - BMC issue SBE chip-ops to collect the processor specific FIR data.    - SBE collects functional chiplets  FIR data.                 -  SBE  utilize the Targeting data abstracted from BMC for this purpose.                          -  During boot HB provides chiplets and gardable units info to SBE.                         -  SBE creates  chipletlevel Target Map ,                          - Also collects I2C related buses OCMB  data.    - SBE package( SCOMS, FIR,CE info and associated gardable /callout units information) this data and send to BMC. BMC creates self contained data file.    - BMC checkstop application (PRD)  analysis this data based on the rule file( created at build time based on MRW).    - BMC create Error log and  service action based on gard/callout info provided by SBE in the target map and initiate reboot if required.    -SBE should handle the collection errors during read operation by providing a communication mechanism to inform BMC about failure.     -Need to avoid data dependency in SBE code load and checkstop analysis code load.    -Gard -Deconfigure:  No deconfigure required for checkstop path .        -BMC should set gard records to deconfigure/  inform SBE to not use as master core in the next boot

ojayanth commented 5 years ago

No activity here now. closing this epic.