summaryrefslogtreecommitdiffstats
path: root/src/usr/ipmi/ipmiwatchdog.C
Commit message (Collapse)AuthorAgeFilesLines
* ipmi: Split into ipmibase and ipmiext modulesAndrew Jeffery2018-10-101-204/+0
| | | | | | | | | | | | | | | | | | Split the IPMI module into base and ext portions, with the BT interface, device driver and resource provider in the base portion, and all remaining IPMI functionality in the ext portion. The split is in preparation for moving the base functionality in the hostboot base image. Change-Id: Iec864f96240d79f4fadd5519d2ef46437d07c1fd Signed-off-by: Andrew Jeffery <andrewrj@au1.ibm.com> Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/66792 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Reviewed-by: Corey V. Swenson <cswenson@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* ipmiwatchdog: Handle uninitialized errors during resetWilliam A. Kennington III2018-07-101-5/+56
| | | | | | | | | | | | | | | | | | | | | The IPMI spec allows for the IPMI watchdog to return an error if the watchdog was never initialized. This can happen if the daemon restarts or if the initial setWatchDog command fails for some reason. Instead of allowing the watchdog to remain uninitialized and disabled, use the values of the previously issued set command to re-initialize the watchdog. This is only attempted once per resetWatchDog call, but periodic calls to the resetWatchDog should eventually re-initialize it. Resolves #139 Signed-off-by: William A. Kennington III <wak@google.com> Change-Id: I7b777e2f3b75d5ce38888018c1b74c6ce12ffc19 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/59163 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* ipmiwatchdog: Limit the number of resetsWilliam A. Kennington III2018-05-301-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | We send resets after the completion of every istep and in the middle of some of our known long isteps. In some instances during boot, during fast isteps or custom routines, we can send 10 or more resets within the same second. This generates a lot of IPMI traffic and causes the BMC to spend more time processing resets than is needed. Since our timeout is relatively long (120s right now), it should be no issue to limit the number of resets to one reset every 1-2 seconds I've tested this on a zaius machine and it reduced load on the BMC and made clean boots a little faster. Resolves #140 Signed-off-by: William A. Kennington III <wak@google.com> Change-Id: I60d26af082e1ddb29624fc22a0513b47526978d5 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/59291 Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com> Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com> Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com>
* Enable super-long watchdog timer when console traces are enabledDan Crowell2018-05-021-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | When console traces are enabled, the boot takes significantly longer than usual. Our standard watchdog timeout of 2 minutes is not sufficient. Made the following changes: - Tied the enablement of the long timeout to the CONFIG flags for console traces - Increased the timeout to 1 hour (from 40 minutes) since this is lab only and false positives are the worst... - Added a couple clarifying traces to make future watchdog debug simpler Change-Id: I92bb0b07cb77a13cb390450999b285f2ad74168d CQ: SW425407 Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/57580 Reviewed-by: Martin Gloff <mgloff@us.ibm.com> Reviewed-by: Richard J. Knight <rjknight@us.ibm.com> Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com> Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com> Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com> Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com> Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com> Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com>
* Set watchdog and set sensors are now asynchronous sendsElizabeth Liner2016-02-191-18/+2
| | | | | | | | | | | Backport: master-p8 Change-Id: If8741e67986c6d6df95a655fb5669df764649e82 Reviewed-on: http://gfw160.aus.stglabs.ibm.com:8080/gerrit/18993 Tested-by: Jenkins Server Reviewed-by: Brian Silver <bsilver@us.ibm.com> Reviewed-by: Richard J. Knight <rjknight@us.ibm.com> Reviewed-by: WILLIAM G. HOFFA <wghoffa@us.ibm.com> Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
* IPMI: C++11 bad string literal concatenationPatrick Williams2015-06-081-2/+2
| | | | | | | | | | Change-Id: I6e19a80eb1918b9b9ceb714c5e90110d17081480 RTC:124186 Reviewed-on: http://gfw160.aus.stglabs.ibm.com:8080/gerrit/17975 Reviewed-by: Brian H. Horton <brianh@linux.ibm.com> Tested-by: Jenkins Server Reviewed-by: WILLIAM G. HOFFA <wghoffa@us.ibm.com> Reviewed-by: A. Patrick Williams III <iawillia@us.ibm.com>
* add IPMI Watchdog TimerAni Bagepalli2014-12-031-0/+149
Change-Id: I4617f5b545a3fc193e62fb7cfdf0292b394871c2 RTC: 108832 Reviewed-on: http://gfw160.aus.stglabs.ibm.com:8080/gerrit/14232 Reviewed-by: Christopher T. Phan <cphan@us.ibm.com> Reviewed-by: Brian H. Horton <brianh@linux.ibm.com> Reviewed-by: A. Patrick Williams III <iawillia@us.ibm.com> Tested-by: Jenkins Server
OpenPOWER on IntegriCloud