From owner-freebsd-stable@freebsd.org Fri Jul 31 13:29:56 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 CA2819AE030 for ; Fri, 31 Jul 2015 13:29:56 +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 B875B2B1A; Fri, 31 Jul 2015 13:29:56 +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 45FB81223; Fri, 31 Jul 2015 13:29:56 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 31 Jul 2015 13:29:54 +0000 From: Glen Barber To: Kurt Jaeger Cc: freebsd-stable@FreeBSD.org Subject: Re: HEADS-UP: PCI ID driver conflict with ahd(4) and pms(4) Message-ID: <20150731132954.GU90754@FreeBSD.org> References: <20150731014832.GN90754@FreeBSD.org> <20150731072049.GT49099@home.opsec.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="50RDeE14MEV4qpyy" Content-Disposition: inline In-Reply-To: <20150731072049.GT49099@home.opsec.eu> 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 13:29:56 -0000 --50RDeE14MEV4qpyy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 31, 2015 at 09:20:49AM +0200, Kurt Jaeger wrote: > Hi! >=20 > > 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: >=20 > Which field of pciconf -lvb or sysctl output needs to be compared ? >=20 > Is it the device=3D field ? >=20 > dev.atapci.0.%pnpinfo: vendor=3D0x1002 device=3D0x439c subvendor=3D0x15d9 > [...] >=20 As far as I can tell (right now), yes. Glen --50RDeE14MEV4qpyy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVu3hSAAoJEAMUWKVHj+KT4q8P/RSZGSqbEpXdX+jTGNl+hG6I boo4JtgKzSGOc4GDIGcKjBpVk0++7XYlFv5spTEIObDaEZVjNNH5qft73atHdePc SspPai1lPNviyQfYiwcgalvsGdgxBDn8VhTlv5TWQwnxNflhoj0/6ItEVUmm9zMF DOqOBdeqDFSJKHz+ujVJNYbUWn5VEYjZH00Qn6QjWEtSiq9xVMw9CpadfLvo+705 4A3uMoQQb4Ze9/eyfoaodBgmZo5HuFqx6HPbKgzyseswxPk1hCsqQq1ZkwhMORxE ECdc/WCNfCcw1nWavoIRN0ONh8YtUdk4w1aw2H79K/vFLbX4Kdj0SvQK14egn9Pm QRfpCXDLW8ovWdyioB1E27kpvd4YqtFCgc6X0buqFuo6xVMd4dUTnN/RqaAZf+un 8KNR+5H2WJ63DnMLXlOyD6kSaOiGhfPDK9om+vFMq8IzXwVtvkPRMUcNHZFPyxv8 vqUzbHAZj0pHZqFXmnVpfak68pnLMVO+HzzDn/gCVH7aaOujgBjkjtugAbgFVj/i O0gZzhTUbMloR6WDckhGIBfZST9bqHpMegjutkBVgictERoDgmsUlWu5hDRu4h8M zuB1aq9VgnQ206BDr3aXk2K988YL5NamBiKY9cQvr8QPVIidrN54+bN5MpJ8oZJU fpjkd0t6uyMVqJz9AMwL =/pay -----END PGP SIGNATURE----- --50RDeE14MEV4qpyy--