From owner-freebsd-questions@FreeBSD.ORG Sat May 27 10:15:52 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C188516A524 for ; Sat, 27 May 2006 10:15:52 +0000 (UTC) (envelope-from jorn@wcborstel.nl) Received: from mail.wcborstel.com (wcborstel.demon.nl [83.160.142.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 477D243D46 for ; Sat, 27 May 2006 10:15:51 +0000 (GMT) (envelope-from jorn@wcborstel.nl) Received: from localhost (mail [192.168.1.151]) by mail.wcborstel.com (Postfix) with ESMTP id 04BB6284C33 for ; Sat, 27 May 2006 12:15:51 +0200 (CEST) Received: from mail.wcborstel.com ([192.168.1.151]) by localhost (mail.wcborstel.com [192.168.1.151]) (amavisd-new, port 10024) with ESMTP id 05026-05 for ; Sat, 27 May 2006 12:15:39 +0200 (CEST) Received: from [192.168.0.2] (unknown [192.168.1.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.wcborstel.com (Postfix) with ESMTP id EA143284BA8 for ; Sat, 27 May 2006 12:15:38 +0200 (CEST) Message-ID: <447826C4.30604@wcborstel.nl> Date: Sat, 27 May 2006 12:15:32 +0200 From: Jorn Argelo User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at wcborstel.com Subject: dhclient in giant lock after a few days X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 May 2006 10:15:56 -0000 Hi all, My FreeBSD server at home is running natd and ipfw on 6.1-STABLE. So it's the router and firewall for me at home. However, after a few days the dhclient, used for obtaining an IP address from my ISP (and the FreeBSD box gets that external IP address) gets into the giant lock and won't come out unless I kill dhclient and restart it again. Note that the dhclient runs fine for a few days first. After it comes in the giant lock, the functionality doesn't break or anything, it's just unusual behavior. I've been running 6.0 on this box first, where this behavior did not appear. However, after upgrading to 6.1-PRERELEASE (this was not intended, but that's besides the point) I've been experiencing this. Since it was a version before the betas I figured this would be fixed with the release of 6.1. However, I still have the same issue after upgrading to 6.1-STABLE. This is a little snapshot from top. And yes, it is constantly the most highest process when no HTTP or SMTP traffic passes trough. last pid: 5339; load averages: 0.09, 0.06, 0.01 up 9+15:47:15 12:04:13 105 processes: 1 running, 103 sleeping, 1 lock CPU states: % user, % nice, % system, % interrupt, % idle Mem: 177M Active, 164M Inact, 82M Wired, 26M Cache, 57M Buf, 17M Free Swap: 935M Total, 280K Used, 934M Free PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 193 _dhcp 1 96 0 1460K 964K *Giant 172:09 5.57% dhclient Note that this box has 6 jails with Postfix, Apache, BIND, MySQL and stuff like that. Also I'm using the vr(4) drivers for my NICs. Yes, I know that they aren't all that great, but that's the only thing I can use, since my VIA box doesn't have space for an external NIC. So if anybody has any advices or ideas, I'd really appreciate it. Thank you in advance. Jorn