From owner-freebsd-net@FreeBSD.ORG Mon Jul 12 08:24:43 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90F7D16A4CE for ; Mon, 12 Jul 2004 08:24:43 +0000 (GMT) Received: from mx1.imp.ch (mx1.imp.ch [157.161.9.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 081ED43D39 for ; Mon, 12 Jul 2004 08:24:43 +0000 (GMT) (envelope-from mb@imp.ch) Received: from mx2.imp.ch (mx2o [157.161.9.17]) by mx1.imp.ch (8.12.11/8.12.11) with ESMTP id i6C8OPPj024816 for ; Mon, 12 Jul 2004 10:24:26 +0200 (CEST) (envelope-from mb@imp.ch) Received: from mx2.imp.ch (localhost [127.0.0.1]) by mx2.imp.ch (8.12.11/8.12.11/Submit) with ESMTP id i6C8ONsj031768 for ; Mon, 12 Jul 2004 10:24:24 +0200 (CEST) (envelope-from mb@imp.ch) Received: (from clamav@localhost) by mx2.imp.ch (8.12.11/8.12.11/Submit) id i6C8ONmF031764 for ; Mon, 12 Jul 2004 10:24:23 +0200 (CEST) (envelope-from mb@imp.ch) Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9]) by ns1.imp.ch (MIMEDefang) with ESMTP id i6C8OJAX057532; Mon, 12 Jul 2004 10:24:23 +0200 (CEST) Date: Mon, 12 Jul 2004 10:24:19 +0200 (CEST) From: Martin Blapp To: net@freebsd.org In-Reply-To: <20040710185759.Q56824@cvs.imp.ch> Message-ID: <20040712102340.R56824@cvs.imp.ch> References: <20040710185759.Q56824@cvs.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checksum: 948eab3335ec9fb3b79b9278b3ee7add X-Virus-Status: No X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=4 tests=BAYES_00 X-Scanned-By: MIMEDefang 2.42 cc: pjd@freebsd.org Subject: Re: if_em memleak with IPv6 ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jul 2004 08:24:43 -0000 Hi all, > After reverting everything back to IPv4, the "No buffer space available" > seems to be gone. > > Maybe this is related to some other problem with this driver, (IPSEC etc). It happened ago this weekend. So it is unrelated to IP_v6 Martin