Yes. I know when it was a new feature I tried it out and didn't see this garbage.
I remember it working well some time ago. It would be great if you could do a binary search and narrow it down. I can then fix the problem.
I probably won't get to that very soon. Sorry.
IIRC K8 has numerous issues in the v3 startup code which can (and probably will) interfere with printk buffers. I'm currently auditing the code to hunt all of these problems down. Please don't try using CONFIG_PRINTK_BUFFER with K8.
We should probably change the defconfigs then. It doesn't change any behavior for me, so I must just be lucky.
I can make PRINTK_BUFFER depend on !K8.
Which would make someone go through and change the defconfigs.
Myles