From owner-freebsd-questions@FreeBSD.ORG Tue Jun 6 01:40:31 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 57C7216DD60 for ; Tue, 6 Jun 2006 01:04:22 +0000 (UTC) (envelope-from reko.turja@liukuma.net) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 211EA43D78 for ; Tue, 6 Jun 2006 01:04:10 +0000 (GMT) (envelope-from reko.turja@liukuma.net) Received: from moria.endor.swagman.org ([213.113.4.185] [213.113.4.185]) by mxfep01.bredband.com with ESMTP id <20060605231604.EQMK14117.mxfep01.bredband.com@moria.endor.swagman.org>; Tue, 6 Jun 2006 01:16:04 +0200 Received: from rivendell (rivendell.endor.swagman.org [192.168.10.10]) by moria.endor.swagman.org (Postfix) with SMTP id DC30628; Tue, 6 Jun 2006 02:16:01 +0300 (EEST) Message-ID: <023401c688f6$090458d0$0a0aa8c0@rivendell> From: "Reko Turja" To: "Chris Maness" , 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> <20060605145453.S55741@ns1.internetinsite.com> Date: Tue, 6 Jun 2006 02:16:11 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jun 2006 01:40:36 -0000 ----- Original Message ----- From: "Chris Maness" > Yes, it does, but why would it not show anything without the flag > right after a reboot? Wierd. I almost suspect hard drive issues. I got the exactly same happen to me with 6.1-RELEASE updated just after 6.1 was released. Didn't think about the weirdness really until now seeing your messages. The symptoms were exactly the same, /var/dmesg file was empty right after the boot and of course dmesg command didn't print the booting messages either. Things seems to be normalized for me with 6.1-STABLE from yesterday, but haven't booted since buildworld process after which I got proper dmesg output. -Reko