Date: Wed, 3 Nov 2004 18:31:49 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/em if_em.c Message-ID: <Pine.BSF.4.53.0411031818150.1747@e0-0.zab2.int.zabbadoz.net> In-Reply-To: <23321.1099505551@critter.freebsd.dk> References: <23321.1099505551@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 3 Nov 2004, Poul-Henning Kamp wrote: > In message <200411031408.03949.jhb@FreeBSD.org>, John Baldwin writes: > > >I think bootverbose needs to be split up some. Imagine having a > >'verbose.ether' tunable that would turn on dumping all the MAC addresses for > >NICs but would be off by default. Many of the interrupt messages on x86 need > >to move from bootverbose to some kind of apic_verbose. Might even be nice to > >have some kind of acpi-like verbose variable that could be set as: > > > >set verbose="boot,apic,ether" > > I think that would be overkill. I think it's overkill to enable all verbose msgs just to see link state messages in my logs again when someone fiddles at the cabling in the colo hotel where he shouldn't - or did I mis-read the commit message ? I am totally agreeing that some changes (including my latest sk patch) my be far too verbose for many things in default configuration but enabling all to get one thing back - isn't that overkill ? The better question should perhaps be if it's best to put things under boot_verbose if they can also be printed at runtime ? -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.53.0411031818150.1747>