diff --git a/README.md b/README.md
index 1a393db..f55412b 100644
--- a/README.md
+++ b/README.md
@@ -573,7 +573,8 @@
 phosphor-logging supports a setting, which when set, will result in the
 software looking at new phosphor-logging entries being created, and if a
 CALLOUT* is found within the entry, ensuring the system will not power
-on.
+on.  Entries with severities of Informational or Debug will not block boots,
+even if they have callouts.
 
 The full design for this can be found
 [here](https://github.com/openbmc/docs/blob/master/designs/fail-boot-on-hw-error.md)
diff --git a/log_manager.cpp b/log_manager.cpp
index d12630a..c2a9b86 100644
--- a/log_manager.cpp
+++ b/log_manager.cpp
@@ -242,7 +242,8 @@
 
     serialize(*e);
 
-    if (isQuiesceOnErrorEnabled() && isCalloutPresent(*e))
+    if (isQuiesceOnErrorEnabled() && (errLvl < Entry::sevLowerLimit) &&
+        isCalloutPresent(*e))
     {
         quiesceOnError(entryId);
     }