You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present core D-bus objects are hosted by PLDM, so when a core is guarded openpower-hw-isolation calls PLDM to enable the D-Bus property of the core, as there are some cases when PLDM gets stuck and does not honor the enabled property causing time-out errors.
At present hw-isolation will not create the guard record for core when the error is injected if setEnabled D-Bus call to PLDM fails.
Now modifying to goahead and create the guard record even if the setEnabled D-Bus call to PLDM fails, drawback with this approach is core will be guarded but it will not be shown in GUI.
This issue is not easily reproducible so going with this approach.
In power11 core D-bus objects might be moved to entity manager during that time this hack needs to be removed.
The text was updated successfully, but these errors were encountered:
At present core D-bus objects are hosted by PLDM, so when a core is guarded openpower-hw-isolation calls PLDM to enable the D-Bus property of the core, as there are some cases when PLDM gets stuck and does not honor the enabled property causing time-out errors.
https://w3.rchland.ibm.com/projects/bestquest/?defect=SW554144 - item 18
/xyz/openbmc_project/inventory/system/chassis/motherboard/dcm0/cpu1/core14
At present hw-isolation will not create the guard record for core when the error is injected if setEnabled D-Bus call to PLDM fails.
Now modifying to goahead and create the guard record even if the setEnabled D-Bus call to PLDM fails, drawback with this approach is core will be guarded but it will not be shown in GUI.
This issue is not easily reproducible so going with this approach.
In power11 core D-bus objects might be moved to entity manager during that time this hack needs to be removed.
The text was updated successfully, but these errors were encountered: