Searched hist:edd211e4 (Results 1 – 2 of 2) sorted by relevance
/openbmc/x86-power-control/config/ |
H A D | power-config-host0.json | edd211e4 Fri Oct 28 06:10:16 CDT 2022 Michal Orzel <michalx.orzel@intel.com> Handle possible SdBus exceptions
Right now service allows to access several signals using DBus interface, instead of GPIO pins. In case of that option selected in config, service will try to read given DBus property using function getProperty. Unfortunately that attempt might fail, for example when that specific object doesn't exist yet, which will cause with unhandled exception and evantually service restart.
This change adds handler for that sort of exception. If read property fails, another one will be scheduled in the next second. That process shall be repeated until value is successfully read. As there are several possible properties to read, each one shall utilize its own timer, so that every failure can be handled independently from each other.
Tested: Change has been tested on Intel platform, which showed symptoms described above: service tried to get property which has not yet been created, which caused its crash and restart. With this fix applied, issue stopped reproducing.
Change-Id: Ib9b89e07a348868d2f15ffda31b3dc9a47340873 Signed-off-by: Michal Orzel <michalx.orzel@intel.com>
|
/openbmc/x86-power-control/src/ |
H A D | power_control.cpp | edd211e4 Fri Oct 28 06:10:16 CDT 2022 Michal Orzel <michalx.orzel@intel.com> Handle possible SdBus exceptions
Right now service allows to access several signals using DBus interface, instead of GPIO pins. In case of that option selected in config, service will try to read given DBus property using function getProperty. Unfortunately that attempt might fail, for example when that specific object doesn't exist yet, which will cause with unhandled exception and evantually service restart.
This change adds handler for that sort of exception. If read property fails, another one will be scheduled in the next second. That process shall be repeated until value is successfully read. As there are several possible properties to read, each one shall utilize its own timer, so that every failure can be handled independently from each other.
Tested: Change has been tested on Intel platform, which showed symptoms described above: service tried to get property which has not yet been created, which caused its crash and restart. With this fix applied, issue stopped reproducing.
Change-Id: Ib9b89e07a348868d2f15ffda31b3dc9a47340873 Signed-off-by: Michal Orzel <michalx.orzel@intel.com>
|