From owner-freebsd-current@FreeBSD.ORG Thu Aug 11 16:13:22 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEA2116A420 for ; Thu, 11 Aug 2005 16:13:22 +0000 (GMT) (envelope-from jahnke@fmjassoc.com) Received: from smtp.wizwire.com (smtp.wizwire.com [209.218.100.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E2DD43D45 for ; Thu, 11 Aug 2005 16:13:21 +0000 (GMT) (envelope-from jahnke@fmjassoc.com) Received: from pinot.fmjassoc.com (209.218.101.53.bvi2.wizwire.com [209.218.101.53]) by smtp.wizwire.com (8.13.1/8.13.1) with ESMTP id j7BGDGtW029663 for ; Thu, 11 Aug 2005 09:13:17 -0700 From: Frank Jahnke To: freebsd-current@freebsd.org Content-Type: text/plain Organization: Sonata Biosciences, Inc. Date: Thu, 11 Aug 2005 09:07:56 -0700 Message-Id: <1123776476.645.7.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-WizWire-MailScanner-Information: Please contact the ISP for more information X-MailScanner-From: jahnke@fmjassoc.com X-Mailman-Approved-At: Fri, 12 Aug 2005 11:46:41 +0000 Subject: 6.0-Beta2: dhclient instability X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jahnke@fmjassoc.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2005 16:13:22 -0000 I have a problem with dhclient becoming unstable. I'm running 6.0-beta2 and Gnome 2.10 on a dual Althon machine. On boot, everything is fine. After visiting a few web pages with Epiphany, dhclient goes from a minor process to one that consumes an entire CPU. The machine is still reasonably responsive, but needless to say, its capacity goes way down. It does not seem to be related to the web site visited, or the scheduler used (ULE or 4BSD). Downloading mail repeatedly also does not trigger the problem. Any ideas? Frank