Handle crashdump busy error
We currently fail out and immediately handle system recovery if there is
any error in starting crashdump. There are cases where crashdump is in
progress, and we don't want to reset. This adds a check for a busy error
code to continue waiting.
Tested:
Confirmed that if crashdump fails, the system is recovered. But if
crashdump is busy, it continues waiting for completion.
Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
Change-Id: I480968caaf8b87ce05756a1b60537bf0300ca209
diff --git a/include/host_error_monitor.hpp b/include/host_error_monitor.hpp
index 3470c2f..8a3d90b 100644
--- a/include/host_error_monitor.hpp
+++ b/include/host_error_monitor.hpp
@@ -95,6 +95,13 @@
[](boost::system::error_code ec) {
if (ec)
{
+ if (ec.value() == boost::system::errc::device_or_resource_busy)
+ {
+ std::cerr << "Crashdump already in progress. Waiting for "
+ "completion signal\n";
+ return;
+ }
+
std::cerr << "failed to start Crashdump\n";
}
},