From owner-freebsd-stable@FreeBSD.ORG Fri Nov 23 00:20:54 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 E8ED9950; Fri, 23 Nov 2012 00:20:54 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ea0-f182.google.com (mail-ea0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 01AAB8FC18; Fri, 23 Nov 2012 00:20:53 +0000 (UTC) Received: by mail-ea0-f182.google.com with SMTP id a14so2315136eaa.13 for ; Thu, 22 Nov 2012 16:20:52 -0800 (PST) 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=vCYyGGCOXKCSqonrMgfsoqVF4Amk1mcXnVsL8Inh7Ps=; b=C45OaToR12waNRwFFpo+iO7mMvS2bcSy1l9KZxxzFfjBuiULVOrXtYMRvArx4tQLLk e3tcqjfwx3Vcw8PUymDPy2XAnainOS03/ojL0wfCMtrrJVUgllJ4fgeKoiJpXPq9lkEK z7+OaDYsmNliDKxFujZ3EiZWOEvVeueftEaprQmgCewU/zCqRFSRltgYz9NP8X9yy5VJ rZfOWaHtRwYICVhsNaxmMguILAZsfokjdlocYsdtBhc8ZIoKu17MIx3UL7/eHrQjjXce krV1EjvTryos+xvT9g8dP2gzN/aFMBjNErdwjJfGowdBoYRAxNOMqPvi1xrXi5WHz71m ulxQ== MIME-Version: 1.0 Received: by 10.14.184.134 with SMTP id s6mr6648455eem.43.1353630052806; Thu, 22 Nov 2012 16:20:52 -0800 (PST) Received: by 10.223.71.199 with HTTP; Thu, 22 Nov 2012 16:20:52 -0800 (PST) In-Reply-To: <20121122224906.GE88593@in-addr.com> 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> Date: Thu, 22 Nov 2012 16:20:52 -0800 Message-ID: Subject: Re: Increasing the DMESG buffer.... From: Kevin Oberman To: Gary Palmer Content-Type: text/plain; charset=UTF-8 Cc: Adrian Chadd , freebsd-stable@freebsd.org, Ian Smith , Alexander Motin , Andriy Gapon , Ronald Klop 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: Fri, 23 Nov 2012 00:20:55 -0000 On Thu, Nov 22, 2012 at 2:49 PM, Gary Palmer wrote: > On Thu, Nov 22, 2012 at 02:14:59PM -0800, Kevin Oberman wrote: >> On Thu, Nov 22, 2012 at 2:05 PM, Adrian Chadd wrote: >> > On 22 November 2012 06:30, Alexander Motin wrote: >> > >> >> Neither ICH, nor any other driver I know have amount of information >> >> comparable to what HDA hardware provides. So the analogy is not good. >> >> Respecting that most CODECs have no published datasheets, that information >> >> is the only input for debugging. >> >> >> >> snd_hda also uses hw.snd.verbose=3. But it is used for even deeper driver >> >> debugging. It also enables a lot of debugging in sound(4), that can be too >> >> verbose for HDA debugging. >> >> >> >> I will recheck again how can it be reorganized, but I think that the real >> >> problem is not in HDA. We need some way to structure and filter the output. >> > >> > I honestly would like to just see it spat out using a userland tool, >> > rather than having the kernel print that level of topology data out. >> > >> > It's highly unlikely that a topology problem is going to cause a >> > system to not boot, right? So the kernel itself doesn't need to be >> > able to spit that data out. >> >> Maybe I'm missing something, but the data needed to adjust HDAC is >> available from 'sysctl dev.hdaa'. I have not looked at the verbose >> output in quite a while, but I think it is mstly or entirely hte >> information in that and 'sysctl dev.hdac'. I never needed to look >> elsewhere to get mine set up properly. >> >> 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. So we need to either expand the default buffer (not something I would want to do) or trim the verbosity of the verbose boot. Am I also missing an obvious reason most of the HDA output could not be eliminated since it is available y sysctl? -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com