From owner-freebsd-bugs@FreeBSD.ORG Sat Aug 19 11:20:17 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 670E316A4DA for ; Sat, 19 Aug 2006 11:20:17 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EB7043D45 for ; Sat, 19 Aug 2006 11:20:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k7JBKGit009095 for ; Sat, 19 Aug 2006 11:20:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k7JBKGtP009094; Sat, 19 Aug 2006 11:20:16 GMT (envelope-from gnats) Date: Sat, 19 Aug 2006 11:20:16 GMT Message-Id: <200608191120.k7JBKGtP009094@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Joost Bekkers Cc: Subject: Re: bin/102226: dhclient stops working, 100% cpu and logs at ~4000 lines/sec X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joost Bekkers List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Aug 2006 11:20:17 -0000 The following reply was made to PR bin/102226; it has been noted by GNATS. From: Joost Bekkers To: Brooks Davis Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/102226: dhclient stops working, 100% cpu and logs at ~4000 lines/sec Date: Sat, 19 Aug 2006 13:17:41 +0200 On Fri, Aug 18, 2006 at 08:56:44AM -0500, Brooks Davis wrote: > > >How-To-Repeat: > > > > /sbin/dhclient > > > > and wait. > > Since this happends to virtually no one else (your's sounds a lot more > repeatable than any cases I've heard previously), we'll need more > information to have any chance of reproducing this. Realistically it's > not going to be possible for me to do it since it's probably hardware > dependent (quite possible a NIC + switch/modem combination). What I'd > like you to do is is capture all dhcp traffic on the interface until > this happens so I can look at the packet stream and see what's coming in > and how we're mishandling it. I think the following should do it: > > tcpdump -i -s 0 -w dhcp.pcap port 67 > > Once you've got that, compress it and put it somewhere I can download > it. Feel free to send the trace in private e-mail if you don't want the > information to be public. > We're in luck, it already happend again. Aug 19 10:26:25 local time Capture and log are available at the site mentioned in private mail. -- greetz Joost joost@jodocus.org