From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 19:55:28 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 D155F16A41F for ; Wed, 27 Jul 2005 19:55:28 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A16643D45 for ; Wed, 27 Jul 2005 19:55:28 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id j6RJva3P090564; Wed, 27 Jul 2005 15:57:36 -0400 (EDT) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: NIKSUN, Inc. To: Brooks Davis Date: Wed, 27 Jul 2005 15:54:58 -0400 User-Agent: KMail/1.6.2 References: <42E58007.9030202@rogers.com> <20050726233933.GA13679@odin.ac.hmc.edu> <20050727191043.GA17885@odin.ac.hmc.edu> In-Reply-To: <20050727191043.GA17885@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200507271555.00945.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.85.1/994/Wed Jul 27 04:28:09 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Wilko Bulte , freebsd-current@FreeBSD.org, Mike Jakubik Subject: Re: dhclient taking all cpu 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: Wed, 27 Jul 2005 19:55:28 -0000 On Wednesday 27 July 2005 03:10 pm, Brooks Davis wrote: > I think I've found it. There was a really odd typo (= instead of > +) in the code that handles undersized captures on the bpf socket. > Please try the following patch and see if it solves the problem. > I'm testing here, but I don't have a reliable way to trigger the > bug. The fix is fairly obvious so I'll commit it to head shortly. Good catch! It seems to fix my 'infinite loop' problem. One more problem to solve... I have to do the following to make bge(4) working correctly at boot time: ifconfig_bge0="up DHCP" Without `up', dhclient fails like this: bge0: link state changed to DOWN bge0: no link .............. giving up bge0: flags=8802 mtu 1500 options=1a ether xx:xx:xx:xx:xx:xx media: Ethernet autoselect (none) status: no carrier because bge(4) does not change link state while the interface is down. This problem is more serious with wireless driver because link doesn't go up until it is associated with some AP. I was always wondering which is correct. Do we have to update link state while interface is down or not? Thanks! Jung-uk Kim