From owner-freebsd-stable@FreeBSD.ORG Fri May 24 05:27: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 B8AEDD2; Fri, 24 May 2013 05:27:56 +0000 (UTC) (envelope-from jpaetzel@FreeBSD.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 74C22B01; Fri, 24 May 2013 05:27:56 +0000 (UTC) Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 9B90620AF0; Fri, 24 May 2013 01:27:55 -0400 (EDT) Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Fri, 24 May 2013 01:27:55 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=references:mime-version:in-reply-to :content-type:content-transfer-encoding:message-id:cc:from :subject:date:to; s=smtpout; bh=1iGdiF8BmWT/1Z3TNd+wmQFYknE=; b= cYou4r6z5QpTJ0C9D+wuDEwzCWRCQSM8PpS4g0Duj+WIl3e0eMbNnY45/foME87R d5V+tU/HgLlBM47TfsDbPGWSvip/aaJVI5pXLFypasEJY9gWrq+mEo8D0K54FqJO rGG2GBR/7Im1rIGc5c7NCqTkc0MxzkmViSqc5H5YC9E= X-Sasl-enc: KBl+or/AjwAslrBJU5eldKt2vrH4Au2tkzKPtxRrCmhl 1369373275 Received: from [10.59.35.195] (unknown [166.137.184.74]) by mail.messagingengine.com (Postfix) with ESMTPA id 2941B200064; Fri, 24 May 2013 01:27:55 -0400 (EDT) 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> <20130524045620.GE28865@glenbarber.us> <20130524051139.GA41712@icarus.home.lan> Mime-Version: 1.0 (1.0) In-Reply-To: <20130524051139.GA41712@icarus.home.lan> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <2690F8C5-62DF-4F0F-9F40-759CA870CF88@FreeBSD.org> X-Mailer: iPhone Mail (10B350) From: Josh Paetzel Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Date: Thu, 23 May 2013 22:26:31 -0700 To: Jeremy Chadwick Cc: YongHyeon PYUN , Glen Barber , "freebsd-stable@freebsd.org" , FreeBSD Release Engineering Team 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 05:27:56 -0000 At this point fxp hardware is over a decade old. I'm loath to introduce dela= ys at the end of the runway for this issue.=20 Keep in mind that delays to 8.4 are pushed directly on to delays for 9.2, wh= ich won't be started until 8.4 is completed, and is desperately needed. (9.1= doesn't have drivers for common shipping hardware for example). Factors lik= e these as well as the age of fxp hardware drive my decision to complete 8.4= and push this fix in to EN territory.=20 Thanks, Josh Paetzel FreeBSD - The Power to Serve On May 23, 2013, at 10:11 PM, Jeremy Chadwick wrote: > On Fri, May 24, 2013 at 12:56:20AM -0400, Glen Barber wrote: >> On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote: >>> [...] >>> So if someone wants to take a stab at this, they'll need to do so and >>> make me an ISO. Sorry that I can't make things easier. :-( >>>=20 >>> This definitely needs to get fixed before 8.4-RELEASE. >>=20 >> *sigh*.... >>=20 >> At this point, it is highly unlikely this will be fixed before >> 8.4-RELEASE. We are _far_ too deep into the release cycle. In fact, we >> are effectively done with the release, and waiting on release notes to >> be completed. >>=20 >> I think this will likely be included in errata notes for the release. >=20 > I urge you to meet with others in Release Engineering and discuss this > fully. This is major enough that, once fixed, it warrants an immediate > binary update (to the kernel + if_fxp.ko) pushed out via freebsd-update. >=20 > fxp(4) is a commonly-used driver; it isn't something rare/uncommon. >=20 > Also remember at this stage we don't know if it's a specific PHY model > or specific NIC model (or series) which triggers it. For all we know it > could affect everything that fxp(4) drives. >=20 > Please don't forget that FreeBSD has a very well-established history of > having rock-solid Intel NIC support. Sure, mistakes happen, we're > human, bugs get introduced, but this does not bode well -- meaning I > would expect Slashdot et al to pick up on this. >=20 >> It is very unfortunate that this waited so long to be reported, as much >> time has passed since 8.4-BETA1... >=20 > This is what happens when people socially proliferate the belief that > "RELEASE is rock solid/stable, don't run stable/X" -- the number of > people who test what changes between RELEASE builds is vastly smaller > comparatively. I've only been saying this for the past 15 years, so > it's even more unfortunate that people keep believing it. :/ >=20 > --=20 > | Jeremy Chadwick jdc@koitsu.org | > | UNIX Systems Administrator http://jdc.koitsu.org/ | > | Mountain View, CA, US | > | Making life hard for others since 1977. PGP 4BD6C0CB |