From owner-freebsd-net  Thu Mar 25 13:17:44 1999
Delivered-To: freebsd-net@freebsd.org
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
	by hub.freebsd.org (Postfix) with SMTP
	id B379A14D1D; Thu, 25 Mar 1999 13:17:39 -0800 (PST)
	(envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id UAA13471; Thu, 25 Mar 1999 20:03:16 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199903251903.UAA13471@labinfo.iet.unipi.it>
Subject: Re: 3.1-STABLE dies on 40+ connects
To: j@lumiere.net (Jesse)
Date: Thu, 25 Mar 1999 20:03:16 +0100 (MET)
Cc: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
In-Reply-To: <Pine.BSF.4.05.9903251309080.493-100000@leaf.lumiere.net> from "Jesse" at Mar 25, 99 01:09:22 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 471       
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> > aren't you running out of mbufs by chance ? (it should not crash, but
> > increasing the value could help...)
> 
> It definitely does crash.

i trust you -- i suspect there is some piece of the code somewhere
which does not check for mcopy/mpullup/etc failures.

in fact it would be nice to know if there is some reproducible way to
trigger these crashes because i think this is a problem that ought to
be fixed in a better way than overallocating resources.

	luigi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message