From owner-freebsd-stable@FreeBSD.ORG  Sat Sep 27 23:24:15 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id B5DDD1CE;
 Sat, 27 Sep 2014 23:24:15 +0000 (UTC)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com
 [IPv6:2a00:1450:400c:c05::235])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 0941AF51;
 Sat, 27 Sep 2014 23:24:14 +0000 (UTC)
Received: by mail-wi0-f181.google.com with SMTP id z2so1327603wiv.2
 for <multiple recipients>; Sat, 27 Sep 2014 16:24:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=CAenBsjdh42J9mdaUXmiroC1QPBZMgq9CWLAtAt7TWo=;
 b=uBEud711i7muAQ35o3pEUvqovrMmuAVobLG4FOu9ugRBljyC4N58m+GjmKgR5Wn1Z1
 chHeAlfHH40INqF0++70J7U7zazWeBO99sHqm9fMek611GrbnEG/D0iU6qd08zANPgz7
 Ac6EeJ5PtQBY3FFu1NtUdIEVyrteG144wKon2AKT2GzOGF3pwA1tvqRY/yxLN1piZ5Vk
 qBIln+QmLGQq5jnmopBSCDcL+WpvUdctVy75Wh+T5VcR9rDps1hps5uwaIgIXi4+0tAW
 jl3ln/juT4veWKISr8S/yQweBzOg6f4ahaJ35ZOMOIP8oMX1tjfJXtKpLRCYM63N+yhv
 Ei7g==
MIME-Version: 1.0
X-Received: by 10.194.142.209 with SMTP id ry17mr34131323wjb.57.1411860253273; 
 Sat, 27 Sep 2014 16:24:13 -0700 (PDT)
Received: by 10.217.127.70 with HTTP; Sat, 27 Sep 2014 16:24:13 -0700 (PDT)
In-Reply-To: <fd2e300a969481d394963d459536b5ba.authenticated@ultimatedns.net>
References: <fd2e300a969481d394963d459536b5ba.authenticated@ultimatedns.net>
Date: Sat, 27 Sep 2014 19:24:13 -0400
Message-ID: <CAKFCL4Wr3OygqhkXPpb=VJdKZgfWSVARzpmumwcx-8J6bNDXQA@mail.gmail.com>
Subject: Re: dmesg seems broken
From: Brandon Allbery <allbery.b@gmail.com>
To: Chris H <bsd-lists@bsdforge.com>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: freebsd current <freebsd-current@freebsd.org>,
 freebsd stable <freebsd-stable@freebsd.org>,
 freebsd amd64 <freebsd-amd64@freebsd.org>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Sep 2014 23:24:15 -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?

-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b@gmail.com                                  ballbery@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net