From owner-freebsd-hackers Mon Feb 11 11:33:53 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 6AF9237B402 for ; Mon, 11 Feb 2002 11:33:25 -0800 (PST) Received: from sasami.jurai.net (winter@sasami.jurai.net [64.0.106.45]) by sasami.jurai.net (8.9.3/8.9.3) with ESMTP id OAA13765; Mon, 11 Feb 2002 14:33:17 -0500 (EST) (envelope-from winter@jurai.net) Date: Mon, 11 Feb 2002 14:33:17 -0500 (EST) From: "Matthew N. Dodd" To: Jonathan Hanna Cc: vs3volod@yahoo.com, hackers@FreeBSD.ORG Subject: RE: ping: sendto: No buffer space available In-Reply-To: <200202092056.g19Ku8j00368@207-194-143-195.dsl.axion.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Man, good catch. Thats been troubling everyone for a long time. I've never been able to reproduce it (likely because of the slow machines my test cards were in.) On Sat, 9 Feb 2002, Jonathan Hanna wrote: > This looks like the bug in the "ep" driver. When the interrupt routine > gets both TX and RX interrupts it acknowledges both but only services > the read. Karl Dietz, is working on an overhaul > but my quick fix is to take out the "continue" after the "epread()" in > ep_intr(). The buffer talked about is actually the ep queue being full. > > --- if_ep.c Fri Feb 1 19:51:43 2002 > +++ if_ep.c.fix Sat Feb 9 12:49:31 2002 > @@ -571,7 +571,6 @@ > > if (status & (S_RX_COMPLETE | S_RX_EARLY)) { > epread(sc); > - continue; > } > if (status & S_TX_AVAIL) { > /* we need ACK */ > > Karl Dietz > On 09-Feb-02 vs3volod@yahoo.com wrote: > > > > Some times connections to my host freeze. > > What buffer ping talks about? > > > > ~:# ping p109 > > ping: sendto: No buffer space available > > ping: sendto: No buffer space available > > ping: sendto: No buffer space available > > ping: sendto: No buffer space available > > PING p109.f434.n5020.z2.fidonet.org (192.168.44.109): 56 data bytes > > > > --- p109.f434.n5020.z2.fidonet.org ping statistics --- > > 4 packets transmitted, 0 packets received, 100% packet loss > > ~:# pstat -T > > 236/1064 files > > 0M/255M swap space > > ~:# netstat -m > > 97/128/4096 mbufs in use (current/peak/max): > > 49 mbufs allocated to data > > 48 mbufs allocated to packet headers > > 17/28/1024 mbuf clusters in use (current/peak/max) > > 88 Kbytes allocated to network (2% of mb_map in use) > > 0 requests for memory denied > > 0 requests for memory delayed > > 0 calls to protocol drain routines > > ~:# ifconfig > > ep0: flags=8c43 mtu 1500 > > inet 192.168.44.41 netmask 0xffffff00 broadcast 192.168.44.255 > > inet6 fe80::2a0:24ff:fe46:b823%ep0 prefixlen 64 scopeid 0x1 > > inet 192.168.44.42 netmask 0xffffffff broadcast 192.168.44.42 > > ether 00:a0:24:46:b8:23 > > media: Ethernet 10baseT/UTP > > faith0: flags=8000 mtu 1500 > > stf0: flags=0<> mtu 1280 > > lo0: flags=8049 mtu 16384 > > inet6 ::1 prefixlen 128 > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > > inet 127.0.0.1 netmask 0xff000000 > > ppp0: flags=8051 mtu 1500 > > inet 192.168.10.202 --> 192.168.3.3 netmask 0xffffff00 > > ppp1: flags=8010 mtu 1500 > > ~:# uname -a > > FreeBSD f434.n5020.z2.fidonet.org 4.4-STABLE FreeBSD 4.4-STABLE #1: Wed Dec 26 22:47:45 MSK 2001 root@f434.n5020.z2.fidon > et.org:/usr/src/sys/compile/PP i386 > > ~:# > > > > > > Seva. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > Jonathan Hanna > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message