:orphan: .. title:: LOG_BLOCK_IN_THREAD_TIMEOUT_MS .. option:: CONFIG_LOG_BLOCK_IN_THREAD_TIMEOUT_MS *Maximum time (in milliseconds) thread can be blocked* Type: ``int`` Help ==== If new buffer for a log message cannot be allocated in that time, log message is dropped. Forever blocking (-1) is possible however may lead to the logger deadlock if logging is enabled in threads used for logging (e.g. logger or shell thread). Direct dependencies =================== \ :option:`LOG_BLOCK_IN_THREAD ` && !\ :option:`LOG_IMMEDIATE ` && !\ :option:`LOG_MINIMAL ` && !\ :option:`LOG_FRONTEND ` && !\ :option:`LOG_MINIMAL ` && \ :option:`LOG ` *(Includes any dependencies from ifs and menus.)* Default ======= - 1000 Kconfig definition ================== .. highlight:: kconfig At ``subsys/logging/Kconfig.processing:36`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:34`` → ``subsys/Kconfig:31`` → ``subsys/logging/Kconfig:23`` Menu path: (Top) → Sub Systems and OS Services → Logging → Processing → Block in thread context on full .. parsed-literal:: config LOG_BLOCK_IN_THREAD_TIMEOUT_MS int "Maximum time (in milliseconds) thread can be blocked" range -1 10000 default 1000 depends on \ :option:`LOG_BLOCK_IN_THREAD ` && !\ :option:`LOG_IMMEDIATE ` && !\ :option:`LOG_MINIMAL ` && !\ :option:`LOG_FRONTEND ` && !\ :option:`LOG_MINIMAL ` && \ :option:`LOG ` help If new buffer for a log message cannot be allocated in that time, log message is dropped. Forever blocking (-1) is possible however may lead to the logger deadlock if logging is enabled in threads used for logging (e.g. logger or shell thread). *(The 'depends on' condition includes propagated dependencies from ifs and menus.)*