From owner-freebsd-stable@FreeBSD.ORG Thu Feb 16 09:27:07 2012 Return-Path: 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 18476106564A for ; Thu, 16 Feb 2012 09:27:07 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8E1E98FC0A for ; Thu, 16 Feb 2012 09:27:05 +0000 (UTC) Received: by lagz14 with SMTP id z14so3155578lag.13 for ; Thu, 16 Feb 2012 01:27:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zM1hhhHOo1kNMcgmxswbvFNut92rat2mWnjdBTkClWk=; b=WgLlEIfLCRd7r7JYn4bEqvY8voUf3Q94Y/gOgDax94hZmGSzYouF/pE3jXezoSC57G h5o9tq037clOsLRk4fhE3N/U3zLJr/eKsM8958ueCGhWejLlL4FBiyU5veVnsKJCe0Hv e5azzbVN49H0LGUokv9C4Upk+FT1Fi00QC6/0= MIME-Version: 1.0 Received: by 10.152.110.102 with SMTP id hz6mr1316235lab.21.1329384425082; Thu, 16 Feb 2012 01:27:05 -0800 (PST) Received: by 10.152.18.4 with HTTP; Thu, 16 Feb 2012 01:27:05 -0800 (PST) In-Reply-To: <4F3CC54B.7080402@freebsd.org> References: <4F3CC54B.7080402@freebsd.org> Date: Thu, 16 Feb 2012 12:27:05 +0300 Message-ID: From: Sergey Kandaurov To: Julian Elischer Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Stable 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Feb 2012 09:27:07 -0000 On 16 February 2012 12:58, Julian Elischer 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. -- wbr, pluknet