From owner-freebsd-bugs Mon Sep 2 10:30:03 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA03351 for bugs-outgoing; Mon, 2 Sep 1996 10:30:03 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA03344; Mon, 2 Sep 1996 10:30:01 -0700 (PDT) Date: Mon, 2 Sep 1996 10:30:01 -0700 (PDT) Message-Id: <199609021730.KAA03344@freefall.freebsd.org> To: freebsd-bugs Cc: From: Garrett Wollman Subject: kern/1555: kern Reply-To: Garrett Wollman Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/1555; it has been noted by GNATS. From: Garrett Wollman To: goldberg@cs.ubc.ca Cc: FreeBSD-gnats-submit@freebsd.org Subject: kern/1555: kern Date: Mon, 2 Sep 1996 13:24:28 -0400 < Aug 22 07:27:53 homebrew /kernel: nfsd send error 55 > Aug 23 07:16:49 homebrew /kernel: nfsd send error 55 Error number 55 is ENOBUFS, ``No buffer space available''. There are a number of possible causes for this error: 1) Your machine is out of mbufs. Recompile with more. 2) Your network interface is hosed. Sometimes, if bad things happen inside a driver, output packet processing can come to a halt without the kernel knowing about it; if this happens when the queue is full, it will get stuck. (I used to see this one a lot when working on my experimental polling code.) 3) Your network interface is really busy. If the messages come only intermittently, this is the most likely cause. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick