From owner-freebsd-stable@FreeBSD.ORG Sat Feb 4 00:48:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9893B16A420 for ; Sat, 4 Feb 2006 00:48:22 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9330D43D46 for ; Sat, 4 Feb 2006 00:48:21 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k140mICB026295; Fri, 3 Feb 2006 16:48:18 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k140mIcl026294; Fri, 3 Feb 2006 16:48:18 -0800 Date: Fri, 3 Feb 2006 16:48:18 -0800 From: Brooks Davis To: "John T. Yocum" Message-ID: <20060204004818.GB24962@odin.ac.hmc.edu> References: <43E2F2B8.5040205@charter.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tjCHc7DPkfUGtrlw" Content-Disposition: inline In-Reply-To: <43E2F2B8.5040205@charter.net> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-stable@freebsd.org Subject: Re: dhclient wedged X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Feb 2006 00:48:22 -0000 --tjCHc7DPkfUGtrlw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 02, 2006 at 10:05:44PM -0800, John T. Yocum wrote: > I've been having a same sort of issue that others have reported. After=20 > dhclient has been running for a random length of time, it suddenly=20 > starts consuming a large amount of CPU. Unfortunately for me, the=20 > longest it tends to run is 48 hours before acting up. >=20 > I did get it rebuilt with debug symbols, and got a stack trace from it,= =20 > while it was acting up. Hopefully, it will be useful. I really need a core dump. A single stack trace just tells me the packet processing routing isn't working (or at least everything is getting rejected). Unfortunatly, I haven't had any luck finding bugs there by inspection. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --tjCHc7DPkfUGtrlw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFD4/nRXY6L6fI4GtQRAhJ3AKDZqKhLCOK4Rvn23TLi9HRB6WqpYACfTEZt 0cEaqcGJJupbY3Bx5j8YchU= =EfGF -----END PGP SIGNATURE----- --tjCHc7DPkfUGtrlw--