Perform serial prints in a critical section

Sometimes during initialization, one log_msg() intercepts another one, leading to a whole lot of weird issues in other modules (like I2C). I suspect this to be memory corruption of some kind. The issues can be fixed by performing serial prints in a critical section, thus ensuring atomicity of prints. Note that this does not mean log messages will not interleave.

A possible downside of this approach is that prints can take quite some time. We did not notice any issues with that so far though. Apart from that, not many prints happen anyway.

added 1-Bug 3-Epicardium 6 - Needs Testing labels

changed milestone to %v1.7

Looks good to me! Thanks for keeping our codebase clean.

However, I'm only a bot - so a human will still have to approve this request.

added 3 commits

• 5a69ac71...a5c5e87e - 2 commits from branch master
• 9605ce6e - fix(serial): Perform serial prints in a critical section

Compare with previous version

added 7 commits

• 9605ce6e...ef03f13b - 6 commits from branch master
• 77183763 - fix(serial): Perform serial prints in a critical section

Compare with previous version

added 4 commits

• 77183763...c8dbb334 - 3 commits from branch master
• 47f437d5 - fix(serial): Perform serial prints in a critical section

Compare with previous version

added 4 commits

• 47f437d5...585144d2 - 3 commits from branch master
• e9a05072 - fix(serial): Perform serial prints in a critical section

Compare with previous version

added 3 commits

• e9a05072...61599d4d - 2 commits from branch master
• 32681478 - fix(serial): Perform serial prints in a critical section

Compare with previous version

removed 6 - Needs Testing label

merged

mentioned in commit 88bc3ea3