From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 23:39:32 2014 Return-Path: Delivered-To: freebsd-stable@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 CFB2265D for ; Sat, 27 Sep 2014 23:39:32 +0000 (UTC) Received: from mail.egr.msu.edu (hill.egr.msu.edu [35.9.37.162]) by mx1.freebsd.org (Postfix) with ESMTP id A687BDD for ; Sat, 27 Sep 2014 23:39:32 +0000 (UTC) Received: from hill (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id B948C1F6D6 for ; Sat, 27 Sep 2014 19:39:25 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by hill (hill.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SwdfU1sEtP0y for ; Sat, 27 Sep 2014 19:39:25 -0400 (EDT) Received: from EGR authenticated sender Message-ID: <54274AAC.60602@egr.msu.edu> Date: Sat, 27 Sep 2014 19:39:24 -0400 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: dmesg seems broken References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Sep 2014 23:39:32 -0000 On 09/27/2014 19:29, Chris H wrote: >> On Sat, Sep 27, 2014 at 7:22 PM, Chris H 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? > Odd. I'm only using GENERIC modified to not contain any > hardware I'm not using. I've made zero changes to alter > buffer(s). > As I also mentioned; this too was the case from GENERIC > that came on the install media. > > 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-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > Increase kern.msgbufsize in /boot/loader.conf or MSGBUF_SIZE in your kernel config. Were you booting with -v or did the standard dmesg content just grow too large?