From owner-freebsd-stable@freebsd.org Fri Jul 31 01:48:34 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE6B09AE6E9 for ; Fri, 31 Jul 2015 01:48:34 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id A67AE75F; Fri, 31 Jul 2015 01:48:34 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 31A0012C0; Fri, 31 Jul 2015 01:48:34 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 31 Jul 2015 01:48:32 +0000 From: Glen Barber To: freebsd-stable@FreeBSD.org Cc: FreeBSD Release Engineering Team Subject: HEADS-UP: PCI ID driver conflict with ahd(4) and pms(4) Message-ID: <20150731014832.GN90754@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="FrxVhwK/bNRjN48l" Content-Disposition: inline X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 31 Jul 2015 01:48:34 -0000 --FrxVhwK/bNRjN48l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The new driver for PMC Sierra SAS/SATA HBAs does not properly validate that both the vendor ID and device ID of some storage device drivers. At present, we know there is a conflict with ahd(4), it is possible there are more. The issue was reported on the -current@ mailing list in this thread: https://lists.freebsd.org/pipermail/freebsd-current/2015-July/056778.html If you are running 10.2-RC1, you should be unaffected when upgrading to 10.2-RC2. If you are running 10.2-BETA2 or prior (and 10.2-PRERELEASE prior to the releng/10.2 branch), please exercise caution when upgrading to the latest stable/10 or releng/10.2 if your storage controller matches any of the following PCI device IDs: 0x0100 0x0101 0x0102 0x0103 0x0104 0x0105 0x0110 0x050A 0x1028 0x1029 0x102a 0x1200 0x1203 0x8001 0x8006 0x8008 0x8009 0x8018 0x8019 0x8070 0x8071 0x8072 0x8073 0x8074 0x8075 0x8076 0x8077 0x8081 0x8088 0x8089 0x8091 0x8098 0x8099 0xB555 0xabcd The resolution to this issue is still being investigated, and is considered a blocker for the 10.2-RELEASE, which means it is now quite likely there will be an -RC3 for this release. Thank you for your patience while this issue is being resolved. Glen On behalf of: re@ --FrxVhwK/bNRjN48l Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVutPwAAoJEAMUWKVHj+KTdm0P/3IA2ev2YGYxbiYzNUgt+Hrz qfxeOdlVxZmuYjTTmDPBWMzeORs05GSMGOrFZQ127jAVxxru2DsJZjL82DfWYn// rrUljUiPKIMPsLIzJIfJlzzZlyzNbOPMyAVov654jdT7J0dmQNM48YJdYbFUp9Zl dR7vI//ndHxtGIsX/IoAd2OBTetVXBW07bG+NH3Tiq883x1IzWGApX9m3aKOmBw7 FP+zKMg2SfXC/cWTxPlJaSokK45XLBCJB8DMlrr35cXZU6qBGR3Zg44ZLeAtAWii 6wlceq06odweghboRJKYkasrdyg5w/M60/DovyYfeT5DKgKQiYOTJoDvK0o8apQX RdZd5/1ppli3Qdajgd+tYfq9YW2OneJ1JMJg6iTCgiYxX6mNiW8O5PBeVjOkOGxI HgTGEPct5VN1XH6Tohu9A0pq7qGS6K18JWfuINOW31e3vAUyWkN5QPVhoD5NnU+g vztv9gnYX98jdoVoOA79DCPC4c6YxAzt/sJ+NsaFt7se1wclKyiE+/FnJr8D5gfZ OOwnXuEcqRH6NJgH3nYNjECDVVxb1Gbue8ad3skLDqmUpwgq2nBba+oFbD3cfj8G g8L67+XX91RrMnlADee8pQafd629KGB2jhOEVor2JGRu4RTpTTjcSwillDRfU4fN NQ32nL1JMk330/nJUdBl =1fKC -----END PGP SIGNATURE----- --FrxVhwK/bNRjN48l--