Date: Mon, 23 Jan 2006 23:25:25 +0100 From: Krzysztof Kowalik <kkowalik@uci.agh.edu.pl> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: freebsd-stable@freebsd.org Subject: Re: dhclient wedged Message-ID: <20060123222525.GA4084@uci.agh.edu.pl> In-Reply-To: <20060123214226.GA11995@odin.ac.hmc.edu> References: <43D339CC.3020204@forrie.com> <20060122155131.GA823@the-grills.com> <20060122221828.GA7703@odin.ac.hmc.edu> <20060123090656.GA22255@uci.agh.edu.pl> <20060123214226.GA11995@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Brooks Davis <brooks@one-eyed-alien.net> wrote: > What NIC are you using? fxp0: <Intel 82559 Pro/100 Ethernet> port 0xc000-0xc03f mem 0xdb121000-0xdb121fff,0xdb000000-0xdb0fffff irq 11 at device 1.0 on pci2 > This particular issue sounds like a NIC returning corrupt packets for > some reason. Alternatively, the sending server could be producing corrupt > packets. Some tcpdump traces (preferably raw dumps) could be useful. As I said, I didn't see anything bad in the tcpdump. And since I really didn't have such issues before, and I don't see anything weird in any other place... I recompiled dhclient with "-g" and will tcpdump the traffic again, if I notice it eating 99% of CPU time again. -- Krzysztof Kowalik | () ASCII Ribbon Campaign Computer Center, AGH UST | /\ Support plain text e-mail
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060123222525.GA4084>