From owner-freebsd-current@FreeBSD.ORG Tue Feb 7 12:25:04 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7AF921065686 for ; Tue, 7 Feb 2012 12:25:04 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2EA758FC13 for ; Tue, 7 Feb 2012 12:25:03 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Ruk6W-0007mz-IS for freebsd-current@freebsd.org; Tue, 07 Feb 2012 13:25:00 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 07 Feb 2012 13:25:00 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 07 Feb 2012 13:25:00 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Tue, 07 Feb 2012 13:24:51 +0100 Lines: 20 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120110 Thunderbird/9.0 In-Reply-To: Subject: Re: Freebsd 9.0 release and dmesg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2012 12:25:04 -0000 On 06/02/2012 18:24, JD wrote: > dmesg no longer outputs the kernel messages. > > $ dmesg > $ > $ which dmesg > /sbin/dmesg > $what /sbin/dmesg > /sbin/dmesg: > > So, I have no idea what version of dmesg got installed. > > Anyone on 9.0 Release have this problem? How to fix it? I thought this was by design, I've noticed it very early (7.x, probably earlier) and just thought that when lot of data is written to the console, the actual kernel message buffer gets invalidated or freed. This made me stop using dmesg altogether and just look at either /var/run/dmesg.boot for the boot messages or /var/log/messages.