Date: Thu, 22 Nov 2012 10:22:10 +0100 From: "Ronald Klop" <ronald-freebsd8@klop.yi.org> To: freebsd-stable@freebsd.org Subject: Re: Increasing the DMESG buffer.... Message-ID: <op.wn54a8ph8527sy@ronaldradial.versatec.local> In-Reply-To: <CAJ-Vmonk2RS=FwpgVHpeuFF5jf%2BSjE2Hv8kOFBrDCkv-=hTYSg@mail.gmail.com> 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> <op.wn4141f88527sy@212-182-167-131.ip.telfort.nl> <CAJ-VmomREO6uj_izmD%2Bp90cFn=AQcz7UbZNkX8PVnU5mG_8ufQ@mail.gmail.com> <20121122144400.M21191@sola.nimnet.asn.au> <CAJ-Vmonk2RS=FwpgVHpeuFF5jf%2BSjE2Hv8kOFBrDCkv-=hTYSg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 22 Nov 2012 08:12:17 +0100, Adrian Chadd <adrian@freebsd.org> wrote: > On 21 November 2012 20:16, Ian Smith <smithi@nimnet.asn.au> wrote: >> On Wed, 21 Nov 2012 12:08:42 -0800, Adrian Chadd wrote: >> > .. because some of us like kernel behaviour to be predictable and >> > controllable, rather than 'just be dynamic here, what could possibly >> > go wrong.' >> > >> > Just bump the default kernel buffer size up to 64k and leave it >> > hard-coded like that. Us embedded people can drop that down to >> > something smaller. >> > >> > There. Problem solved, right? >> >> Well maybe, but I still tend to take Andriy's point about snd_hda. For >> example, Lars Engels posted several verbose dmesgs the other day, not to >> do with sound, one of which was: >> http://bsd-geek.de/FreeBSD/T61_dmesg.boot.10.works >> >> T61_dmesg.boot.10.works (file 1 of 2) lines 1813-1861/1861 byte >> 82415/82415 >> >> Cutting just the hdaa0, pcm0 and pcm1 stuff results in: >> >> hda_pcm.verbose (file 2 of 2) lines 712-760/760 byte 28531/28531 > > Is there a way to extract this topology information out of the driver > without putting it in the verbose output? > > Adrian Maybe via /dev/sndstat. See hw.snd.verbose in sound(4). An additional level 5 for super verbose information? Ronald.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wn54a8ph8527sy>