From owner-freebsd-stable@FreeBSD.ORG Wed May 29 06:42:33 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 849B73BA; Wed, 29 May 2013 06:42:33 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by mx1.freebsd.org (Postfix) with ESMTP id 4D287E68; Wed, 29 May 2013 06:42:33 +0000 (UTC) Received: by mail-pb0-f46.google.com with SMTP id rq2so8831897pbb.19 for ; Tue, 28 May 2013 23:42:33 -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=PrSZ2wHrFr986/SAHgUWEFJ0nwM6nSs9j47hCGOBrxA=; b=HBz2RDvDHh95hOdS0L7LJCsbPOz6cUBQmJ7h9tWE3KLHFJpovGGKvHcXAwh8oprp10 2vTYAtyZa3AGSRxGx9DdTfQQD67B+WWomBj5qjEZ88TeZ71zR5HK4WBvh4WJH1Pl/qoW zbL1MWYciu3FXqCTcRLR4G6991ThCUdNzFjpQwHuyLQlX14lgnfZ1FojslvRwQ4Cv90+ hxTeJNWHzC2dSrgFF+TGYCW70umMVrH1czncLeL5BHxfefl6D6log3Yid8ocHVLMJ2wN cbL0KiHADsvjtFZsehl+iDeTVhHyW4ANTQHt7hyLrbJtDUMbA0NKdWmJHo6bFPJWi68y i4lA== X-Received: by 10.68.190.104 with SMTP id gp8mr1435053pbc.120.1369809753070; Tue, 28 May 2013 23:42:33 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPSA id w8sm36114902pbo.9.2013.05.28.23.42.28 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 28 May 2013 23:42:31 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 29 May 2013 15:42:24 +0900 From: YongHyeon PYUN Date: Wed, 29 May 2013 15:42:24 +0900 To: "Michael L. Squires" Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130529064224.GB3042@michelle.cdnetworks.com> References: <20130524044919.GA41292@icarus.home.lan> <20130524054720.GA1496@michelle.cdnetworks.com> <20130524.162926.395058052118975996.hrs@allbsd.org> <20130524.163646.628115045676432731.hrs@allbsd.org> <20130526113841.GA1511@michelle.cdnetworks.com> <20130527043923.GA1480@michelle.cdnetworks.com> <20130528023300.GA3077@michelle.cdnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: jdc@koitsu.org, gjb@freebsd.org, freebsd-stable@freebsd.org, re@freebsd.org 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: Wed, 29 May 2013 06:42:33 -0000 On Tue, May 28, 2013 at 03:34:00PM -0400, Michael L. Squires wrote: > Short answer: it didn't work. [...] > Patch did not solve the problem on the home NAT box. I'll try it on the Hmm, I can't reproduce it on my box. I double checked every possible controller initialization sequences in driver but couldn't find a clue. Let you know if I manage to narrow down the issue. > second 1U box at work tomorrow. > > I applied the patch (see below) and recompiled/reinstalled world. > Rebuilding kernel should be enough. > root@familysquires:/usr/src/sys/dev/fxp # uname -a > FreeBSD familysquires.net 8.4-RELEASE FreeBSD 8.4-RELEASE #54: Sun May 26 > 22:56:19 EDT 2013 root@familysquires.net:/usr/obj/usr/src/sys/NEWGATE > i386 > > drwxr-xr-x 236 root 3584 May 28 10:28 ../ > -rw-r--r-- 1 root 95366 May 28 10:28 if_fxp.c > -rw-r--r-- 1 root 94968 Mar 28 09:04 if_fxp.c.orig > -rw-r--r-- 1 root 15638 Mar 28 09:04 if_fxpreg.h > -rw-r--r-- 1 root 8717 Mar 28 09:04 if_fxpvar.h > -rw-r--r-- 1 root 23009 Mar 28 09:04 rcvbundl.h > > One immediate difference in behavior is that without the modified rc.conf > the box was unable to use ntp to the outside world; it eventually sync'd on > my internal ntp server. With the modified rc.conf the box immediately > sync'd to an ntp server in the outside world. > There is a side-effect of the rc.conf workaround. Parallel detection may or may not work and generally can result in duplex mismatch.