summaryrefslogtreecommitdiffstats
path: root/sensordatahandler.cpp
diff options
context:
space:
mode:
authorAndrew Geissler <geissonator@yahoo.com>2018-01-26 11:53:46 -0800
committerTom Joseph <tomjoseph@in.ibm.com>2018-01-29 19:26:08 +0000
commit6fcdc21b16410fa8475417c0ff9bb761da4aed05 (patch)
treeb1980e3278297712035b847a5d7778ce91b06830 /sensordatahandler.cpp
parentb5de286c50d2f9204243e69b49222e8d0fe7204f (diff)
downloadphosphor-host-ipmid-6fcdc21b16410fa8475417c0ff9bb761da4aed05.tar.gz
phosphor-host-ipmid-6fcdc21b16410fa8475417c0ff9bb761da4aed05.zip
Increase timeout for host to respond to attentions
OpenBMC is dealing with some performance issues right after a reboot. Systemd does almost too good a job at parallelizing all of the services which causes a 6X hit on the processor during the initial boot once mapper is ready. In situations where the BMC is rebooted when the host is up, this performance issue coupled with errors queued up by the host to send down to the BMC, can cause OpenBMC to exceed its current 3 second timeout for attentions. This initial message from OpenBMC to the host is done to check if the host is running. If the message times out then it's assumed the host is not running which causes all sorts of issues for the system. Testing has shown it can take up to 10 seconds for the path to complete. Given the uncertainty of future performance, the unknowns on how many errors the host may have queued up, and the minimal impact a larger timeout has, this commit is increasing the timeout to 30 seconds. Resolves openbmc/openbmc#2832 Change-Id: I0d1baf601b6441a149e786e1f5de607862d86a52 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Diffstat (limited to 'sensordatahandler.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud