diff --git a/vm/Thread.c b/vm/Thread.c
index 7ca3dc7..55e27f6 100644
--- a/vm/Thread.c
+++ b/vm/Thread.c
@@ -521,6 +521,10 @@
     case SUSPEND_FOR_DEBUG:         return "debug";
     case SUSPEND_FOR_DEBUG_EVENT:   return "debug-event";
     case SUSPEND_FOR_STACK_DUMP:    return "stack-dump";
+#if defined(WITH_JIT)
+    case SUSPEND_FOR_TBL_RESIZE:    return "table-resize";
+    case SUSPEND_FOR_IC_PATCH:      return "inline-cache-patch";
+#endif
     default:                        return "UNKNOWN";
     }
 }
@@ -559,6 +563,9 @@
                  *
                  * Could be the debugger telling us to resume at roughly
                  * the same time we're posting an event.
+                 *
+                 * Could be two app threads both want to patch predicted
+                 * chaining cells around the same time.
                  */
                 LOGI("threadid=%d ODD: want thread-suspend lock (%s:%s),"
                      " it's held, no suspend pending\n",