From owner-freebsd-questions@FreeBSD.ORG  Mon Jun  5 22:26:26 2006
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 A7EFA16BA14
	for <freebsd-questions@freebsd.org>;
	Mon,  5 Jun 2006 21:56:37 +0000 (UTC)
	(envelope-from chris@chrismaness.com)
Received: from ns1.internetinsite.com (ns1.internetinsite.com [208.179.97.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E547E43D5F
	for <freebsd-questions@freebsd.org>;
	Mon,  5 Jun 2006 21:56:36 +0000 (GMT)
	(envelope-from chris@chrismaness.com)
Received: from ns1.internetinsite.com (localhost [127.0.0.1])
	by ns1.internetinsite.com (8.13.6/8.13.6) with ESMTP id k55LuZq3055801; 
	Mon, 5 Jun 2006 14:56:36 -0700 (PDT)
	(envelope-from chris@chrismaness.com)
Received: from localhost (chris@localhost)
	by ns1.internetinsite.com (8.13.6/8.13.6/Submit) with ESMTP id
	k55LuZOq055796; Mon, 5 Jun 2006 14:56:35 -0700 (PDT)
	(envelope-from chris@chrismaness.com)
X-Authentication-Warning: ns1.internetinsite.com: chris owned process doing -bs
Date: Mon, 5 Jun 2006 14:56:35 -0700 (PDT)
From: Chris Maness <chris@chrismaness.com>
X-X-Sender: chris@ns1.internetinsite.com
To: freebsd-questions@freebsd.org
In-Reply-To: <448xobpi30.fsf@be-well.ilk.org>
Message-ID: <20060605145453.S55741@ns1.internetinsite.com>
References: <44843B61.5050209@chrismaness.com>
	<448469D5.8060700@scls.lib.wi.us>
	<20060605105358.Q54670@ns1.internetinsite.com>
	<44847336.9050908@scls.lib.wi.us> <448xobpi30.fsf@be-well.ilk.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Greg Barniskis <nalists@scls.lib.wi.us>
Subject: Re: dmesg not working on new system
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jun 2006 22:26:28 -0000



On Mon, 5 Jun 2006, Lowell Gilbert wrote:

> Greg Barniskis <nalists@scls.lib.wi.us> writes:
>
>> Chris Maness wrote:
>>>
>>>
>>> On Mon, 5 Jun 2006, Greg Barniskis wrote:
>>>
>>>> Chris Maness wrote:
>>>>> I just installed 6.1 and upgraded to RELEASE-p1.  The command
>>>>> dmesg is not displaying any kernel messages, any suggestions?
>>>>
>>>> Suggests all is well?
>>>>
>>>> dmesg outputs stuff from the current system message buffer, which
>>>> contains your boot messages right after booting but those can get
>>>> flushed over time. Boot messages are saved to a file though, for
>>>> reference.
>>>>
>>>> more /var/run/dmesg.boot
>>>>
>>
>>>
>>> I just thought it was strange because every other system I have it
>>> at least displays dmesg.boot if there is no other messages.  Is this
>>> new behavior for 6.1?
>>
>> Not new behavior. A dmesg on any of my running systems (4.x, 5.x)
>> returns nothing after a time. You were just catching it before the
>> buffer was flushed. I don't know what triggers that, and it is
>> possible that the trigger/timing of it may have changed in 6.x (and as
>> always, YMMV).
>
> Interesting.  Does "dmesg -a" show anything different?
>
Yes, it does, but why would it not show anything without the flag right 
after a reboot?  Wierd.  I almost suspect hard drive issues.