From owner-freebsd-current@FreeBSD.ORG Mon Sep 29 18:26:00 2014 Return-Path: Delivered-To: freebsd-current@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 D139B399 for ; Mon, 29 Sep 2014 18:26:00 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id AC7D8FB for ; Mon, 29 Sep 2014 18:26:00 +0000 (UTC) Received: from [172.16.0.139] (unknown [92.247.20.226]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 04E8456288 for ; Mon, 29 Sep 2014 18:25:58 +0000 (UTC) Message-ID: <5429A434.5040008@freebsd.org> Date: Mon, 29 Sep 2014 14:25:56 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: dmesg seems broken References: <54298AEB.9070700@freebsd.org> <13dd6d3eab3735353f5309a223dc1799.authenticated@ultimatedns.net> In-Reply-To: <13dd6d3eab3735353f5309a223dc1799.authenticated@ultimatedns.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 18:26:00 -0000 On 2014-09-29 14:22, Chris H wrote: >> On 09/29/2014 10:31, 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? >>> 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" >>>> >>> >>> _______________________________________________ >>> 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" >>> >> >> Try adding the sysctl to your loader.conf so it is set earlier > Thank you for the reply, Allan. > I bumped kern.msgbufsize quite a bit within loader.conf. That's how I > discovered that that tunable worked. But then needed to eek it down, > until I found the actual top of the output -- had to bounce the box > quite a few times. :P > >> >> I don't think the size was reduced, you may just have a lot of messages. > ODD. Because running RELENG_8, or 11-CURRENT on the same hardware, and yes, > with BOOT_VERBOSE && VERBOSE_LOADING. I received the entire buffer. > > Thanks again, Allan. > > --Chris > >> >> -- >> Allan Jude Do you actually see a difference in the size of kern.msgbufsize between RELENG_8 and the RELENG_9 box that is exhibiting issues? -- Allan Jude