From owner-freebsd-current@FreeBSD.ORG Fri Sep 11 19:28:24 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D726106566C for ; Fri, 11 Sep 2009 19:28:24 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from smtp.utwente.nl (smtp1.utsp.utwente.nl [130.89.2.8]) by mx1.freebsd.org (Postfix) with ESMTP id 12B698FC17 for ; Fri, 11 Sep 2009 19:28:23 +0000 (UTC) Received: from lux.student.utwente.nl (lux.student.utwente.nl [130.89.170.81]) by smtp.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id n8BJSGJD019785; Fri, 11 Sep 2009 21:28:16 +0200 From: Pieter de Goeje To: freebsd-current@freebsd.org, pyunyh@gmail.com Date: Fri, 11 Sep 2009 21:28:15 +0200 User-Agent: KMail/1.9.10 References: <200909111924.10927.pieter@degoeje.nl> <20090911173756.GA1100@michelle.cdnetworks.com> In-Reply-To: <20090911173756.GA1100@michelle.cdnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909112128.15645.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact icts.servicedesk@utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: Subject: Re: BETA3: network processes hang in keglimit (unkillable) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Sep 2009 19:28:24 -0000 On Friday 11 September 2009, Pyun YongHyeon wrote: > On Fri, Sep 11, 2009 at 07:24:10PM +0200, Pieter de Goeje wrote: > > I just experienced a complete loss of network, where every network > > related process would sleep on "keglimit". I was unable to recover from > > this situation. I tried killing the processes with SIGKILL, but it didn't > > work, and I tried to bring the network interface (em) down and up again, > > which also didn't work. A reboot "solved" the problem. The machine was > > handling some major traffic, both TCP and UDP. > > > > Apparently the system was waiting on some resource to free up, but what > > could it be? How can this situation be avoided in the future? > > > > uname: 8.0-BETA3 FreeBSD 8.0-BETA3 #1: Sun Aug 30 01:23:36 CEST 2009 > > amd64 > > Both em(4) and igb(4) had mbuf leak bug which was recently fixed by > Jack. Check mbuf statistics with "netstat -m" and see whether > you've reached mbuf resource limit(see 4K jumbo cluster counter). > The leak can be easily seen on UDP traffic, especially NFS over UDP. Ok, that matches my usage (NFS over UDP), so I will monitor mbuf usage and test Jack's fixes when they're MFCed (or sooner if I can reproduce this). Thank you for your reply, Pieter de Goeje