From owner-freebsd-current Tue Feb 2 11:42:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22461 for freebsd-current-outgoing; Tue, 2 Feb 1999 11:42:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22452 for ; Tue, 2 Feb 1999 11:42:14 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id UAA21563; Tue, 2 Feb 1999 20:40:57 +0100 (CET) To: Neal Westfall cc: current@FreeBSD.ORG Subject: Re: de0 XXX: driver didn't set ifq_maxlen In-reply-to: Your message of "Tue, 02 Feb 1999 11:32:44 PST." Date: Tue, 02 Feb 1999 20:40:54 +0100 Message-ID: <21561.917984454@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , 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 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