From owner-freebsd-stable@freebsd.org  Fri Jul 31 07:20:53 2015
Return-Path: <owner-freebsd-stable@freebsd.org>
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 73E449AEEF0
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Fri, 31 Jul 2015 07:20:53 +0000 (UTC) (envelope-from pi@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 28471135;
 Fri, 31 Jul 2015 07:20:52 +0000 (UTC) (envelope-from pi@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.85 (FreeBSD))
 (envelope-from <pi@opsec.eu>)
 id 1ZL4cb-000GGw-Mg; Fri, 31 Jul 2015 09:20:49 +0200
Date: Fri, 31 Jul 2015 09:20:49 +0200
From: Kurt Jaeger <pi@opsec.eu>
To: Glen Barber <gjb@FreeBSD.org>
Cc: freebsd-stable@FreeBSD.org
Subject: Re: HEADS-UP: PCI ID driver conflict with ahd(4) and pms(4)
Message-ID: <20150731072049.GT49099@home.opsec.eu>
References: <20150731014832.GN90754@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150731014832.GN90754@FreeBSD.org>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jul 2015 07:20:53 -0000

Hi!

> 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:

Which field of pciconf -lvb or sysctl output needs to be compared ?

Is it the device= field ?

dev.atapci.0.%pnpinfo: vendor=0x1002 device=0x439c subvendor=0x15d9 subdevice=0xa711 class=0x01018a

>  0x0100
>  0x0101
>  0x0102
[...]

-- 
pi@opsec.eu            +49 171 3101372                         5 years to go !