From owner-freebsd-bugs@FreeBSD.ORG Fri Aug 18 14:00:40 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 5F87E16A4DD for ; Fri, 18 Aug 2006 14:00:40 +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 BD59A43D49 for ; Fri, 18 Aug 2006 14:00:39 +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 k7IE0dm3048540 for ; Fri, 18 Aug 2006 14:00:39 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k7IE0dUl048539; Fri, 18 Aug 2006 14:00:39 GMT (envelope-from gnats) Date: Fri, 18 Aug 2006 14:00:39 GMT Message-Id: <200608181400.k7IE0dUl048539@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Brooks Davis 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: Brooks Davis List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Aug 2006 14:00:40 -0000 The following reply was made to PR bin/102226; it has been noted by GNATS. From: Brooks Davis To: Joost Bekkers Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/102226: dhclient stops working, 100% cpu and logs at ~4000 lines/sec Date: Fri, 18 Aug 2006 08:56:44 -0500 > >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. -- Brooks