From owner-freebsd-stable Thu May 1 14:04:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA16767 for stable-outgoing; Thu, 1 May 1997 14:04:17 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA16762 for ; Thu, 1 May 1997 14:04:14 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id OAA29970; Thu, 1 May 1997 14:05:27 -0700 (PDT) Message-Id: <199705012105.OAA29970@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Kachun Lee cc: freebsd-stable@freebsd.org Subject: Re: kmem_map full with 2.2beta to 2.2-releng-970422 In-reply-to: Your message of "Thu, 01 May 1997 09:50:33 -0000." <1.5.4.32.19970501095033.006e6dc8@dopey.pathlink.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 01 May 1997 14:05:27 -0700 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >clients, and our NFS servers have quite a lot of these: > > /kernel: nfsd send error 55 > >They does not seem cause any ill effect. I assume 55=ENOBUFS No buffer space >available. But I thought with the unified VM/Buffer, there are no MAXBUFFER >setting any more. Do you know what parameter I should adjust? ...that one indicates that network buffers were depleted. This usually happens when the interface queue reaches it's limit of 50 queued packets, although it can also happen if the global pool of network buffers is deleted. The most common cause of this error is a stuck network device driver - some NICs, for example will stop sending if the cable is unplugged. It can also happen on PPP/SLIP lines if hardware flow control (CTS) stays de-asserted too long. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project