Date: Tue, 20 Mar 2001 17:25:34 +0100 From: Thomas Moestl <tmoestl@gmx.net> To: Noel Koethe <noel@koethe.net> Cc: freebsd-stable@freebsd.org Subject: Re: dmesg output Message-ID: <20010320172534.A1977@crow.dom2ip.de> In-Reply-To: <Pine.LNX.4.21.0103201704060.12266-100000@data.wipol.uni-bonn.de>; from noel@koethe.net on Tue, Mar 20, 2001 at 05:10:47PM %2B0100 References: <Pine.LNX.4.21.0103201704060.12266-100000@data.wipol.uni-bonn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 20, 2001 at 05:10:47PM +0100, Noel Koethe wrote: > since some weeks my dmesg output is broken: > # dmesg > 2250 192.168.159.255:138 in via xl0 > > I got the broken output in the mails every night. > > # uname -a > FreeBSD rock.domain.de 4.3-BETA FreeBSD 4.3-BETA #0: Fri Mar 16 22:53:58 \ > CET 2001 > > I tried some cvsup updates but the output is always cuted.:( > > Maybe someone can give me a hint to fix it if the problem is located at my > machine. Try "dmesg -a". The messages are stored in a ring buffer, so the oldest ones will be overwritten if the buffer fills up. Additionally, dmesg will normally not show the console output that is also stored in the message buffer. This produces these effects. This is starting to become a FAQ... - thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010320172534.A1977>