From owner-freebsd-stable@FreeBSD.ORG Thu Nov 22 22:15:06 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 B83F4964; Thu, 22 Nov 2012 22:15:06 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id CBB028FC14; Thu, 22 Nov 2012 22:15:05 +0000 (UTC) Received: by mail-ee0-f54.google.com with SMTP id c13so6083142eek.13 for ; Thu, 22 Nov 2012 14:14:59 -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=WiN1ft5IXMaiVaU1zeiG6vS7CBJkaDb89/jIY+VHzBU=; b=G5Bfn1CxUgM9LJNHcR0kuCe8JXlczPXleHuSGaWYy/lj7JHL8x7ErBT88CV85kyugW 8AHb4PoYTvaOBTOR4qdC61GEUBy22KlSAYX/bBBkBiOTOTgFLEDonBiDj7+0zWMqPX0H VjMaDmrvGDDH+eIOn4nqRHldX05t1Qm90A8/N1t+Bj4CmBPNVo5my8j8lGCDbzAezsIj k3NpAtDnwxifs0Ayl1evuk7QdlersSBS+VsWp39hjp/6rSBAlClSuKokYDX3aDLuH5Hd qIE+k783whGYQV/T3v/h3XUVgUn7b9pMLTlFQAbcwdY73gBP57TRT2qr9oiXWBa7582h jOog== MIME-Version: 1.0 Received: by 10.14.194.72 with SMTP id l48mr5942466een.9.1353622499337; Thu, 22 Nov 2012 14:14:59 -0800 (PST) Received: by 10.223.71.199 with HTTP; Thu, 22 Nov 2012 14:14:59 -0800 (PST) In-Reply-To: References: <50ACA59D.3080809@digiware.nl> <20121121101411.GG4535@server.rulingia.com> <50ACD522.7000706@digiware.nl> <50ACEE5B.8000901@FreeBSD.org> <50ACF891.4050105@digiware.nl> <1353513692.69940.7.camel@revolution.hippie.lan> <50ACFC6C.8070506@FreeBSD.org> <20121122040251.G21191@sola.nimnet.asn.au> <50AD0E82.3070706@digiware.nl> <20121121194142.8c4bf7d1977f13801a021ccc@getmail.no> <20121122144400.M21191@sola.nimnet.asn.au> <20121122213328.J21191@sola.nimnet.asn.au> <50AE36FF.7080106@FreeBSD.org> Date: Thu, 22 Nov 2012 14:14:59 -0800 Message-ID: Subject: Re: Increasing the DMESG buffer.... From: Kevin Oberman To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: Andriy Gapon , Alexander Motin , freebsd-stable@freebsd.org, Ian Smith , 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: Thu, 22 Nov 2012 22:15:06 -0000 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? -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com