Logging stops on all backend when overloaded for a time #75736
Labels
area: Logging
bug
The issue is a bug, or the PR is fixing a bug
priority: medium
Medium impact/importance bug
Describe the bug
Logging stops on all backend when overloaded for a time. After stopped no more messages are produced, even when the overload ceases. By overloaded I mean to drop 99% of the messages.
Platform: STM32H743
Version: tag zephyr-v3.5.0
Additional info:
I have two backends, one logs on UART and other logs to an external flash with filesystem littlefs and file rotation. All my threas are same priority 5.
Workarround: patching log_core.c to trigger the logging thread when above the configured threshold seems to work.
With the workarround the system behaves normally after the overload passes.
KConfigs
Expected behavior
Messages should be dropped as necessary but the logging system should remain operational.
Impact
minor, patch works for me.
Environment
The text was updated successfully, but these errors were encountered: