From owner-freebsd-current@FreeBSD.ORG  Fri Sep 11 17:25:29 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 AC1F91065693
	for <freebsd-current@freebsd.org>; Fri, 11 Sep 2009 17:25:29 +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 346768FC0A
	for <freebsd-current@freebsd.org>; Fri, 11 Sep 2009 17:25:28 +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
	n8BHOCJD031972
	for <freebsd-current@freebsd.org>; Fri, 11 Sep 2009 19:24:12 +0200
From: Pieter de Goeje <pieter@degoeje.nl>
To: freebsd-current@freebsd.org
Date: Fri, 11 Sep 2009 19:24:10 +0200
User-Agent: KMail/1.9.10
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200909111924.10927.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
Subject: 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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2009 17:25:29 -0000

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

-- 
Pieter de Goeje