From owner-freebsd-amd64@FreeBSD.ORG  Mon Sep 29 14:31:13 2014
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CFAB9955;
 Mon, 29 Sep 2014 14:31:13 +0000 (UTC)
Received: from udns.ultimatedns.net (unknown
 [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9CA971A6;
 Mon, 29 Sep 2014 14:31:13 +0000 (UTC)
Received: from udns.ultimatedns.net (localhost [127.0.0.1])
 by udns.ultimatedns.net (8.14.5/8.14.5) with ESMTP id s8TEVTVc010237;
 Mon, 29 Sep 2014 07:31:35 -0700 (PDT)
 (envelope-from bsd-lists@bsdforge.com)
Received: (from www@localhost)
 by udns.ultimatedns.net (8.14.5/8.14.5/Submit) id s8TEVMgr010213;
 Mon, 29 Sep 2014 07:31:22 -0700 (PDT)
 (envelope-from bsd-lists@bsdforge.com)
Received: from udns.ultimatedns.net ([2602:d1:b4d6:e600:4261:86ff:fef6:aa2a])
 (UDNSMS authenticated user chrish) by ultimatedns.net with HTTP;
 Mon, 29 Sep 2014 07:31:24 -0700 (PDT)
Message-ID: <f1a6c55c641e1d559559b28735251e50.authenticated@ultimatedns.net>
In-Reply-To: <CAKFCL4Wr3OygqhkXPpb=VJdKZgfWSVARzpmumwcx-8J6bNDXQA@mail.gmail.com>
References: <fd2e300a969481d394963d459536b5ba.authenticated@ultimatedns.net>
 <CAKFCL4Wr3OygqhkXPpb=VJdKZgfWSVARzpmumwcx-8J6bNDXQA@mail.gmail.com>
Date: Mon, 29 Sep 2014 07:31:24 -0700 (PDT)
Subject: Re: dmesg seems broken
From: "Chris H" <bsd-lists@bsdforge.com>
To: "Brandon Allbery" <allbery.b@gmail.com>
User-Agent: UDNSMS/2.0.3
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: freebsd current <freebsd-current@freebsd.org>,
 freebsd stable <freebsd-stable@freebsd.org>,
 freebsd amd64 <freebsd-amd64@freebsd.org>
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Sep 2014 14:31:13 -0000

> On Sat, Sep 27, 2014 at 7:22 PM, Chris H <bsd-lists@bsdforge.com> wrote:
>
>> Where can I get that information? Where was it sent? Why am I
>> not allowed to view it?
>>
>
> Sounds to me like the kernel ring buffer is now too small for all the early
> boot messages?
OK more investigation indicates that bumping
kern.msgbufsize
will return the missing bits. Maybe this is what you were trying to tell me. ;)

Anyway. Anyone know why was this tunable reduced? I don't experience this on
RELENG_8, or 11-CURRENT.

FWIW I have loader.conf(5) set to boot verbose. But still didn't get the info
expected. :(

Thanks for the reply, Brandon.

--Chris

>
> --
> brandon s allbery kf8nh                               sine nomine associates
> allbery.b@gmail.com                                  ballbery@sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>