Thanks again,
yep you were right. I don't know why I didn't see them.
Unfortunately restarting either/both of the demons does not reset the logging system in a way so it cures the garbled output...
BTW. Its not only garbled, it seems also that the logging system accesses the log string at the wrong memory position. Here it seems that it reads the format string at a position skipping the string start which contained %s (to display the denoted string parameter)...
<decode: mismatch for [%x] got [STRING sz:59]>] {
I am bit clueless right now, since logging is a very valueable and neccesary way of developing/debuggin kernel code. Often its not even possible/manageable to connect a debugger...
What can I do to progress here?
Thanks & cheers,
Hagen