From owner-freebsd-current Sun Feb 14 22:28:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11036 for freebsd-current-outgoing; Sun, 14 Feb 1999 22:28:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-30.ppp.wenet.net [206.15.85.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11031 for ; Sun, 14 Feb 1999 22:28:28 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.2/8.9.1) with ESMTP id WAA01939; Sun, 14 Feb 1999 22:25:30 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sun, 14 Feb 1999 22:25:30 -0800 (PST) From: Alex Zepeda To: Kris Kennaway cc: freebsd-current@FreeBSD.ORG Subject: Re: 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 Mon, 15 Feb 1999, Kris Kennaway wrote: > 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. FWIW I'm seeing this at bootup now: ep0 XXX: driver didn't set ifq_maxlen lo0 XXX: driver didn't set ifq_maxlen changing root device to wd0s1a link_elf: symbol grow undefined Ahh well guess I get to buildworld now... - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message