From owner-freebsd-stable@FreeBSD.ORG  Thu Feb 16 22:15:13 2012
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 71C821065670
	for <freebsd-stable@freebsd.org>; Thu, 16 Feb 2012 22:15:13 +0000 (UTC)
	(envelope-from julian@freebsd.org)
Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16])
	by mx1.freebsd.org (Postfix) with ESMTP id 442B68FC14
	for <freebsd-stable@freebsd.org>; Thu, 16 Feb 2012 22:15:13 +0000 (UTC)
Received: from julian-mac.elischer.org (c-67-180-24-15.hsd1.ca.comcast.net
	[67.180.24.15]) (authenticated bits=0)
	by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id q1GMFBUX015765
	(version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO);
	Thu, 16 Feb 2012 14:15:12 -0800 (PST)
	(envelope-from julian@freebsd.org)
Message-ID: <4F3D804B.8000008@freebsd.org>
Date: Thu, 16 Feb 2012 14:16:43 -0800
From: Julian Elischer <julian@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US;
	rv:1.9.2.26) Gecko/20120129 Thunderbird/3.1.18
MIME-Version: 1.0
To: Sergey Kandaurov <pluknet@gmail.com>
References: <4F3CC54B.7080402@freebsd.org>
	<CAE-mSO+CQqzEFUbuyfb5=oC0iwr0TNEDjbmKTXUYN7Fk+er8qA@mail.gmail.com>
In-Reply-To: <CAE-mSO+CQqzEFUbuyfb5=oC0iwr0TNEDjbmKTXUYN7Fk+er8qA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: something wrong with dmesg?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2012 22:15:13 -0000

On 2/16/12 1:27 AM, Sergey Kandaurov wrote:
> On 16 February 2012 12:58, Julian Elischer<julian@freebsd.org>  wrote:
>> I just noticed that lately in 9.x and maybe 8-Stable, dmesg seems to return
>> nothing if
>> there is active logging going on. I saw someone else refer to this as well.
>>
>> Has this been reported?
> Didn't we have this for years? I cannot recall there was a difference to the
> current behavior since 8.x or 7.x (or even 6.x).
> kern.msgbuf includes messages sent with syslog, and if they dominate
> then you might get empty dmesg output. By default it skips non-kernel
> (or rather those messages which doesn't use BSD syslog format)
> messages, and you can include them using dmesg -a.
>
I expect to see the output from all kernel 'printf' statements in dmesg.
they were definitely not turning up for me last week, but if I tried 
again,
there would be contents,