de0 XXX: driver didn't set ifq_maxlen

1999-02-02 Thread Neal Westfall 
Just built a kernel from code cvsup'd last night.  I get the following
messages now during boot:

de0 XXX: driver didn't set ifq_maxlen
lo0 XXX: driver didn't set ifq_maxlen

Everything otherwise seems to be working.  Are these messages
indicative of a problem?

Thanks
--
Neal Westfall  mailto:nwest...@odc.net  http://www.odc.net/~nwestfal/
FreeBSD: The Power To Serve!http://www.freebsd.org/

  $Id: dot.signature,v 1.2 1998/12/30 08:23:13 nwestfal Exp nwestfal $


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message

Re: de0 XXX: driver didn't set ifq_maxlen

1999-02-02 Thread Poul-Henning Kamp 
In message pine.lnx.4.04.9902021128470.9384-100...@vorlon.odc.net, Neal Westf
all writes:
Just built a kernel from code cvsup'd last night.  I get the following
messages now during boot:

de0 XXX: driver didn't set ifq_maxlen
lo0 XXX: driver didn't set ifq_maxlen

Everything otherwise seems to be working.  Are these messages
indicative of a problem?

No, the XXX: in general means Somebody should do something
about this, but it is probably not a problem.  The maintainers
for the respective drivers will hopefully take notice and fix
this buglet soon.

--
Poul-Henning Kamp FreeBSD coreteam member
p...@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 majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message