diff options
| author | Vasant Hegde <hegdevasant@linux.vnet.ibm.com> | 2019-02-28 08:30:10 +0530 |
|---|---|---|
| committer | Vasant Hegde <hegdevasant@linux.vnet.ibm.com> | 2019-03-05 11:28:40 +0530 |
| commit | 1d1a977916b619570644ecc3f9266d819adaf4a4 (patch) | |
| tree | 7ca3b4a18599a68b2da03f39315db90580197494 | |
| parent | 184f81559530da68d5eb5130255fc60afdcc506b (diff) | |
| download | skiboot-1d1a977916b619570644ecc3f9266d819adaf4a4.zip skiboot-1d1a977916b619570644ecc3f9266d819adaf4a4.tar.gz skiboot-1d1a977916b619570644ecc3f9266d819adaf4a4.tar.bz2 | |
hw/bt: Do not disable ipmi message retry during OPAL boot
[ Upstream commit c0ab7b45db3dc44daf001f61324bd1418091dede ]
Currently OPAL doesn't know whether BMC is functioning or not. If BMC is
down (like BMC reboot), then we keep on retry sending message to BMC. So
in some corner cases we may hit hard lockup issue in kernel.
Ideally we should avoid using synchronous path as much as possible. But
for now commit 01f977c3 added option to disable message retry in synchronous.
But this fix is not required during boot. Hence lets disable IPMI message
retry during OPAL boot.
Fixes: 01f977c3 (hw/bt: Add backend interface to disable ipmi message)
Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
Signed-off-by: Stewart Smith <stewart@linux.ibm.com>
Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
| -rw-r--r-- | core/ipmi.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/core/ipmi.c b/core/ipmi.c index 27cb426..d599c3f 100644 --- a/core/ipmi.c +++ b/core/ipmi.c @@ -176,7 +176,7 @@ void ipmi_queue_msg_sync(struct ipmi_msg *msg) lock(&sync_lock); while (sync_msg); sync_msg = msg; - if (msg->backend->disable_retry) + if (msg->backend->disable_retry && !opal_booting()) msg->backend->disable_retry(msg); ipmi_queue_msg_head(msg); unlock(&sync_lock); |