From owner-freebsd-stable@FreeBSD.ORG Fri May 24 03:03:56 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 61BF03B9 for ; Fri, 24 May 2013 03:03:56 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:227]) by mx1.freebsd.org (Postfix) with ESMTP id 2CB0C235 for ; Fri, 24 May 2013 03:03:56 +0000 (UTC) Received: from omta07.emeryville.ca.mail.comcast.net ([76.96.30.59]) by qmta12.emeryville.ca.mail.comcast.net with comcast id felJ1l0031GXsuc01f3sqL; Fri, 24 May 2013 03:03:52 +0000 Received: from jdc.koitsu.org ([67.180.84.87]) by omta07.emeryville.ca.mail.comcast.net with comcast id ff3r1l00g1t3BNj8Uf3sWE; Fri, 24 May 2013 03:03:52 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id C45DF73A33; Thu, 23 May 2013 20:03:51 -0700 (PDT) Date: Thu, 23 May 2013 20:03:51 -0700 From: Jeremy Chadwick To: Glen Barber Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524030351.GA39091@icarus.home.lan> References: <20130508174721.GD1651@glenbarber.us> <20130524010943.GA37252@icarus.home.lan> <20130524012117.GE1672@glenbarber.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130524012117.GE1672@glenbarber.us> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369364633; bh=TFKt/3PPF9OHSX3nE1QogbgK4OvFiXTOGqiWQE/1hjI=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=iFwPXFeq2IwA/TxJ0V1z4OOwGZMQJfeoagwRUvx9ezH7L/NySYxErLtAnZo1LznRu nfcVsX6wtzbYaXpOzztIKajJYGpbgK6PbgZ6QSaeohn6eYnQ8BxGR3ANGMgHYpk3E6 CWTLM2z9SOreskSSmTd2WQQkYGymrX3qCONRdNcAh+ZJqauPwsdimqzQ4eC+pb8whT SMdpve4fuGTHfhrnehbDjfUNZDzIfwDVqgC791ZIWr3+5WaLbyoPrOBz+8RpLdKiw3 nyTOGPLfzvxSLXRcYnqav1WI2U3gjqb6y9oPGuJRxeEENG+VE0KTI3kDSTZUPmhdnw Ok7L8PWKXmHYw== Cc: YongHyeon PYUN , Craig Rodrigues , FreeBSD Release Engineering Team , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list 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 03:03:56 -0000 On Thu, May 23, 2013 at 09:21:17PM -0400, Glen Barber wrote: > On Thu, May 23, 2013 at 06:09:43PM -0700, Jeremy Chadwick wrote: > > On Thu, May 23, 2013 at 08:18:33PM -0400, Michael L. Squires wrote: > > > I've just tested 8.4-RC3 using a different Supermicro 1U box with a fresh > > > installation of 8.4-RC3. I had problems with the installation, wouldn't > > > boot until I used a Windows 98 FDISK to write a master boot record > > > (no idea why; this system uses an Adaptec SATA 1.5 6-channel PCI-X > > > board with two > > > drives in RAID 1). > > > > > > Using the em0 interface there are no problems with DHCP; when I > > > switch to the fxp0 interface the interface starts going up/down in > > > the same manner as reported. > > > > > > The problem appears associated with "world", not with the kernel (running > > > the 8.4 kernel with the 8.3 world does not have this problem). > > > > > > This motherboard is an X5DPL-iGM with 2 Xeon 2.8GHz CPUs and 4 GB of RAM. > > > The other unit (an earlier board) has a Serverworks chipset with a single > > > Xeon CPU but also with a 100Mbit Intel Pro100 Ethernet port and a 1000Mbit > > > Intel Pro1000 Ethernet port. > > > > > > This unit isn't doing anything useful, so testing isn't a problem. > > > > Mike, Yong-Hyeon asked you a very important question which you didn't > > answer: > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073458.html > > > > If you assign a static IP address, does fxp0 behave properly? > > > > I'm also re-adding Yong-Hyeon to the CC list here. > > > > At this point, I am not convinced we have a problem with what will turn > out to be 8.4-RELEASE. > > There have been several attempts to ensure the upgraded version is > actually 8.4-RC3 (and again, 'uname -a' is not provided in this > email...). > > I find it very hard to believe that we have exactly one fxp(4) user > upgrading to 8.4-*. > > I'd really like to make sure that this is not an issue that will affect > an uncountable number of users, but truthfully, at this point have to > consider it a local configuration problem. I have numerous Supermicro 1U boxes sitting in my garage from closing down my hosting organisation back in August 2012. I am certain one or two of them have Intel NICs that use fxp(4) -- the problem is that I don't know what exact NIC and PHY model they use. >From what I can tell, there are at least two systems Mike has which experience this anomaly. One of those systems' dmesg: http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073440.html The relevant lines start at "fxp0: