Date: Sun, 24 May 1998 08:40:01 -0700 (PDT) From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) To: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/6694: Network hangs, with "No buffers available" message Message-ID: <199805241540.IAA25395@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/6694; it has been noted by GNATS. From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) To: coutinho@dextra.com.br Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/6694: Network hangs, with "No buffers available" message Date: 24 May 1998 17:39:14 +0200 coutinho@dextra.com.br writes: > # ping 192.168.0.1 > ping: sendto: No buffer space available > ping: sendto: No buffer space available > ^C > # netstat -m > 246 mbufs in use: > 109 mbufs allocated to data > 128 mbufs allocated to packet headers > 8 mbufs allocated to protocol control blocks > 1 mbufs allocated to socket names and addresses > 74/266 mbuf clusters in use > 562 Kbytes allocated to network (31% in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > > It seems that the only way to recover this problem is re-booting the > machine. This is a known problem with the ep driver. The immediate workaround is to ifconfig the interface down and up again. A more permanent workaround is to set NMBCLUSTERS to some large value, such as 4096 or 8192, in your kernel configuration file. The Correct Solution (tm) would of course be to identify and correct the error in the ep driver. -- Noone else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805241540.IAA25395>