From owner-freebsd-questions@FreeBSD.ORG Sat Sep 30 02:20:55 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B83316A412 for ; Sat, 30 Sep 2006 02:20:55 +0000 (UTC) (envelope-from captainspam@speakeasy.net) Received: from mail3.sea5.speakeasy.net (mail3.sea5.speakeasy.net [69.17.117.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BE3F43D46 for ; Sat, 30 Sep 2006 02:20:55 +0000 (GMT) (envelope-from captainspam@speakeasy.net) Received: (qmail 9408 invoked from network); 30 Sep 2006 02:20:54 -0000 Received: from dsl093-002-115.det1.dsl.speakeasy.net (HELO [192.168.1.2]) (captainspam@[66.93.2.115]) (envelope-sender ) by mail3.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 30 Sep 2006 02:20:54 -0000 Message-ID: <451DD485.8020802@speakeasy.net> Date: Fri, 29 Sep 2006 22:20:53 -0400 From: Nicholas Killewald User-Agent: Thunderbird 1.5.0.7 (X11/20060921) MIME-Version: 1.0 To: Dan Nelson References: <451DCDB9.1090306@speakeasy.net> <20060930020018.GB77128@dan.emsphone.com> In-Reply-To: <20060930020018.GB77128@dan.emsphone.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Empty dmesg output X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2006 02:20:55 -0000 Dan Nelson wrote: > In the last episode (Sep 29), Nicholas Killewald said: >> Is there any situation in which dmesg should give no output whatsoever? >> Currently, my FreeBSD machine (RELEASE-6.0) isn't reporting anything >> at all when I call up dmesg. It has been on for quite some time, and to >> the best of my knowledge there isn't much of interest it should have >> reported recently. It DID say something back at its initial bootup and >> for some time thereafter, but nothing now. Is this normal, or should I >> be a bit concerned? > > Things printed to the console (via syslog or writing to /dev/console) > get logged to the dmesg buffer but aren't printed by the dmesg command. > If you've had lots of console output all your kernel messages may have > been pushed out. Try running "dmesg -a" to see the raw buffer. You > can see the kernel bootup log at /var/run/dmesg.boot . > Aha... that makes sense. Yep, that was it, the console messages must've flooded out any kernel messages. Thanks! -- Nicholas Killewald