summaryrefslogtreecommitdiffstats
path: root/discover
diff options
context:
space:
mode:
authorJeremy Kerr <jk@ozlabs.org>2015-09-30 08:38:36 +0800
committerJeremy Kerr <jk@ozlabs.org>2015-09-30 13:23:49 +0800
commitd171258160f7ed4756531f51e66fb116753bc990 (patch)
treefe34ffeb8e0f97e30d43f8bd3af9cd683182b4e6 /discover
parent420f0e2c5d8338b42047c58f055cdb944685ead7 (diff)
downloadtalos-petitboot-d171258160f7ed4756531f51e66fb116753bc990.tar.gz
talos-petitboot-d171258160f7ed4756531f51e66fb116753bc990.zip
discover/ipmi: Increase IPMI timeout to a reasonable value
We've seen some IPMI timeouts during testing - meaning that an IPMI bootdev setting will be ignored. This can result in a machine booting from an incorrect boot device, or missing a 'safe mode' indication, or incorrectly proceeding past petitboot. The firmware & kernel has its own timeout & retry mechanism, so we already have a little error-recovery there; the timeout in petitboot is to prevent an indefinite block if the kernel interface isn't behaving correctly. So, this change bumps the timeout to a value that suits BMCs we've seen in the field (specifying a 2 second timeout, with one retry). Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
Diffstat (limited to 'discover')
-rw-r--r--discover/platform-powerpc.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/discover/platform-powerpc.c b/discover/platform-powerpc.c
index d45cced..23e63c1 100644
--- a/discover/platform-powerpc.c
+++ b/discover/platform-powerpc.c
@@ -22,7 +22,7 @@
static const char *partition = "common";
static const char *sysparams_dir = "/sys/firmware/opal/sysparams/";
static const char *devtree_dir = "/proc/device-tree/";
-static const int ipmi_timeout = 500; /* milliseconds */
+static const int ipmi_timeout = 5000; /* milliseconds. */
struct param {
char *name;
OpenPOWER on IntegriCloud