From owner-freebsd-stable@FreeBSD.ORG Sun Nov 25 06:21:02 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 941D3780 for ; Sun, 25 Nov 2012 06:21:02 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id C8D348FC08 for ; Sun, 25 Nov 2012 06:21:01 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id qAP6KqGS011064; Sun, 25 Nov 2012 17:20:52 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sun, 25 Nov 2012 17:20:52 +1100 (EST) From: Ian Smith To: Lars Engels Subject: Re: Increasing the DMESG buffer.... In-Reply-To: <1ab82c79bc6d72fdaa90e7ed0c794f5f@mail.0x20.net> Message-ID: <20121125165737.V21191@sola.nimnet.asn.au> References: <50AD0E82.3070706@digiware.nl> <20121121194142.8c4bf7d1977f13801a021ccc@getmail.no> <20121122144400.M21191@sola.nimnet.asn.au> <20121122213328.J21191@sola.nimnet.asn.au> <50AE36FF.7080106@FreeBSD.org> <20121122224906.GE88593@in-addr.com> <20121123150719.M21191@sola.nimnet.asn.au> <1ab82c79bc6d72fdaa90e7ed0c794f5f@mail.0x20.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Nov 2012 06:21:02 -0000 On Fri, 23 Nov 2012 11:33:21 +0100, Lars Engels wrote: > Am 23.11.2012 05:50, schrieb Ian Smith: > > On Thu, 22 Nov 2012 16:20:52 -0800, Kevin Oberman wrote: [..] > > > >> Also, isn't the entire verbose boot captured in /var/run/dmesg? > > > > > > > > Only if the message buffer hasn't overflowed before the utility runs > > to > > > > populate the file > > > > > > Ouch! I did miss hte obvious. Thanks for pointing this out. > > > > I've noticed quite a few truncated verbose dmesgs posted over the last > > couple of years, sometimes frustratingly starting after important stuff > > like the CPU info or ACPI tables etc .. Lars presumably had increased > > his buffer size to capture 85k, which would be well less than Adrian's > > suggested 64k with more minimal hda + pcm logging. Perhaps a debug.snd. > > or something tunable could reenable the higher verbosity if/when needed? > > > No, I was creating the dmesg on a vanilla FreeBSD 10-CURRENT kernel and the > other one on PC-BSD 9.1-RCsomething. Well that's interesting, excuse my assumption. But as downloaded: -rw-r--r-- 1 smithi smithi 82415 Nov 22 14:08 T61_dmesg.boot.10.works So is the default msgbufsize on 10 different to what mav@ just posted? > kern.msgbufsize="65536" # Set size of kernel message buffer And if the PC-BSD 9.1-RCsomething one you refer to is: http://bsd-geek.de/FreeBSD/T61_dmesg.boot.9.works then that's only 37844 bytes and has most of its head missing, in fact starting only a screenful before the hda stuff that's most of the rest. cheers, Ian