From owner-freebsd-questions@FreeBSD.ORG Tue Jun 17 13:38:49 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3205637B401 for ; Tue, 17 Jun 2003 13:38:49 -0700 (PDT) Received: from pa-plum1b-166.pit.adelphia.net (pa-plum1b-217.pit.adelphia.net [24.53.161.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A50B43F75 for ; Tue, 17 Jun 2003 13:38:48 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com (working [172.16.0.95]) h5HKcfOg005877; Tue, 17 Jun 2003 16:38:42 -0400 (EDT) (envelope-from wmoran@potentialtech.com) Message-ID: <3EEF7C51.3090402@potentialtech.com> Date: Tue, 17 Jun 2003 16:38:41 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gary Jennejohn References: <200306172011.h5HKBUN4011919@peedub.jennejohn.org> In-Reply-To: <200306172011.h5HKBUN4011919@peedub.jennejohn.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org cc: jaime@snowmoon.com Subject: Re: ping: sendto: No buffer space available X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2003 20:38:49 -0000 Gary Jennejohn wrote: > Bill Moran writes: > >>>jaime@snowmoon.com wrote: >>> It looks like something is causing it to pile up packets in the >>>buffers temporarily. Any thoughts? In the mean time, I will see if I can >>>dig up a PCI ethernet card. >> >>Yes, but it doesn't look like the pile is deep enough that it should have run >>out of buffer space. > > The ``No buffer space available'' message generally has _nothing at all_ > to do with whether there are enough mbufs available. It really means > that the send queue in the driver is full and no further packets can > be added to it until it drains soemwhat. > > The message indicates that, for some reason, the driver can't send > out any packets on the wire. So the comment that I made that it was either a driver, NIC, or link-level problem was near the mark? > For some reason most people think that this message means they've run > out of mbufs. Examination of the source would quickly disabuse them > of this idea. My original comment was meant to say that. But apparently I didn't communicate well enough. I spent a while looking through the source to get a better idea of where that error originates, and only got frustrated. As a favor, can you point me to the area of the source from which I can learn more of this? -- Bill Moran Potential Technologies http://www.potentialtech.com