Date: Fri, 24 May 2013 01:24:24 -0400 From: Glen Barber <gjb@FreeBSD.org> To: Jeremy Chadwick <jdc@koitsu.org> Cc: YongHyeon PYUN <pyunyh@gmail.com>, FreeBSD Release Engineering Team <re@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130524052424.GF28865@glenbarber.us> In-Reply-To: <20130524051139.GA41712@icarus.home.lan> References: <alpine.BSF.2.00.1305232013110.14717@familysquires.net> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
--7cm2iqirTL37Ot+N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Speaking entirely on behalf of myself now... On Thu, May 23, 2013 at 10:11:39PM -0700, Jeremy Chadwick wrote: > > 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 It can be solved with a -pN update after 8.4-RELEASE is out. > fxp(4) is a commonly-used driver; it isn't something rare/uncommon. >=20 Right. So why do we have exactly 1 (now 2) reports of this? We are already behind the release schedule. There have been 4 "Hey, the next release is available for testing, so please do so" announcements. At this stage, holding up this release for last-minute (not last-minute code changes, either) reports will do nothing for the FreeBSD Project as a whole but hold up the remaining releases scheduled for the remainder of the year. > 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 Right. Without this information, we simply cannot hold off the release indefinitely. I've asked the OP to do some very specific things, all without yielding results, as well as replies from others. > 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 This is not a last minute bug. This is a last minute report, sadly. Glen --7cm2iqirTL37Ot+N Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJRnvmIAAoJEFJPDDeguUaj7bUH/RV6ysx/1ZzZexqBq6QVJ60U yrr7gkABtzM2vpwgc3hAy/A8b3bturjyzW375ORav25CkbvInmmVdgVe5lKb4BmK KZlgVFbscN1mYygLX4YvgdkHsJozH21mqLrXPDoe2dgdifg+d8xwLPBoycRGhReR FKGsqbwFJ843bHcqoLHJXSesYrRKYQEl0302B0ajd5SfVMDMtAk4muk3HmS0rd8y J3b2G63WJAewKWSshlecYzrGHfIej2f7VhciTfvmsJrYl6+e1YqVMozepSR1aerE eVKIymZmKJ73VGgfKi+W849TA39tkZ1VgVhqOCtV2xoS/jNno35B9bjBj27TC5Q= =ssXG -----END PGP SIGNATURE----- --7cm2iqirTL37Ot+N--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130524052424.GF28865>