From owner-freebsd-current Sun Feb 14 14:53:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21364 for freebsd-current-outgoing; Sun, 14 Feb 1999 14:53:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21357 for ; Sun, 14 Feb 1999 14:53:00 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id JAA01247; Mon, 15 Feb 1999 09:22:57 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA13456; Mon, 15 Feb 1999 09:22:54 +1030 Date: Mon, 15 Feb 1999 09:22:54 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Brian Feldman Cc: freebsd-current@FreeBSD.ORG Subject: XXX: driver didn't set ifq_maxlen (was Re: Disk locks and weird things) In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 Feb 1999, Brian Feldman wrote: > > I'm also getting messages from de0 and lo0 that say: > > > > de0 XXX: driver didn't set ifq_maxlen > > That's mostly harmless. It's a warning to driver maintainers that was just > put in recently; the driver hasn't ever set ifq_maxlen, no doubt. I see this on lo0 every time I boot - is this a problem in 3.1 as well, or just -current? It's probably not good to leave these messages in 3.1 as it ships, if the former. Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message