From owner-freebsd-stable@FreeBSD.ORG Fri May 24 05:47:36 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 542A27E4; Fri, 24 May 2013 05:47:36 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) by mx1.freebsd.org (Postfix) with ESMTP id 2365ED15; Fri, 24 May 2013 05:47:36 +0000 (UTC) Received: by mail-pd0-f175.google.com with SMTP id 6so3404852pdd.20 for ; Thu, 23 May 2013 22:47:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=GUSypoip906UDecrQ7QTvxBqk+Hz2SIM02+RcVFWiis=; b=PsAMrcQ7JreUzvkj/+QAmwVuhahaEr2jsy17q5k/zcCs8HZ3ZwGhebg3oRzavkkvit k2RBF22KFUOBy++wcRcga7VHK4SI8vV/aH8bIWAduoSoHfJCytW6g1NFB8SkX8408Jcm 3gtpK48laaWWqGPsNeHHCHux+Z396oOjdFnM6fheoAKtZCn81fbdOJHHW6wfP5WuiMAA odjBqpItEnzBw1l+7/T6yl0+LafgiUmsjHYk5krdeOLRhSojJeq5gCo+9N1EHCMyv6G2 GuzQBkiVpQehwT8ZoC/e9Pw+SxTvKEMvfbWqTGeBVlViySNSDOLKY99whuLqF0etSPRr DdSw== X-Received: by 10.68.13.228 with SMTP id k4mr15806483pbc.215.1369374450642; Thu, 23 May 2013 22:47:30 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPSA id bs2sm15948330pad.17.2013.05.23.22.47.27 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 23 May 2013 22:47:29 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 24 May 2013 14:47:20 +0900 From: YongHyeon PYUN Date: Fri, 24 May 2013 14:47:20 +0900 To: Jeremy Chadwick Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524054720.GA1496@michelle.cdnetworks.com> References: <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> <20130524030351.GA39091@icarus.home.lan> <20130524031303.GC28865@glenbarber.us> <20130524033806.GA39720@icarus.home.lan> <20130524034244.GD28865@glenbarber.us> <20130524044035.GA40957@icarus.home.lan> <20130524044919.GA41292@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130524044919.GA41292@icarus.home.lan> User-Agent: Mutt/1.4.2.3i Cc: Glen Barber , freebsd-stable@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 May 2013 05:47:36 -0000 On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote: > On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote: > > On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote: > > > On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote: > > > > If someone wants me to test DHCP via fxp(4) on the above system (I can > > > > do so with both NICs), just let me know; it should only take me half an > > > > hour or so. > > > > > > > > I'll politely wait for someone to say "please do so" else won't bother. > > > > > > > > > > For the sake of completeness... > > > > > > "Please do so." :) > > > > Issue reproduced 100% reliably, even within sysinstall. > > > > {snip} > > Forgot to add: > > This issue ONLY happens when using DHCP. > > Statically assigning the IP address works fine; fxp0 goes down once, > up once, then stays up indefinitely. I asked Mike to try backing out dhclient(8) change(r247336) but it seems he missed that. Jeremy, could you try that? I guess dhclient(8) does not like flow-control negotiation of fxp(4) after link establishment. > > I also tested network I/O in the statically-assigned scenario. Pinging > the box from another machine on the LAN: > > $ ping 192.168.1.192 > PING 192.168.1.192 (192.168.1.192): 56 data bytes > 64 bytes from 192.168.1.192: icmp_seq=0 ttl=64 time=0.180 ms > 64 bytes from 192.168.1.192: icmp_seq=1 ttl=64 time=0.138 ms > 64 bytes from 192.168.1.192: icmp_seq=2 ttl=64 time=0.214 ms > 64 bytes from 192.168.1.192: icmp_seq=3 ttl=64 time=0.165 ms > 64 bytes from 192.168.1.192: icmp_seq=4 ttl=64 time=0.114 ms > ^C > --- 192.168.1.192 ping statistics --- > 5 packets transmitted, 5 packets received, 0.0% packet loss > round-trip min/avg/max/stddev = 0.114/0.162/0.214/0.034 ms