Date: Wed, 21 Feb 2001 02:17:01 +0100 From: Thomas Moestl <tmoestl@gmx.net> To: freebsd-stable@freebsd.org Subject: Re: dmesg flakeyness Message-ID: <20010221021701.A4814@crow.dom2ip.de> In-Reply-To: <20010221120436.W44375@goldenterrace.com.au>; from sjhstable@tracking.amos.net on Wed, Feb 21, 2001 at 12:04:36PM %2B1100 References: <20010221120436.W44375@goldenterrace.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 21, 2001 at 12:04:36PM +1100, Steve Horan wrote: > I've recently cvsup'd (twice - about a week apart) and both worlds > seem to have some weirdness with dmesg. > > After booting, dmesg works fine, as normal, but after a while, if I do > another dmesg, I get only the last entry, and often the first few > characters are missing. > > example: > > (root@jobu) /usr/home/sjhoran > dmesg > not authoritative for xxxxxx.com.au, SOA query got rcode 0, aa 0, ancount 0, aucount 13 > (root@jobu) /usr/home/sjhoran > > > Any info would be great, and I hope this is useful to someone who > might be able to fix it. Have you tried "dmesg -a"? It seems like the above message is from syslog (if something is printed on into /dev/console, this is also recorded in the message buffer). dmesg by default ignores messages that are not from the kernel, but it cannot determine this if the first characters of a line are missing. The missing characters get lost when the oldest messages are partly overwritten by new ones (the message buffer is a ring buffer). - 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?20010221021701.A4814>