From owner-freebsd-hackers Sun Feb 10 15:59:37 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from f434.n5020.z2.fidonet.org (host5.mtelecom.ru [212.44.147.5]) by hub.freebsd.org (Postfix) with ESMTP id 3B85437B405 for ; Sun, 10 Feb 2002 15:59:32 -0800 (PST) Received: (from seva@localhost) by f434.n5020.z2.fidonet.org (8.11.6/8.11.3) id g1ANwn552149; Mon, 11 Feb 2002 02:58:49 +0300 (MSK) (envelope-from seva) To: Jonathan Hanna Cc: hackers@FreeBSD.ORG Subject: Re: ping: sendto: No buffer space available References: <200202092056.g19Ku8j00368@207-194-143-195.dsl.axion.net> From: User Seva Date: 11 Feb 2002 02:58:48 +0300 In-Reply-To: Jonathan Hanna's message of "Sat, 09 Feb 2002 12:56:06 -0800 (PST)" Message-ID: <86bsew99dz.fsf@f434.n5020.z2.fidonet.org> Lines: 28 X-Mailer: Gnus v5.7/Emacs 20.7 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 Thanks! I commented out "continue" in if_ep.c. There is no any "No buffer space available" any more. Seva. Jonathan Hanna writes: > 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 */ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message