Dmesg output breaking up.
bde at zeta.org.au
Fri Jan 23 21:08:19 PST 2004
On Fri, 23 Jan 2004, John Baldwin wrote:
> On Friday 23 January 2004 04:13 pm, Josef Karthauser wrote:
> > On Thu, Jan 22, 2004 at 10:30:27AM -0500, John Baldwin wrote:
> > > On Thursday 22 January 2004 03:23 am, Josef Karthauser wrote:
> > > > What is it that causes the dmesg output to break after a while?
> > > ...
> > > I don't remember the exact details, but dmesg -a will give you the entire
> > > message back. I know that the cause goes back to when the console output
> > > started getting dumped into the message buffer.
> > That appears to work. It would be good to get this fixed though ->
> > I notice that the dmesg output in the period scripts is broken in the
> > same way.
> Apparently there isn't a good fix. You can try bugging phk. :)
It's interesting that it seems to be broken on freefall right now.
dmesg prints just one line. But the bug seems to be in printing that
line instead of nothing. The message bugger is full of syslog messages
do there are no kernel messages to print, but the tail of one of the
syslog messages is printed because its markup has been clobbered by
the buffer wrapping around.
More information about the freebsd-current