Date: Wed, 30 Oct 1996 14:41:28 -0500 (EST) From: Christopher Sedore <cmsedore@mailbox.syr.edu> To: FreeBSD hackers <freebsd-hackers@freebsd.org> Subject: Re: Verbose babble in if_fddisubr.c Message-ID: <Pine.SOL.3.95.961030143906.17752A-100000@rodan.syr.edu> In-Reply-To: <199610301638.RAA06231@ida.interface-business.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>
> i've just got a call by a customer who's using a DEC DEFPA FDDI card
> now. She told me that everything works fine (once i've pointed her to
> the `pseudo-device fddi') but has been a little scared by some verbose
> babble caused by the driver.
>
> After digging around and looking up the error messages, it looks to me
> that they've got all kinds of weird frames and packets on their wire,
> so the following two printf's hit often enough:
>
> (sys/net/if_fddisubr.c)
>
> default:
> printf("fddi_input: unknown protocol 0x%x\n", fddi_type);
>
> ....
> default:
> printf("fddi_input: unknown dsap 0x%x\n", l->llc_dsap);
> ifp->if_noproto++;
>
> I think both printf's are merely nice debugging aids to see all the
> garbage that flies along your wire :), but nothing to be dropped onto
> a regular user. I therefore suggest hiding them inside either some
> #ifdef, or at least behind `bootverbose'.
This is a good idea. I have IPX on my FDDI wire, and this gets annoying
in a hurry. Commenting these out is step number 4 in preparing a machine
for use around here. How about #ifdef FDDI_VERBOSE or FDDI_DEBUG?
-Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SOL.3.95.961030143906.17752A-100000>