From owner-freebsd-scsi@FreeBSD.ORG  Sat Feb 15 16:14:49 2014
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D0137BF8
 for <freebsd-scsi@freebsd.org>; Sat, 15 Feb 2014 16:14:49 +0000 (UTC)
Received: from mail.tdx.com (mail.tdx.com [62.13.128.18])
 by mx1.freebsd.org (Postfix) with ESMTP id 723EF139E
 for <freebsd-scsi@freebsd.org>; Sat, 15 Feb 2014 16:14:49 +0000 (UTC)
Received: from study64.tdx.co.uk (study64.tdx.co.uk [62.13.130.231])
 (authenticated bits=0)
 by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s1FGEfvq029915
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
 for <freebsd-scsi@freebsd.org>; Sat, 15 Feb 2014 16:14:41 GMT
Date: Sat, 15 Feb 2014 16:14:40 +0000
From: Karl Pielorz <kpielorz_lst@tdx.co.uk>
To: freebsd-scsi@freebsd.org
Subject: Wiring down devices with LSI 2308 / mps?
Message-ID: <41337B9333D94F88B9469A60@study64.tdx.co.uk>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Sat, 15 Feb 2014 16:14:49 -0000


Hi,

I've got a SuperMicro board that has an onboard LSI 2308 onboard. This 
appears using the mps driver:

"
mps0: <LSI SAS2308> port 0xc200-0xc2ff mem 
0xf33c0000-0xf33cffff,0xf3380000-0xf33bffff irq 44 at device 7.0 on pci0
mps0: Firmware: 15.00.00.00, Driver: 16.00.00.00-fbsd
mps0: 
IOCCapabilities:185c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,IR>
"

I'd like to wire the devices down on this - but that doesn't seem to work :(

I tried this by putting entries in '/boot/device.hints' such as:

"
hint.scbus.0.at="mps0"

hint.da.0.at="scbus0"
hint.da.0.target="2"
hint.da.0.unit="0"

hint.da.1.at="scbus0"
hint.da.1.target="1"
hint.da.1.unit="0"
...
"

Testing though shows that maybe the controller itself is collapsing 
'missing' ports/targets?

e.g. Attach a disk to 'Port 0' - and it shows as:

 da2 at mps0 bus 0 scbus0 target 2 lun 0

Ok, target 2? - but at least that's mapped to da2 (wiring works)

Take the disk off, and connect it to Port 1 - and it shows as:

 da2 at mps0 bus 0 scbus0 target 2 lun 0

Port 1 is target 2 as well? - Switch the drive to 'Port 2' - and you get:

 da2 at mps0 bus 0 scbus0 target 2 lun 0

So port 2 is also target 2? (if the others aren't occupied)

Add a 2nd drive (to any port) and you get:

 da3 at mps0 bus 0 scbus0 target 3 lun 0


So the 'wiring down' is working - but it looks like the LSI collapses it's 
own 'missing drives'? - And starts at Target 2?

I can't see any setting in the LSI bios that would change this? - I'm 
presuming it must be possible not to have it do this - though searching the 
lists didn't turn anything obvious up...

Thanks,

-Karl