-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
samples: net: syslog_net: hard fault when running on frdm_k64f #34515
Comments
Increasing the logging thread stack space from 768 (default) to 2048, the crash disappeared. |
Thanks @jukkar, you are right. I have should tried that before making this issue. |
@aunsbjerg I think better would be to increase the logging thread default stack size as the 768 seems to be too small. Then we would not need to adjust each and every sample. |
I will look into this. Stack usage should not increase after logging v2. |
Describe the bug
When building and running the syslog_net sample on a frdm_k64f board with no changes to the sample configuration, the application crashes with nothing printed to the shell besides the standard zephyr booting banner.
Disabling autostart of the log backend yields slightly more information in the form of a bus fault stack trace, see log output.
To Reproduce
west build -b frdm_k64f zephyr/samples/net/syslog_net -- -DCONFIG_LOG_BACKEND_NET_AUTOSTART=n
west flash -r jlink
Logs and console output
Additional context
Possibly related to #34403, at least in terms of observed behaviour.
The text was updated successfully, but these errors were encountered: