Comment 3 for bug 25550

Ben wrote:
>klogd is started _well_ after the kernel starts
>printing the messages, and must first consume the entire kmsg buffer.

Good to know.
Since the pattern is repeatable and happens once at the start, I now wonder
whether the kmsg buffer is too small for the current amount of messages,
therefore it just starts printing contents of a rolled-over ring buffer, i.e.
somewhere amid a line?

Increasing the kernel buffer size could then solve that issue and not loose
messages. I'll see if I can find a place where this is configured, without
building a custom kernel