Date: Fri, 05 Feb 1999 10:57:22 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: conrads@neosoft.com Cc: current@FreeBSD.ORG Subject: Re: ifq_maxlen problem... Message-ID: <2361.918208642@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 04 Feb 1999 19:20:23 CST." <XFMail.990204192023.conrads@neosoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <XFMail.990204192023.conrads@neosoft.com>, Conrad Sabatier writes: > >On 04-Feb-99 Jaroslaw Bazydlo wrote: >> After yesterdays 'make world' I am having such warnings: >> >> FreeBSD 4.0-CURRENT #0: Thu Feb 4 17:19:09 GMT 1999 >> jarekb@ent.freebsd.org.pl:/usr/src/sys/compile/ENT >> [...] >> ep0 at 0x300-0x30f irq 10 on isa >> ep0: utp/bnc[*UTP*] address 00:60:08:65:d6:8d >> [...] >> ep0 XXX: driver didn't set ifq_maxlen >> lo0 XXX: driver didn't set ifq_maxlen >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> The system itself seems to work fine (for last 24 hrs). What do those >> messages mean??? Does anyone of you noticed similar messages??? >> >> The NIC is 3com 3c509B. > >Just cvsup'ed, made world and kernel today (Thursday, 2/4), and am seeing >the same thing at bootup (on lo0; I have no network interfaces installed). >No idea what it means or what's causing it, but it seems pretty harmless. I've already answered once: this is a note to driver developers. I would also point out that stuff like this can be easily found with grep over the kernel sources and examination of the cvs log message would explain it in more detail. I mean, you guys are not running -current without reading committ messages, right ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2361.918208642>