From owner-freebsd-stable@FreeBSD.ORG Sun May 12 06:45:07 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 AB0939DA; Sun, 12 May 2013 06:45:07 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [199.48.134.227]) by mx1.freebsd.org (Postfix) with ESMTP id 89F69DBD; Sun, 12 May 2013 06:45:07 +0000 (UTC) Received: from glenbarber.us (70.15.88.86.res-cmts.sewb.ptd.net [70.15.88.86]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id D151723F804; Sun, 12 May 2013 02:45:05 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.8.3 onyx.glenbarber.us D151723F804 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Sun, 12 May 2013 02:45:03 -0400 From: Glen Barber To: "Michael L. Squires" Subject: Re: Apparent fxp regression in FreeBSD 8.4-RC3 Message-ID: <20130512064503.GA1632@glenbarber.us> References: <20130508174721.GD1651@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="liOOAslEiF7prFVr" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: 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: Sun, 12 May 2013 06:45:07 -0000 --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 11, 2013 at 10:57:44PM -0400, Michael L. Squires wrote: > I upgraded to FreeBSD 8.4-RC3 and noticed a problem with the fxp > driver on an older Supermicro single CPU single core Xeon > motherboard. >=20 > [...] > Copyright (c) 1992-2013 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 8.4-PRERELEASE #45: Fri May 10 09:43:40 EDT 2013 > root@familysquires.net:/usr/obj/usr/src/sys/NEWGATE i386 Your attached dmesg of -RC3 is not -RC3, it is 8-STABLE. At this point, there have been changes between the stable/8 and releng/8.4 branches enough say that the two have diverged, and the stable/8 code is _not_ what will be the 8.4-RELEASE. While your issue does concern me, it is still unclear that this is a problem with the upcoming 8.4-RELEASE. Can you please try upgrading to the releng/8.4 branch to see if this issue persists? Glen --liOOAslEiF7prFVr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJRjzpvAAoJEFJPDDeguUaj3uQH/RtVyl4/sSoYMYtgf8WQLsUI TqYE093S1FYYFqWvvI43e7V+aaE6cga7sqpKbWfk0V0sutQUm88D3T1Nrn2oyXGn Jwo3akdgicHDAJzNkKE1qBtWxfQecQ60q9a08vJksjjS/20lPOzXcLIVfTIXnGi0 PrXFBiLOPJP42D7SI6tXlSK5l0bck/dqvzH1zO2bXGTm+03EuD2fcT1ESKxAU9cz b+jboswapnMk7lKg6Kn2IBshlVjDB8dRjjc1DbRWBV/bkyXxgFAw0mSoVo0zfoZo GPYIz9kVhceKOMzZ4VeI3YxA9FS3HsIJ5z9iZLhumsMsCDfOpbl/DQjsvAQj49Q= =rszd -----END PGP SIGNATURE----- --liOOAslEiF7prFVr--