From owner-freebsd-scsi@FreeBSD.ORG  Wed Mar  2 17:36:06 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D2E261065670
	for <freebsd-scsi@freebsd.org>; Wed,  2 Mar 2011 17:36:06 +0000 (UTC)
	(envelope-from weiler@soe.ucsc.edu)
Received: from mail-01.cse.ucsc.edu (mail-01.cse.ucsc.edu [128.114.48.32])
	by mx1.freebsd.org (Postfix) with ESMTP id C037A8FC1E
	for <freebsd-scsi@freebsd.org>; Wed,  2 Mar 2011 17:36:06 +0000 (UTC)
Received: from wraith.cse.ucsc.edu (wraith.cse.ucsc.edu [128.114.56.35])
	by mail-01.cse.ucsc.edu (Postfix) with ESMTPSA id 6CC381009C0D
	for <freebsd-scsi@freebsd.org>; Wed,  2 Mar 2011 09:36:06 -0800 (PST)
Message-ID: <4D6E8006.5040809@soe.ucsc.edu>
Date: Wed, 02 Mar 2011 09:36:06 -0800
From: Erich Weiler <weiler@soe.ucsc.edu>
User-Agent: Thunderbird 2.0.0.24 (X11/20100318)
MIME-Version: 1.0
To: "freebsd-scsi@freebsd.org" <freebsd-scsi@freebsd.org>
References: <E8A852F2-A3CF-45E7-8CE1-F8C50CD202A4@soe.ucsc.edu>
	<4D6D48C6.10900@soe.ucsc.edu> <4D6D6DAC.8050601@soe.ucsc.edu>
In-Reply-To: <4D6D6DAC.8050601@soe.ucsc.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: MFI driver issues
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 17:36:06 -0000

> I guess it would be most useful if I could somehow force MFI to be used 
> on my boot disk as it is now, but use MPS on my 24 JBOD disks coming 
> from the Perc H800 SAS controller...?  They are JBOD because I have them 
> roped into a ZFS filesystem.

I just checked and the Perc H800 uses the LSI SAS2108 chipset, which in 
theory is supposed to be picked up by the MPS driver, according to this 
web page:

http://leaf.dragonflybsd.org/cgi/web-man/?command=mps&section=ANY

but instead it is picked up by the MFI driver...?  What gives?  ;)  Is 
it that the MPS driver *and* the MFI driver both support the LSI SAS2108 
chipset, but the MFI driver checks first during boot, so it wins?