On Sun, Apr 07, 2013 at 09:52:37PM -0700, Jeremy Chadwick wrote: | I have discussed this problem for years now -- over 5 years, to be | exact. As if I haven't sounded like a broken record before, I surely do | now. Start here, under section "Kernel", item "Scrambled or garbled | kernel output": | | https://wiki.freebsd.org/BugBusting/Commonly_reported_issues | | The problem has not gone away. It has not been solved. It has not been | worked around. PRINTF_BUFR_SIZE does not solve the problem, and rarely | helps relieve it. | | I have discussed this issue more recently (2010) with John Baldwin as | well: | | http://lists.freebsd.org/pipermail/freebsd-questions/2010-March/214412.html | http://lists.freebsd.org/pipermail/freebsd-questions/2010-March/214423.html | | And in December 2011 too -- particularly an important read if you think | increasing the number is a wise idea: | | http://lists.freebsd.org/pipermail/freebsd-stable/2011-December/065158.html | | Bottom line: there is no solution other than to switch OSes.
I have tweaked some kernel message generaters to be more line based. We had issues with CAM attached devices print out parts separately and then get intermixed a lot. So I modified them to print them as one line. Then they didn't seem to get intermixed. This doesn't solve the overall problem, but if messages are done more this way then it helps. Thanks, Doug A. _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
